Navigate to the ODI_HOMEcommonbin directory.
3-10 Oracle Fusion Middleware Installation Guide for Oracle Data Integrator
2.
OdiAgent1 and OdiAgent2 are Java EE agents and OdiAgent3 is a Standalone agent.
3.
OdiAgent1 is deployed on a WLS domain with the name agent_1_domain and OdiAgent2 is deployed on a WLS domain with the name agent_2_domain. Both
domains use a WebLogic user as their administrator.
4.
A user called SUPERVISOR is declared in the Master Repository, and SUPERVISOR is specified as the Supervisor Key value when creating the Java EE
agent templates.
The following sequence of WLST commands creates the appropriate entries: createCredmap=oracle.odi.credmap, key=SUPERVISOR, user=SUPERVISOR,
password=SUPERVISOR, desc=Key for Supervisor createCredmap=oracle.odi.credmap, key=agent_1_domain, user=weblogic,
password=, desc=Username and password for agent_1_domain createCredmap=oracle.odi.credmap, key=agent_2_domain, user=weblogic,
password=, desc=Username and password for agent_2_domain
Once the credential maps are created, you can start the Java EE components. Agents are fully functional, but Oracle Data Integrator Console and Oracle Enterprise
Manager may need extra configuration. See Configure Oracle Data Integrator Console
Connections and
Configure Oracle Enterprise Manager for more information.
For more information on Oracle Data Integrator JEE configuration options, see High Availability for Oracle Data Integrator in the Oracle Fusion Middleware High
Availability Guide.