This chapter describes how to install and configure Oracle Data Integrator. Post-installation configuration parameters are also provided.
The following topics are covered:
Section 2.4, "Manual Configuration Tasks for ODI Studio, Repositories, and Standalone Agent"
Section 2.5, "Manual Configuration Tasks for Java EE Components"
Review the information in this section before you begin:
Create ODI Repositories with the Repository Creation Utility (RCU)
Install Oracle WebLogic Server and Create the Middleware Home
Before installing any Oracle Data Integrator (ODI) components, you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements. Both of these documents are available on Oracle Technology Network (OTN).
The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:
http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm
The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Note:
If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.If you are using a 64-bit Java Virtual Machine (JVM) in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.
Refer to the Oracle Fusion Middleware Certifications matrix for information on the platforms that support a 64-bit JDK:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK. For 32-bit JVM support, refer to the Oracle Fusion Middleware Release Notes for information on how to configure your environment for 32-bit JVM support for your platform.
For the latest information about supported databases, visit the following URL:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
This section provides a brief overview of using the Repository Creation Utility (RCU). For more information, for detailed information, see Oracle Fusion Middleware Repository Creation Utility User's Guide.
Oracle Data Integrator stores information in a repository that is stored in a database schema. The Repository Creation Utility (RCU) is able to create the schema and the repository in the database. RCU supports Oracle, Microsoft SQL Server and IBM DB2, and supports the installation of a Master Repository and Work Repositories into a single schema.
You can also use ODI Studio to manually create repositories. See Appendix G, "Creating Repositories with Oracle Data Integrator Studio".
Caution:
Due to the intensive communication that exists between ODI components and the repositories, Oracle recommends that you co-locate the repositories and the other ODI components on the same LAN, and not on remote sites.Follow these instructions to create the schemas using RCU:
Insert the RCU CD-ROM and start RCU from the bin
directory:
On UNIX operating systems:
./rcu
On Windows operating systems:
rcu.bat
You can also download a .zip
file containing RCU from Oracle Technology Network (OTN):
http://www.oracle.com/technology/
Provide the required information on each of the screens as described in "Repository Creation Utility Screens" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
On the Select Components screen, select the components whose schemas you want to install. For Oracle Data Integrator, expand Oracle Data Integrator and select Master and Work Repository as shown in Figure 2-1. The Select Components screen is described in detail in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
Figure 2-1 Repository Creation Utility Select Components Screen
On the Custom Variables screen, provide the following information as shown in Figure 2-2:
Note:
This version of Repository Creation Utility (RCU) does not perform extensive validation on the user entries of Repository ID and Repository Type.Master Repository ID values must be between 0 and 999 and Work Repository ID values must be between 0 and 999. Repository Type value must be either D (Development) or P (Production).
When incorrect values are entered for either of these, RCU fails during the repository creation process with the following error:
RCU-6135: Error while trying to execute Java action
If you receive this error, go back to the Repository Creation Utility Custom Variables Screen and provide the correct values.
Figure 2-2 Repository Creation Utility Custom Variables Screen
Click Next to continue through the remaining screens as described in "Repository Creation Utility Screens" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
The Oracle Data Integrator Java EE components require an Oracle WebLogic Server on your system. If you want to use Oracle Data Service Integrator in a Java EE deployment, you must install and configure the Oracle WebLogic server.
For information on installing the Oracle WebLogic Server, see "Preparing for Installation" and "Running the Installation Program in Graphical Mode" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
This section contains information and instructions for installing Oracle Data Integrator:
Section 2.2.4, "Installation Instructions for "Developer" Install Type"
Section 2.2.5, "Installation Instructions for "Standalone" Install Type"
Section 2.2.6, "Installation Instructions for "Java EE" Install Type"
Note:
If you are installing on a UNIX system for the first time, you may be asked to run theORACLE_HOME
/oracleRoot.sh
script as root
user to create all of the necessary installation directories.The Oracle Universal Installer requires a Java Development Kit (JDK) which provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. You must specify the directory that contains the software for the Sun JDK if it is installed with your software.
Tip:
If you installed Oracle WebLogic Server (Section 2.1.5, "Install Oracle WebLogic Server and Create the Middleware Home"), a JRE was installed on your system. You can use this location (the location of the JRE directory) to start the installer.On UNIX operating systems, the default location for the JRE is MW_HOME/jdk16
x, where MW_HOME
is the Middleware Home directory and jdk1.6_
x is the complete filename of the installed JDK.
On Windows operating systems, the default location for the JRE is MW_HOME\jdk16x, where MW_HOME
is the Middleware Home directory and jdk1.6_
x is the complete filename of the installed JDK.
On 64-bit platforms, the JRE location is the JAVA_HOME
you used to install Oracle WebLogic Server.
For more information, refer to Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
To start the installer, insert the CD-ROM and run the following command:
On UNIX operating systems:
./runInstaller -jdkLoc JDK_LOCATION
On Windows operating systems:
setup.exe -jdkLoc JDK_LOCATION
Note:
The minimum JDK required for Oracle Data Integrator is JDK 1.6. Refer to the Oracle Fusion Middleware Certification documentation to see the JDKs supported for your system:http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
The installer writes logs files to the OraInventory
/log
directory (on UNIX operating systems) or Oracle_Inventory_Location
\logs
(on Windows operating systems) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc
file in the following directories (default locations):
Linux: <ODI_HOME>/oraInst.loc
HP-UX and Solaris: /var/opt/oracle/oraInst.loc
Windows operating systems: C:\Program Files\Oracle\Inventory\logs
The Oracle Data Integrator installer provides three installation options:
Installation Instructions for "Developer" Install Type
The Developer installation includes the ODI Studio and the Oracle Data Integrator Software Development Kit (SDK).
Note that the Developer installation does not include the Standalone Agent or the scripts for managing sessions or scenarios from the command line. If a Standalone Agent will be needed, choose the Standalone install type in addition to the Developer install type.
Installation Instructions for "Standalone" Install Type
The Standalone installation includes an Oracle Data Integrator standalone agent.
Installation Instructions for "Java EE" Install Type
The Java EE installation includes the Java EE agent, Oracle Data Integrator Console, and Public Web Services.
Follow the instructions in Table 2-1 to install and configure Oracle Data Integrator when the Developer Installation is selected.
If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Data Integrator Installation Screens" or click Help to access the online help.
Table 2-1 Developer Installation Flow
No. | Screen | When Does This Screen Appear? | Description and Action Required |
---|---|---|---|
1 |
Always |
Click Next to continue. |
|
2 |
Always |
Select Developer Installation. By default, ODI Studio (with local agent) is selected. Oracle recommends that you also select the ODI SDK with the Developer Installation. Click Next to continue. |
|
3 |
Always |
Click Next to continue. |
|
4 |
Always |
Enter the absolute path for the Oracle home location (referred to later in this guide as NOTE - The specified directory must be an empty directory or an existing Oracle Data Integrator home location. Click Next to continue. |
|
5 |
Always |
Select whether you want to configure the Oracle Data Integrator Studio and the Standalone Agent with an existing Master and Work Repository pair. NOTE - If you choose to Skip Repository Configuration, you will have to configure the Oracle Data Integrator Studio and Standalone Agent manually as described in Section 2.4. Click Next to continue. |
|
6 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Specify the connection string to the database that hosts the Master Repository and the database user name and password Click Next to continue. |
|
7 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Specify the password for the ODI Click Next to continue. |
|
8 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Select an existing Work Repository from the list. Click Next to continue. |
|
9 |
Always |
Choose how you want to be notified about security issues:
|
|
10 |
Always |
Verify the information on this screen. Click Install to begin the installation. |
|
11 |
Always |
Click Next to continue. |
|
12 |
Always |
Click Next to continue. |
|
13 |
Always |
Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time. After saving your configuration information, click Finish to dismiss the installer. |
Follow the instructions in Table 2-2 to install and configure Oracle Data Integrator when the Standalone Installation is selected.
If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Data Integrator Installation Screens" or click Help to access the online help.
Table 2-2 Standalone Agent Installation Flow
No. | Screen | When Does This Screen Appear? | Description and Action Required |
---|---|---|---|
1 |
Always |
Click Next to continue. |
|
2 |
Always |
Select Standalone Installation. This installs the ODI Standalone Agent and the command line scripts. Click Next to continue. |
|
3 |
Always |
Click Next to continue. |
|
4 |
Always |
Enter the absolute path for the Oracle home location (referred to later in this guide as NOTE - The specified directory must be an empty directory or an existing Oracle Data Integrator home location. Click Next to continue. |
|
5 |
Always |
Select whether you want to configure with a connection to existing Master and Work Repositories or skip the repository configuration. NOTE - If you choose to Skip Repository Configuration, you can manually edit the Click Next to continue. |
|
6 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Specify the connection string to your database and the database user name and password. Click Next to continue. |
|
7 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Specify the password for the ODI Supervisor user. The default user name is Click Next to continue. |
|
8 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Select an existing Work Repository from the list. Click Next to continue. |
|
9 |
Only if Standalone Agent is selected on the Select Installation Type Screen and Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen. |
Enter the Agent Name and Agent Port number. The name cannot be the same as another agent already declared in the topology. NOTE - Agent Name can be 5 to 30 characters long, must begin with an alphabetic character, and may contain only alphanumeric characters and underscores (_). Click Next to continue. |
|
10 |
Always |
Choose how you want to be notified about security issues:
|
|
11 |
Always |
Verify the information on this screen. Click Install to begin the installation. |
|
12 |
Always |
Click Next to continue. |
|
13 |
Only if Configure with existing Master and Work Repositories is selected on the Repository Configuration Screen |
Click Next to continue. |
|
14 |
Always |
Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time. After saving your configuration information, click Finish to dismiss the installer. |
Follow the instructions in Table 2-3 to install and configure Oracle Data Integrator when the Java EE Installation is selected.
If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Data Integrator Installation Screens" or click Help to access the online help.
Table 2-3 Java EE Installation Flow
No. | Screen | When Does This Screen Appear? | Description and Action Required |
---|---|---|---|
1 |
Always |
Click Next to continue. |
|
2 |
Always |
Select Java EE Installation. This installation type includes the Java EE agent, Oracle Data Integrator Console, and Public Web Services. Click Next to continue. |
|
3 |
Always |
Click Next to continue. |
|
4 |
Always |
Specify the Middleware Home and Oracle home location (Oracle home is referred to later in this guide as ODI_HOME). The Oracle Data Integrator home location must be inside the Oracle Middleware Home directory and the WebLogic Server must already be installed in the same Oracle Middleware Home. For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide. Click Next to continue. |
|
5 |
Always |
Select Skip Repository Configuration. Click Next to continue. |
|
6 |
Always |
Choose how you want to be notified about security issues:
|
|
7 |
Always |
Verify the information on this screen. Click Install to begin the installation. |
|
8 |
Always |
Click Next to continue. |
|
9 |
Always |
Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time. After saving your configuration information, click Finish to dismiss the installer. |
After the installation is complete, you must configure managed servers in your ODI domain to work with the Oracle Data Integrator Java EE components. The Oracle Fusion Middleware Configuration Wizard can be used to automate many of these tasks. Once the domain has been configured, see the following for additional information:
To start the Configuration Wizard in graphical mode from a Windows command prompt or on UNIX systems:
Log in to the system on which the product is installed.
Open an MS-DOS command prompt window (on Windows operating systems) or a command shell (on UNIX operating systems).
Go to the following directory:
On UNIX operating systems:
ODI_HOME/common/bin
On Windows operating systems:
ODI_HOME\common\bin
Execute the following command:
On UNIX operating systems:
sh config.sh
On Windows operating systems:
config.cmd
Provide the required information on the Oracle Fusion Middleware Configuration Wizard as described in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
The Select Domain Source screen shown in Figure 2-3 lists the ODI-specific components that may be configured based on your installation. You may also choose to Extend an Existing Domain with Oracle Data Integrator components. When you extend an existing domain, only those products which have not been configured in the domain will be available.
Figure 2-3 Fusion Middleware Configuration Wizard Select Domain Source Screen
Oracle Data Integrator Products | Dependency |
---|---|
Oracle Enterprise Manager Plugin for ODI | Oracle Enterprise Manager must be installed in the same domain. |
Oracle Data Integrator SDK Web Services | Oracle JRF |
Oracle Data Integrator Console | Oracle JRF |
Oracle Data Integrator Agent | Oracle JRF |
Note:
If ODI Java EE components were installed, they automatically appear in the Oracle Fusion Middleware Configuration Wizard when launched to create a new domain. If dependencies exist, they are managed by the Oracle Fusion Middleware Configuration Wizard automatically.Also note that if you select MDS while creating or extending an ODI domain, there is no dependency on Oracle WSM Policy Manager 11.1.1.0.
For more information on creating and configuring a WebLogic domain, see Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
When you finish creating your domain, you can start the Administration Server. To start an Administration Server that you have created, invoke the following:
On UNIX operating systems:
DOMAIN_NAME
/bin/startWebLogic.sh
On Windows operating systems:
DOMAIN_NAME
\bin\startWebLogic.cmd
where DOMAIN_NAME
is the name of the directory in which you located the domain, typically MW_HOME
\user_projects\domains\
DOMAIN_NAME
.
On Windows operating systems, the Configuration Wizard creates a shortcut on the Start menu to start the Administration Server that you created (User Projects > DOMAIN_NAME
> Start Admin Server for WebLogic Domain).
If the server prompts you to enter a username and password, enter the name of a WebLogic Server user who has permission to start servers. For more information, see "Provide User Credentials to Start and Stop Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.
NOTE: In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly on the Administration Server. In a production environment, you typically create Managed Servers to run applications.
For more information on the various methods you can use to start the Administration Server, see "Starting and Stopping Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.
To start the Managed Server, run the startManagedWebLogic.sh
(on UNIX operating systems) or startManagedWebLogic.cmd
(on Windows operating systems) script in the /bin
directory inside the directory where you created your domain. These managed servers must be started from the command line.
This command also requires that you specify a server name. The server that needs to be started is:
odi_server1
(Oracle Data Integrator Server)
For example, to start ODI Server on a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh odi_server1
On Windows operating systems:
MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd soa_server1
Before the managed server is started, you will be prompted for the WebLogic Server user name and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard. See Oracle Fusion Middleware Creating Domains Using the Configuration Wizard for more information.
The following manual steps may be required for specific component installations:
ODI installation includes a set of DataDirect drivers for the following technologies: Oracle, Hypersonic SQL, SQL Server, Sybase ASE, and DB2 UDB. If additional drivers and open tools are needed, they must be added to the Standalone Agent and the ODI Studio in the following directories:
On UNIX/Linux operating systems:
USER_HOME/.odi/oracledi/userlib
This folder contains the additional_path.txt
file that allows you to declare additional files or folders outside of the /userlib
directory from which the ODI Studio acquires its libraries and drivers.
Standalone Agent
ODI_HOME/oracledi/agent/drivers/
On Windows operating systems:
%APPDATA%\odi\oracledi\userlib
%APPDATA% is the Windows Application Data directory for the user (usually C:\Documents and Settings\<user>\Application Data).
Standalone Agent
ODI_HOME\oracledi\agent\drivers
Note:
The ODI 11gR1 installation does not include JDBC drivers for the PostgreSQL database. To use PostgreSQL, you must downloadpostgresql-8.4-701.jdbc4.jar
from http://jdbc.postgresql.org/download.html
and then follow the instructions above.If repository creation was not possible through RCU due to unsupported technology or repository topology, use ODI Studio to create and configure repositories.
For detailed instructions see Appendix G, "Creating Repositories with Oracle Data Integrator Studio".
If the repository connections were not configured during installation, use ODI Studio to create the connections to the repositories.
For detailed instructions see Appendix G, "Creating Repositories with Oracle Data Integrator Studio".
During the Standalone Agent installation, the agent is pre-configured to connect the existing repository. If the Skip Repository Configuration option was selected on the Repository Configuration screen, then the agent is installed but not configured.
Connect to the Master Repository and define a physical agent in the topology for the standalone agent, with the following information:
Name - Name of the physical agent.
Host - Name of the host where the standalone agent will be started.
Port - Port on this host where the standalone agent will be started. Provide a port number between 1024 and 65535 that is not currently being used by any other Oracle home. This port defaults to 20910.
Web Application Context: oraclediagent
(This parameter cannot be changed for a standalone agent.)
See Also:
For detailed instruction on declaring an agent in the topology, refer to "Creating a Physical Agent" in Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.Configure the agent manually by editing the odiparams.bat/sh
file to point to the correct repository. The odiparams
file is pre-configured if you installed your standalone agent using Oracle Universal Installer and selected to configure a repository connection during installation. See Table 2-4 for the list of these parameters.
Table 2-4 Repository Connection Information
Parameter | Description |
---|---|
|
JDBC driver used to connect the Master Repository. |
|
JDBC URL used to connect the Master Repository. |
|
Database account used to connect the Master Repository. |
|
Database account password. The password must be encoded with the |
|
Name of the Work Repository to connect to. This Work Repository is the default repository into which the scenarios are started. |
|
Name of an ODI supervisor user. This Supervisor user is used by the agent to connect the Master Repository. |
|
This user's password. The password must be encoded with the |
|
Name of an ODI user used to start scenarios. This user's credentials are used when starting a scenario from a command line. |
|
This ODI user password |
|
The number of retries to establish the connection in the event that a repository connection fails. If set to 0, no retry will be performed. Default is 10. NOTE: The |
|
Time in milliseconds between repository connection retries. Default is 1000. |
The following example shows a modified odiparams.bat/sh
file:
ODI_MASTER_DRIVER=oracle.jdbc.driver.OracleDriver ODI_MASTER_URL=jdbc:oracle:thin:@ours:1521:ORA9 ODI_MASTER_USER=ODI_11G ODI_MASTER_ENCODED_PASS=gxfpqkz074jeaCpL4XSEFzxoj8E0p ODI_SECU_WORK_REP=WORKREP ODI_SUPERVISOR=SUPERVISOR ODI_SUPERVISOR_ENCODED_PASS=fJya.vR5kvNcu9TtV,jVZEt
See Also:
For more information on how to work with a standalone agent, a Java EE agent and how to handle load balancing, see "Managing Agents" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.Once the standalone agent has been defined in Topology, it can be started and used to execute scenarios on predefined schedules or on demand.
To launch a standalone agent:
Change directory to the /agent/bin
directory of the Oracle Data Integrator Agent.
Enter the following command to start the agent.
On UNIX system:
./agent
On Windows system:
agent.bat
Agent Configuration Parameters
Table 2-5 lists the different parameters that allow the agent to be configured. The parameters are prefixed by the "-" character and the possible values are preceded by the "=" character. When entering the command, consider the operating system specific syntax of the delimiters.
Table 2-5 Agent Configuration Parameters
Parameters | Description |
---|---|
|
Port on which the agent is listening. Default value is 20910. This port should exactly match the port specified in the physical agent definition in the topology. |
|
This is the name of the physical agent used. This name should match the name of the physical agent as defined in the topology. If this parameter is not specified, the agent starts with the default name OracleDIAgent. |
|
JMX agent port number. The agent listens on this port for JMX request to provide its metrics. Default value is the listening port + 1000. For example, if |
For example, on UNIX, the following command launches the standalone agent declared in the repository as agent_001
on the port 20300
.
./agent.sh -PORT=20300 -NAME=agent_001
WARNING:
On Windows platforms, it is necessary to "delimit" the command arguments containing "=" signs or spaces, by using double quotes. For example:
agent.bat "-PORT=20300" "-NAME=agent_001
"
This section provides post-installation steps for Java EE Agent, Oracle Data Integrator Console and Oracle Enterprise Manager.
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.
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.
In Topology Navigation, connect to the Master Repository and declare the Java EE agent and provide the following:
Name - Name of the physical agent.
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 Developer's Guide for Oracle Data Integrator.
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 Section 4.3.2, "Java EE Agent" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
Note:
Default templates contain the following datasources for connecting the repositories:jdbc/odiMasterRepository
and jdbc/odiWorkRepository
. 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.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.
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:
Navigate to the ODI_HOME/common/bin
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.
Launch wlst
.
On UNIX operating systems:
./wlst.sh
On Windows operating systems:
wlst.bat
Execute the following WLST command substituting your usernames and passwords:
connect('weblogic','welcome1','t3://localhost:7001') createCred(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR", password="supervisor1", desc="Key for Supervisor") disconnect()
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:
createCred(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR", password="******", desc="Key for Supervisor") createCred(map="oracle.odi.credmap", key="base_domain", user="weblogic", password="*******", desc="Username and password for base_domain")
Example Scenario:
Three agents OdiAgent1, OdiAgent2 and OdiAgent3 are defined as physical agents in the topology.
OdiAgent1 and OdiAgent2 are Java EE agents and OdiAgent3 is a Standalone agent.
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.
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:
createCred(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR", password="SUPERVISOR", desc="Key for Supervisor") createCred(map="oracle.odi.credmap", key="agent_1_domain", user="weblogic", password="*****", desc="Username and password for agent_1_domain") createCred(map="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.
The Oracle Data Integrator Console template is created (by default) with two connections aliases:
Work Repository connects a Work Repository after the two default datasources jdbc/odiMasterRepository
and jdbc/odiWorkRepository
.
Master Repository connects a Master Repository after the default datasource jdbc/odiMasterRepository
.
If more repository connections are required, either to access these repositories from ODI Console or to monitor them from Oracle Enterprise Manager, add the connections from the ODI Console interface.
To add new connections to ODI Console:
Start the Oracle Data Integrator Console application.
Open the Management tab. Connect to ODI Console (with an existing repository connection) as a user who has supervisor privileges. Select the Management tab.
If you have not yet configured a connection, a link to the Management tab appears at the top right corner of the login screen.
Navigate to the Repository Connections node in the Management Navigation tab.
Click Create in the Navigation tab toolbar. A Create Repository Connection dialog for this object appears.
Provide the values for the repository connection:
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: jdbc/odiMasterRepository
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 user's 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:comp/env/
to identify it in the application server's JNDI directory. Note that the JNDI Standard is not supported by Oracle WebLogic Server or for global data sources.
For example: jdbc/odiWorkRepository
Default: Check this option if you want this Repository Connection to be selected by default on the login page.
Click Save. The new Repository Connection appears in the Management Navigation tab.
See "Performing Administrative Operations" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator for more information about creating repository connections.
To use Oracle Enterprise Manager with the Oracle Data Integrator Console, you must first configure the following:
Create the appropriate Credential Store Entries for Oracle Enterprise Manager as described in Section 2.5.3.
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:
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_HOME/config/oracledi/config.properties
.
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.
Any agent on the domain will appear in the domain with its status and will start posting notifications (if started).
If you want Oracle Enterprise Manager to drill down into Oracle Data Integrator Console using a different URL (host:port/application_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 Administrator's Guide.