3-8 Oracle Fusion Middleware Installation Guide for Oracle Data Integrator
After deploying the Oracle Data Integrator templates, the following steps must be performed before starting the Java EE Agent, Oracle Data Integrator Console and
Oracle Enterprise Manager applications deployed in WebLogic Server.
3.3.1 Declare the Java EE Agent in Topology
All Java EE components are pre-configured in default templates. The default Java EE agent has a template, but the agent is not declared in the repository. Therefore, the
agent must be configured in the repository.
1.
In Topology Navigation, connect to the Master Repository and declare the Java EE agent and provide the following:
■
Name - Name of the physical agent.
Caution: If you use the default Java EE agent, then you must create an agent
called OracleDIAgent case sensitive. In addition, if you use the default agent created during the Java EE install, you do not have to create a new
template. See Managing Agents in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information.
■
Host - Name of the host where the Java EE agent will be started.
■
Port : Port number of the WLS Server where the Java EE agent is deployed.
■
Protocol : Protocol to use for the agent connection. Possible values are http or
https. Default is http.
■
Web Application Context : Default value is oraclediagent. The web
application context should match the name set when deploying the agent template.
For detailed instructions on declaring the Java EE agent in Topology, see Managing Agents in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator.
3.3.2 Generate Java EE Agent Template
A Java EE agent template can be generated from the ODI Studio. This is required to bundle the agent code with extra drivers with the source or target and Work or Master
datasources declared in the Topology. For more information on datasource declaration, deployment and template generation in ODI Studio, see Java EE Agent
in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator.
3.3.3 Add Credential Store Entries
The Oracle Data Integrator usernames and passwords required by the Java EE components to connect the repositories are not stored in ODI Configuration files. This
information is stored in the Application Server credential store. When they need to authenticate to the repository, the ODI Java EE components refer to credential store
entries, identified by a map named by default oracle.odi.credmap and a key.
Note: Default templates contain the following datasources for
connecting the repositories: jdbcodiMasterRepository and jdbcodiWorkRepository. These JNDI names are referred to in
the default Run-time Agent or Oracle Data Integrator Console templates. If you use a generated agent template, the datasources
included in this template will be those declared in the topology for this agent. This template will also optionally contain the driver files.
