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

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 4-20 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ Target : WLS Target into which this datasource will be deployed.

7. Click OK.

WLS Datasource Configuration and Usage When setting up datasources in WebLogic Server for Oracle Data Integrator, please note the following: ■ Datasources should be created with the Statement Cache Size parameter set to 0 in the Connection Pool configuration. Statement caching has a minor impact on data integration performances, and may lead to unexpected results such as data truncation with some JDBC drivers. ■ If using Connection Pooling with datasources, it is recommended to avoid ALTER SESSION statements in procedures and Knowledge Modules. If a connection requires ALTER SESSION statements, it is recommended to disable connection pooling in the related datasources, as an altered connection returns to the connection pool after usage.

4.3.3 Load Balancing Agents

Oracle Data Integrator allows to load balance parallel session execution between physical agents. Each physical agent is defined with: ■ A maximum number of sessions it can execute simultaneously from a work repository The maximum number of sessions is a value that must be set depending on the capabilities of the machine running the agent. It can be also set depending on the amount of processing power you want to give to the Oracle Data Integrator agent. ■ Optionally, a number of linked physical agents to which it can delegate sessions executions. An agents load is determined at a given time by the ratio Number of running sessions Maximum number of sessions for this agent.

4.3.3.1 Delegating Sessions

When a session is started on an agent with linked agents, Oracle Data Integrator determines which one of the linked agents is less loaded, and the session is delegated to this linked agent. An agent can be linked to itself, in order to execute some of the incoming sessions, instead of delegating them all to other agents. Note that an agent not linked to itself is only able to delegate sessions to its linked agents, and will never execute a session. Delegation cascades in the hierarchy of linked agents. If agent A has agent B1 and B2 linked to it, and agent B1 has agent C1 linked to it, then sessions started on agent A Note: This operation only creates the Datasources definition in WebLogic Server. It does not install drivers or library files needed for these datasources to work. Additional drivers added to the Studio classpath can be included into a WLS Agent Template. See Section 4.3.2.1.2, Create an WLS template for the Java EE Agent for more information.