Configuring Oracle Data Integrator 3-11
■
Connection Alias : Name of the connection that will appear on the Login page.
■
Master JNDI URL : JNDI URL of the datasource to connect the master
repository database. For example: jdbcodiMasterRepository
■
Supervisor User Name : Name of the Oracle Data Integrator user with
Supervisor privileges that Oracle Data Integrator Console will use to connect to the repository. This users password must be declared in the WebLogic
Server Credential Store.
■
Work JNDI URL : JNDI URL of the datasource to connect the work repository
database. If no value is given in this field, the repository connection will allow connection to the master only, and the Navigation will be limited to Topology
information.
■
JNDI URL : Check this option if you want to use the Environment Naming
Context ENC. When this option is checked, Oracle Data Integrator Console automatically prefixes the data source name with the string
java:compenv to identify it in the application servers JNDI directory. Note that the JNDI Standard is not supported by Oracle WebLogic Server or
for global data sources.
For example: jdbcodiWorkRepository
■
Default : Check this option if you want this Repository Connection to be
selected by default on the login page.
6. Click Save. The new Repository Connection appears in the Management
Navigation tab. See Performing Administrative Operations in the Oracle Fusion Middleware
Developers Guide for Oracle Data Integrator for more information about creating repository connections.
3.3.5 Configure Oracle Enterprise Manager
To use Oracle Enterprise Manager with the Oracle Data Integrator Console, you must first configure the following:
1.
Create the appropriate Credential Store Entries for Oracle Enterprise Manager as described in
Section 3.3.3 .
2.
Set the following property before starting the managed server on which Oracle Data Integrator Console is deployed.
set JAVA_OPTIONS=-Doracle.odi.repex.view.main.init.skipem=false Domain discovery is performed with the following process:
1.
Oracle Enterprise Manager finds the Oracle Data Integrator Console configuration file storing the Repository Connection repositories.xml in the location specified
in the configuration file DOMAIN_ HOMEconfigoraclediconfig.properties.
2.
Oracle Enterprise Manager parses the repository connections declared in Oracle Data Integrator Console, tries to connect all the masters and retrieves their status
and list of agents. Even if an agent or repository is down, it will appear in the Oracle Enterprise Manager.
3.
Any agent on the domain will appear in the domain with its status and will start posting notifications if started.
3-12 Oracle Fusion Middleware Installation Guide for Oracle Data Integrator
If you want Oracle Enterprise Manager to drill down into Oracle Data Integrator Console using a different URL host:portapplication_name than the one detected by
Oracle Enterprise Manager, you will need to reconfigure this in Oracle Enterprise Manager. Re-configuration is not mandatory, but may be needed when using a
firewall for HTTP load balancing to Oracle Data Integrator Console. For more information on using Oracle Enterprise Manager, see the Oracle Fusion Middleware
Administrators Guide.
