Generate Java EE Agent Template

Configuring Oracle Data Integrator 3-9

3.3.3.1 Credential Store Entries for the Java EE Agent

The Java EE agent requires a single key storing the login and password for a user that will be used to connect the repositories. The key is the Supervisor Key value provided when creating the agent this key is SUPERVISOR in the default agent template and the user and password values must be a valid user name and password pair for a user with Supervisor privileges. For example, if you use the default template and have created a repository with a SUPERVISOR user, you should create a key using the following WLST command:

1. Navigate to the ODI_HOMEcommonbin directory.

Note that you must use WLST from this directory when using Oracle Data Integrator. The default WLST script provided with the Oracle WebLogic Server will not work. For more information on using WLST commands, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

2. Launch wlst.

■ On UNIX operating systems: .wlst.sh ■ On Windows operating systems: wlst.cmd 3. Execute the following WLST command substituting your usernames and passwords: connectweblogic,welcome1,t3:localhost:7001 createCredmap=oracle.odi.credmap, key=SUPERVISOR, user=SUPERVISOR, password=supervisor1, desc=Key for Supervisor disconnect

3.3.3.2 Credential Store Entries for the Oracle Enterprise Manager

Oracle Enterprise Manager requires an ODI Supervisor key to connect the agents deployed on a domain and manage them. This key is similar to the key created for the Java EE Agent. In addition to this key, Oracle Enterprise Manager requires a second key containing the username and password of a WebLogic administrator for each domain into which ODI Java EE Agents are deployed and must to be managed. The second key is named after the domain, and contains a valid WebLogic administrator username and password. For example, if you use the default template and have it deployed within a domain called based domain with the WebLogic administrator called WebLogic, you can create the keys using the following WLST commands: createCredmap=oracle.odi.credmap, key=SUPERVISOR, user=SUPERVISOR, password=, desc=Key for Supervisor createCredmap=oracle.odi.credmap, key=base_domain, user=weblogic, password=, desc=Username and password for base_domain Example Scenario: 1. Three agents OdiAgent1, OdiAgent2 and OdiAgent3 are defined as physical agents in the topology.