ODI 12c – Standalone Collocated Agent

ODI12c has are three types of agents:

  • Standalone agent no WLS installed
  • Standalone Collocated agent WLS installed but not used.
  • JEE agent WLS installed and used. The agent is JEE apps running in the domain

The Standalone Collocated Agent comes as additional feature with ODI12c, which is the blend of both standalone and Java EE agents.  This can be configured only with an ODI12c Enterprise Edition Installation. A Standalone Collocated Agent is started as its own binary. Alternately we can start the agent using Weblogic Server.

Features of the Standalone Collocated Agent in ODI 12c:

• UI-driven configuration through Configuration Wizard
• Multiple configurations can be maintained in separate domains
• Node Manager can be used to control and automatically restart agents

Configurations required for this agent are user interface driven by invoking config.sh,  There is no need to define the configurations in odiparams.bat  file manually, which is in ODI 11g.

ODI 12C Standalone Collocated Agent vs ODI 11g Agents.

Features

ODI 12C  Standalone Collocated Agent

ODI 11g Standalone Agent

ODI 11g Java EE agent

Manual agent configuration for odiparams.bat

Not required. It is UI driven configuration through configuration wizard.

Manual intervention is required to configure odiparams.bat file

Not required. It is UI driven configuration through configuration wizard.

Managing through command prompt

Yes. We can start this agent using command prompt using agent.bat

Yes. We can start this agent using command prompt using agent.bat

No.

Managing(Agent startup/shutdown) through web services

Yes. We can manage through restricted Application servers (eg: web logic server).

No. we cannot manage through Web services. It will be always through Command prompt using agent.bat

Yes.

Invoking Web services

Yes.

No.

Yes.

UI driven

Yes.

No. Managed only through ODI Studio.

Yes.

The Standalone Collocated Agent can be started by either a command prompt or through invoking the ODI server configured through the Weblogic Server (dedicated Weblogic 12C application)

a. Starting  Standalone Collocated Agent via command prompt:
/Middleware/user_projects/domains/../bin>./agent.sh -NAME=<Agent_Name> -PORT=20910

b. Starting Standalone Collocated Agent via Weblogic Server:

1. Start the Node Manager.
2. Start the Administration Server.
3. Starting the Collocated standalone agent.

Other ODI 12C agents:

Standalone Agent :
• The ODI 12c Standalone Agent is similar to ODI 11g Standalone Agent.
• No Web logic Server is installed.
• Requires manual configuration of odiparams.sh file.
• Managed only through ODI Studio.
• Comes with only ODI 12c standalone installation mode.

JEE Agent: (Java Enterprise Edition Agent)
• Similar to ODI 11g Java EE agent
• The agent is one of many possible JEE apps running in the domain.
• No manual configurations required. It is all user interface (UI) Driven.
• Managed only through Application servers.
• Comes with only ODI 12c Enterprise Edition Installation mode.

below are the steps to create a domain:

  1. Start the Fusion Middleware Configuration Wizard to create a domain for the agent. 
[myuser@myhost ~]$ cd $ODI_HOME/common/bin
[myuser@myhost bin]$ pwd 
/home/oracle/odi12c/odi/common/bin
[myuser@myhost bin]$ ./config.sh 

2. On the Configuration Type panel, leave the defaults. If you do not yet have a WLS domain, then the first one created will be called base_domain by default. You can rename it like odi_agent

3. On the Templates panel, select Oracle Data Integrator – Standalone Collocated Agent OR Oracle Data Integrator – Standalone Agent accordingly. It is standalone in the sense that it does not use WLS, but it is collocated in the sense that WLS is installed. Selecting this one option causes several other options to be selected. CAUTION! Do NOT select Oracle Data Integrator – Agent or it will not work!

4. On the Administrator Account panel, enter your password twice. 

5. On the Domain Mode and JDK panel, leave the defaults.

6. On the Database Configuration Type panel, change the Service to the database service (not database instance), such as orcl.us.oracle.com. Change the Host Name to ur host or localhost, change the Schema Password to the password for DEV_STB that you picked when you ran RCU then Click Get RCU Configuration to continue, & then click Next to continue.

7. On the JDBC Component Schema panel, leave the defaults.

8. On the JDBC Component Schema Test panel, leave the defaults.

9. On the Advanced Configuration panel, select System Components. The defaults are fine, but you do have to go through the panels to make them apply.

10. On the System Components panel, leave the defaults.

11. On the ODI Server Configuration panel, make a note of the Port (you will need that number later), and change the Supervisor Password to the password you picked when you ran RCU.

12. On the Machines panel, leave the defaults.

13. On the Assign System Components to Machines panel, leave the defaults.

14. On the Configuration Summary panel, leave the default

15. On the Configuration Progress panel, there is nothing to do. Just make sure that it ends with the progress bar at 100%, and with the message, Domain Created Successfully!Click Finish

The physical agent is a background OS process that communicates with ODI via TCP/IP ports. To create, start, and test the physical agent, perform the following steps:

1. Login to ODI studio On the Topology tab, expand Physical Architecture, then expand Agents. Right-click Agents and select New Agent

2. On the Agent panel, on the Definition tab, in Name, enter the name that matches the agent you created with the earlier domain wizard: OracleDIAgent1In Port, enter the port that matches the agent you created with the earlier domain wizard: 20910Verify that Host is correct. Save You should now see the new agent display on the left under Topology > Physical Architecture > Agents.

3. Change to the directory of the domain that contains the binary files. Start the agent using the agent name from the domain. Leave that window running (perhaps minimized or sent to the back of the desktop.)

[myuser@myhost ~]$ cd $FMW_HOME/user_projects/domains/base_domain/bin 
[myuser@myhost bin]$ pwd 
/home/oracle/odi12c/user_projects/domains/base_domain/bin
[myuser@myhost bin]$ ./agent.sh -NAME=OracleDIAgent1 -PORT=20910 

The very first time you run this, you will get LOTS of output as Java initializes. Subsequent run times the messages will be fewer. The -PORT parameter is optional but recommended. In studio Click Test to test the agent now that the process is running outside of ODI.

4. On the Topology tab, expand Logical Architecture, then expand Agents. Right-click Agents and select New Logical Agent. On the Logical Agent panel, on the Definition tab, in Name, enter MyAgent. In the Physical Agents pull-down, select OracleDIAgent1. We should now see the new agent display on the left under Topology > Logical Architecture > Agents.

We can also start the agent Using http://<hostname&gt;:PORT/console

Advertisements