Enter the following command to stop the agent.

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.

Setting-up the Topology 4-19

4. In the Libraries and Drivers step, select from the list the external libraries and

drivers to deploy with this agent. Only libraries added by the user appear here. Note that the libraries can be any JAR or ZIP file that is required for this agent. Additional JDBC drivers or libraries for accessing the source and target data servers must be selected here. You can use the corresponding buttons in the toolbar to select or deselect all libraries andor drivers in the list.

5. Click Next.

6. In the Datasources step, select the datasources definitions that you want to include

in this agent template. You can only select datasources from the wizard. Naming and adding these datasources is done in the Data Sources tab of the Physical Agent editor.

7. Click Next.

8. In Template Target and Summary step, enter the Target Template Path where the

WLS template will be generated.

9. Click Finish to close the wizard and generate the WLS template.

The Template generation information dialog appears.

10. Click OK to close the dialog.

The generated template can be used to deploy the agent in WLS using the WLS configuration wizard. Refer to the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for more information. Declare the Supervisor in the WLS Credential Store After deploying the template, it is necessary to declare the Supervisor into the WLS Credential Store. Refer to the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for more information.

4.3.2.2 Deploying Datasources from Oracle Data Integrator in WLS for an Agent

You can create datasources from the Topology Navigator into a WebLogic Server for which a Java EE agent is configured. To deploy datasources in a Oracle WebLogic Server: 1. Open the Physical Agent Editor configured for the WLS application server into which you want to deploy the datasources.

2. Go to the Datasources tab.

3. Drag and Drop the sourcetarget data servers from the Physical Architecture tree in the Topology Navigator into the DataSources tab.

4. Provide a JNDI Name for these datasources.

5. Right-click any of the datasource, then select Deploy Datasource on WLS.

6. Fill in the following fields: ■ Host : Host name or IP address of the WLS Admin Server. ■ Port : Port of the WLS Admin Server ■ User : WebLogic server user name. ■ Password : this user’s password