ODI11g - Deploying and Configuring The ODI Agent As A Java EE Application
ODI11g - Deploying and Configuring The ODI Agent As A Java EE Application
1 of 22
Purpose
This tutorial walks you through the steps that are needed to deploy and configure an Oracle Data Integrator (ODI) Java EE Agent
Time to Complete
Approximately 20 minutes
Overview
A common task that is performed using ODI is to deploy and configure an ODI Java EE Agent. With ODI 11g, the Runtime Agent can now be deployed as a Java
EE component within an application server. It benefits in this configuration from the application server layer features such as clustering and connection pooling for
large configurations. This Java EE Agent exposes an MBeans interface enabling lifecycle operations (start/stop) from the application server console and metrics
that can be used by the application server console to monitor the agent activity.
Scenario
Linda works as a database administrator for Global Enterprise. In Global Enterprise, Linda is responsible for performing database management and integration
tasks on various resources within the organization. In particular, Linda is responsible for data loading, transformation, and validation. To begin working on her
projects, Linda created the new Master repository and Work repository. Linda also created the project and the procedure to create a relational table and populate it
with data. Now Linda needs to deploy and configure an ODI Java EE Agent to be able monitor the agent activity via WebLogic server console.
Prerequisites
Before you start the tasks, make sure that your system environment meets the following requirements:
1 . Have installed Oracle Database 11g. If not done before, start the services and components for Oracle Database 11g
2 . Have installed Oracle Data Integrator 11gR1
3 . Before attempting this OBE, you should have successfully completed the following OBEs:
ODI11g: Creating and Connecting to ODI Master and Work Repositories
ODI11g: Creating an ODI Project: Developing an ODI XML to Database Transformation Using Interface with ODI
Constraint. Note: Alternatively you may have your own ODI interface created and used for testing ODI JEE agent
. In this case you don't have complete this OBE.
To access these OBEs, click HERE.
11/11/2014 1:54 PM
2 of 22
the Java EE Agent and its configuration, and can optionally include the JDBC datasources definitions required for this agent as well as the drivers and libraries files
for these datasources to work. By using the Oracle WebLogic Configuration Wizard, domain administrators can extend their domains or create a new domain for
the Oracle Data Integrator Java EE runtime agents. The ODI 11g Java EEAgent can be deployed to an existing domain or deployed automatically when creating a
new domain. For the purpose of this lab we will first create the WLS domain, and then extend the domain by depying the Java EE agent. Before creating an ODI
JEE agent, you create a new WLS domain, ODI-DOMAIN. To do so, perform the following steps:
1. To deploy and configure domains with WLS, you start the config.bat from within the ODI Home Install. Start
command shell and change directory to: <WLS-HOME>\common\bin, for example: C:\oracle\Middleware
\Oracle_ODI2\common\bin. Execute config command. The Configuration Wizard starts.
2. In Welcome screen, select Create a new WebLogic domain, and click Next. In the Select Domain Source screen, just
click Next.
11/11/2014 1:54 PM
3 of 22
3. In Specify Domain Name and Location screen, enter ODI-DOMAIN for Domain name. Leave default Domain
location. Click Next. In the screen that follows, enter Administrator user password: "welcome1". Leave User name as
"weblogic". Click Next. In the next screen, leave default location for available JDKs. Leave other default settings, as
shown on the screenshot and click Next.
11/11/2014 1:54 PM
4 of 22
4. In the Select Optional Configuration screen, select: Administration Server, Managed Servers, Clusters and Machines.
Click Next. In the screen that follows, verify that Listen port is set to 7001. Click Next. In the screen that follows, click
Add to add a new managed server. It will be used later to depoy ODI JEE agent.
11/11/2014 1:54 PM
5 of 22
5 . In the Configure Managed Server screen, in the Name field enter: odi_server1. In the Listen Port field, enter: 8001,
as shown on the screenshot. Click Next. In the screen that follows, click Next.
11/11/2014 1:54 PM
6 of 22
6 . In the Configure Machines screen, click Next. In Configuration Summary screen, click Create. When the domain is
created, click Done.
Note: Don't select "Start Admin server" yet. It will be done later.
11/11/2014 1:54 PM
7 of 22
11/11/2014 1:54 PM
8 of 22
Deploy and configure the ODI Java EE agent on the existing WebLogic domain, ODI-DOMAIN.
Now that you have created the WebLogic server domain ODI_DOMAIN, you need to deploy and configure ODI JEE agent with this domain.
1. If not started, start ODI and connect to ODI Work repository (WORKREP1). For user SUPERVISOR, eneter
password: SUNOPSIS. Open Topology Navigator, open Physical architecture and then create a new ODI Agent.
Name this agent OracleDIAgent. Set the port to 8001 and Host to localhost . Verify that the Web application context
is set to oraclediagent , as shown below. Save your new physical agent
Note: The agent name is case-sensitive! Use the exact name OracleDIAgent, as shown in the screenshot.
1 . In the Logical architecture, create a new logical agent with the same name as your new physical agent,
OracleDIAgent . Link this logical agent to the physical agent OracleDIAgent in Global context, as shown below. Save
logical agent OracleDIAgent, and close the tab.
11/11/2014 1:54 PM
9 of 22
2. Open the Command Prompt window again. If necessary, change directory to: <WLS-HOME>\common\bin. Execute
config command. The Configuration Wizard starts.
3. In the Welcome screen, select: Extend an existing WebLogic domain. Click Next. In the screen that follows, select
the domain ODI-DOMAIN, as shown on the screenshot. Click Next.
11/11/2014 1:54 PM
10 of 22
4 . In the screen that follows, select Oracle Data Integrator Agent 11.1.1.1 (Oracle JRF will then also be selected;
leave this option selected). Click Next. In the screen that follows, click OK to replace the existing component
odi_server1, that was created earlier.
11/11/2014 1:54 PM
11 of 22
5 . The wizard will set up the ODI repository connection within the domain server. During the wizard configuration, the
repository connection information must be supplied. Click the check boxes next to ODI Master schema, and next to
ODI Work schema. Configure the JDBC component schema as shown in the following table. Click Next. Verify that
the test was successful (if not, correct any connectivity settings). Click Next.
Database Connection (Master Repository)
Parameter
Value
Vendor
Oracle
Driver
Schema Owner
snpm1
Schema Password
oracle1
11/11/2014 1:54 PM
12 of 22
DBMS/Service
orcl
Host Name
localhost
Port
1521
6 . In the next screen, select Managed Servers, Clusters and Machines. Click Next. Verify that Listen port is set to
8001 for managed server odi_server1. Click Next. In the Configure Clusters screen, click Next.
11/11/2014 1:54 PM
13 of 22
7 . In the Configure Machines screen, click Next. The Assign Servers to Machines screen will already have the
odi_server1 assigned to localODImachine. Click Next. Review the Configuration Summary, and then click Extend.
When the domain is created, click Done.
11/11/2014 1:54 PM
14 of 22
11/11/2014 1:54 PM
15 of 22
2. Security must be set up for the JAVA EE application to have access to the ODI repository. The entry will be created
within the credential store, which will allow the JAVA EE Agent to authenticate itself to be able to use the required
resources. This user should be a user that is already set up in the ODI Security. In this practice, we use user
SUPERVISOR. To do this, you execute Web Logic Scripting Tool (WLST), connect to our running Admin server and
add the credential store. To start WLST, in the new command window, change directory to the WLS_HOME common
11/11/2014 1:54 PM
16 of 22
4 . Execute the following command to add the correct credential store for ODI Supervisor : createCred
(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR", password="SUNOPSIS", desc="ODI
SUPERVISOR Credential").
Note: All commands are case-sensitive! You can copy commands from the text file provided HERE.
11/11/2014 1:54 PM
17 of 22
5 . IAlso execute the command to add the correct credential store for the domain ODI-DOMAIN :
createCred (map="oracle.odi.credmap", key="ODI-DOMAIN", user="weblogic", password="welcome1",
desc="ODI-DOMAIN Credential").
To exit WLST, execute the command exit() .
11/11/2014 1:54 PM
18 of 22
11/11/2014 1:54 PM
19 of 22
7 . From ODI Designer, click Test icon to test connectivity of your configured ODI Java EE agent. Click OK. Close
OracleDIAgent tab.
11/11/2014 1:54 PM
20 of 22
2. Click the ODI Operator tab to open ODI Operator. In ODI Operator, click the Session List tab, and then click the
Refresh icon. Expand: Physical Agent > OracleDIAgent -1> PRD_CREATE_POPULATE_TABLE, and view the
execution results for the PRD-create-populate-table procedure. Verify that procedure PRD-create-populate-table
executed successfully.
11/11/2014 1:54 PM
21 of 22
3 . To stop managed WebLogic server odi_server1 and then WebLogic server, change directory to WLS Home C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin, and then execute the following command:
stopManagedWebLogic odi_server1. For Username, enter weblogic . For the password, enter welcome1 .
To stop WebLogic server, execute the command: stopWebLogic.
11/11/2014 1:54 PM
22 of 22
Summary
In this tutorial, you have learned how to:
Verify the Prerequisites
Deploy and configure the ODI Java EE agent on the WebLogic domain
Connect to WebLogic Admin server and Managed server
Test ODI java EE agent by executing an ODI object
Resources
Oracle Data Intergator 11g Documentation
To learn more about , refer to additional OBEs in the Learning Library.
11/11/2014 1:54 PM