Launching a Standalone Agent

Setting-up the Topology 4-17

4.3.2 Java EE Agent

Managing a Java EE agent involves the actions discussed in the sections: ■ Section 4.3.2.1, Deploying an Agent in a Java EE Application Server Oracle WebLogic Server ■ Section 4.3.2.2, Deploying Datasources from Oracle Data Integrator in WLS for an Agent

4.3.2.1 Deploying an Agent in a Java EE Application Server Oracle WebLogic Server

The easiest way for deploying an Oracle Data Integrator agent in Oracle WebLogic Server WLS is to generate a WLS template with Oracle Data Integrator. This template can directly be deployed into WLS Configuration Wizard. To deploy an agent in a Java EE Application Server Oracle Web Logic Server, follow the procedure in the following tasks. ■ Task 1: Define the Java EE Agent in the Topology ■ Task 2: Create an WLS template for the Java EE Agent

4.3.2.1.1 Define the Java EE Agent in the Topology

Defining a Java EE agent consists of two tasks. First, you need to create the physical agent corresponding to your Java EE agent, then, a logical agent. To create a physical agent: 1. In Topology Navigator right-click the Agents node in the Physical Architecture accordion.

2. Select New Agent.

3. In the Definition tab, pay attention to the following parameters.

■ Name is the name of the Java EE agent. ■ Host must correspond to the WLS host name. ■ Port is the HTTP port of the Java EE Agent application. ■ Protocol : Protocol to use for the agent connection. Possible values are http or https. Default is http. ■ Web Application Context is name of the web application corresponding to the Java EE agent. -IMMEDIATE=truedefault|false If this parameter is set to yes then the agent is killed without waiting for completion of its running sessions. If it is set to no then the agent is killed after all its running sessions reach completion or after the MAX_ WAIT timeout is reached. Default value is No. -MAX_WAIT=stop timeout in millis This parameter can be used when IMMEDIATE is set to No. It defines a timeout in milliseconds after which the agent is killed regardless of the running sessions. Default is 0, meaning no timeout and the agent is killed after all its running sessions reach completion. Parameters Description 4-18 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator 4. Drag and drop the work repositories or data servers to be managed as Java EE data sources from the Repositories accordion in the Topology Navigator into the DataSources tab of this agents Editor.

5. Provide a JNDI name for these data sources.

6. Drag and drop the sourcetarget data servers that this agent will access from the Physical Architecture accordion in the Topology Navigator into the DataSources tab of this agents Editor.

7. Provide a JNDI name for these data sources.

8. From the File menu, click Save to save the Physical Agent.

To create a logical agent: 1. Create a Logical Agent for this Physical Agent as described in Section 4.2.6, Creating a Logical Agent . 2. Map the Logical Agent in the appropriate context.

4.3.2.1.2 Create an WLS template for the Java EE Agent

Oracle Data Integrator provides a WLS Template Generation wizard to help you create an WLS template for a run-time agent. To open the WLS Template Generation wizard:

1. From the Physical Agent Editor toolbar menu, select Generate WLS Template.

This starts the Template Generation wizard.

2. In the Agent Information step, review the agent information and modify the

default configuration if needed. The Agent Information includes the following parameters: ■ General Agent Name: Displays the name of the Agent that you want to deploy. ■ Master Repository Connection JNDI Datasource Name: The name of the datasource used by the Java EE agent to connect to the master repository. The template can contain a definition of this datasource. Default is jdbcodiMasterRepository. ■ Connection Retry Settings Connection Retry Count: Number of retry attempts done if the agent loses the connection to the repository. Note that setting this parameter to a non-zero value, enables a high availability connection retry feature if the ODI repository resides on an Oracle RAC database. If this feature is enabled, the agent can continue to execute sessions without interruptions even if one or more Oracle RAC nodes become unavailable. Retry Delay milliseconds: Interval in milliseconds between each connection retry attempt. ■ Supervisor Authentication Supervisor Key: Name of the key in the application server credential store that contains the login and the password of an ODI user with Supervisor privileges. This agent will use this user credentials to connect to the repository.

3. Click Next.