Before you continue, make sure that you have completed the Enterprise Installation install type (Chapter 2). This install type contains ODI Studio, and also the necessary files to create and configure a WebLogic Domain.
The following topics are covered:
Before you can configure the topology for your Java EE agent, make sure you have created the necessary schema in your database. See Chapter 3 for instructions.
This section provides instructions for creating a WebLogic domain for your Java EE agent using the configuration wizard. For more information on other methods available for domain creation, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating WebLogic Domains Using the Configuration Wizard.
The following topics are covered in this section:
To begin domain configuration, navigate to the
/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.
On UNIX operating systems:
On Microsoft Windows operating systems:
Follow the instructions in this section to create and configure the domain for the topology.
You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain creation and configuration includes the following tasks:
On the Configuration Type screen, select Create a New Domain.
In the Domain Location field, specify your Domain home directory.
It is recommended that you locate your Domain home in accordance with the directory structure summarized in "Understanding the Recommended Directory Structure" in Planning an Installation of Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle Enterprise Manager Plugin for ODI - 126.96.36.199 [em]]
Selecting this template automatically selects the following as dependencies:
Oracle Enterprise Manager - 188.8.131.52 [em]
Oracle JRF - 184.108.40.206 [oracle_common]
WebLogic Coherence Cluster Extension - 220.127.116.11 [wlserver]
Oracle Data Integrator - Agent - 18.104.22.168 [odi]
Selecting this template automatically selects the following as dependencies:
Oracle Data Integrator - Agent Libraries - 22.214.171.124 [odi]
Oracle Data Integrator SDK Shared Library Template - 126.96.36.199 [odi]
Oracle Data Integrator - Console - 188.8.131.52 [odi]
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
On the Application Location screen, select the location where you want to store your applications associated with your domain. This location is also referred to as the Application home directory.
It is recommended that you locate your Application home in accordance with the directory structure summarized in "Understanding the Recommended Directory Structure" in Planning an Installation of Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or re-install your software.
More information about the Application home directory can be found in "Choosing an Application Home" in Planning an Installation of Oracle Fusion Middleware.
More information about the options on this screen can be found in Application Location in Creating WebLogic Domains Using the Configuration Wizard.
On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.
It is recommended that you make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.
On the Domain Mode and JDK screen:
Select Production in the Domain Mode field.
Select the Oracle HotSpot JDK in the JDK field.
More information about the options on this screen can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.
Select RCU Data to activate the fields on this screen. The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.
If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the JDBC Component Schema screen.
After selecting RCU Data, fill in the following fields:
Enter the database DBMS name, or service name if you selected a service type driver.
Enter the name of the server hosting the database.
Enter the port number on which the database listens.
Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Section 4.1, "Creating the Database Schema").
The default username is
Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
More information about the RCU Data option can be found in "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard
Verify that the values on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
More information about the other options on this screen can be found in JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema Test screen to test the datasource connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard
Use the Credentials screen to create the following two keys:
A key for the Supervisor user already exists. Modify the credential as follows:
Specify SUPERVISOR (all CAPS) as the user name. This is the default name initially assigned to the Supervisor account and cannot be changed unless you create a new Supervisor account.
Create a second credential as follows:
Click the Plus sign (+) icon to add a new credential.
In the Key Name field, enter the name of this domain as the key.
In the Username and Password fields, provide the Administrator user's user name and password.
oracle.odi.credmap as the store name.
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
This is required to properly configure the listen address of the Administration Server.
This is required to configure Node Manager.
Managed Server, Clusters and Coherence
This is required to configure the Oracle Data Integrator Managed Server.
On the Administration Server screen, select the drop-down list next to Listen Address and select the IP address on the host where the Administration Server will reside. Do not use "All Local Addresses."
Do not specify any server groups for the Administration Server.
The Node Manager screen can be used to select the type of Node Manager you want to configure, along with the Node Manager credentials.
Select Per Domain as the Node Manager type, then specify the Node Manager credentials.
On the Managed Servers screen, a new Managed Server named
ODI_server1 is created:
In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside. Do not use "All Local Addresses."
In the Server Groups drop-down list, select JRF-MAN-SVR. This server group ensures that the Oracle JRF services are targeted to the Managed Servers you are creating.
Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.
These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.
You must make a note of the IP address and port number for the Managed Server. You will need this information when you configure the ODI agent.
More information about the options on this screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Use the Clusters screen to create a new cluster:
Click the Add button.
ODI_cluster1 in the Cluster Name field.
Leave the cluster Address field blank.
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
New clusters can also be created using Fusion Middleware Control. In such cases, cluster communication (unicast or multicast) can be configured when the new cluster is created. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Clusters screen to assign
ODI_server1 to the new cluster
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
In the Servers pane, assign
ODI_cluster1 by doing one of the following:
Click once on
ODI_server1 to select it, then click on the right arrow to move it beneath the selected cluster (
ODI_cluster1) in the Clusters pane.
ODI_server1 to move it beneath the selected cluster (
ODI_cluster1) in the clusters pane.
More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the default port number 0 as the Coherence cluster listen port.
Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that can be assigned to a Managed Server port number is 60535, instead of 65535.
See Table 7-2 for more information and next steps for configuring Coherence.
For Coherence licensing information, refer to "Oracle Coherence" in Licensing Information.
Use the Machines screen to create a new machine in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.
If you plan to create a high availability environment and know the list of machines required for your target topology, you can follow the directions in this section to create all of the machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.
Click the Add button to create a new machine.
ODI_machine1 in the Name field.
In the Node Manager Listen Address field, select the IP address of the machine where the Managed Servers are being configured.
You must select a specific interface and not "localhost." This allows Coherence cluster addresses to be dynamically calculated.
Verify the port in the Node Manager Listen Port field.
The port number
5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.
If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.
More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Server to the new machine you just created:
In the Machines pane, select the machine to which you want to assign the servers; in this case,
In the Servers pane, assign
ODI_machine1 by doing one of the following:
Click once on
AdminServer to select it, then click on the right arrow to move it beneath the selected machine (
ODI_machine1) in the Machines pane.
AdminServer to move it beneath the selected machine (
ODI_machine1) in the Machines pane.
Repeat to assign
More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Create.
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen will show the Domain home location and URL of the Administration Server you just configured:
You must make a note of both items as you will need them to start the servers in your domain.
Click Finish to dismiss the configuration wizard.
A physical agent corresponds to a single standalone agent or a Java EE agent. A physical agent should have a unique name in the topology.
As part of its startup sequence, an agent connects to the Master Repository to see if there is a physical agent defined with its name. If it finds its entry, the agent continues with startup and, once started, it reads all the scheduled jobs of itself from the repository and starts processing.
If there is no physical agent entry for an agent, then the agent startup fails.
ODI Studio can be used to create the agent:
To start the ODI Studio:
Go to the Oracle home where you have installed Oracle Fusion Middleware Infrastructure and the Enterprise Installation type.
Inside that Oracle home, go to the
Start ODI Studio.
On UNIX operating systems:
On Windows operating systems:
Before an agent can be created you must connect to the Master repository:
If you have installed any previous version of Oracle Data Integrator on the same computer you are currently using, you may be asked whether or not you want to import preferences and settings from those previous installations into ODI Studio. The tasks and descriptions in this section assume that no previous versions of Oracle Data Integrator exist on your computer.
For more information, refer to the topics in the ODI Studio Help menu.
From the ODI Studio menu, select File, then select New.
On the New gallery screen, select Create a New ODI Repository Login, then click OK.
On the Oracle Data Integrator Login screen, click the plus sign (+) icon to create a new login. On the Repository Connection Information screen:
Oracle Data Integrator Connection section:
Login Name: Specify a custom login name.
SUPERVISOR (all CAPS).
Password: Specify the password defined for the Supervisor user on both the RCU Custom Variables screen and also the Credentials screen in the Configuration Wizard.
Database Connection (Master Repository) section
User: Specify the schema user name for the Master repository. This should be
_ODI_REPO as specified on the Select Components screen in RCU.
Password: Specify the schema password for the Master repository. This was specified on the Schema Passwords screen in RCU.
Driver List: Select the appropriate driver for your database from the drop-down list.
URL: Specify the connection URL. Click on the magnifying glass icon for more information about the connection details for your driver.
In the Work Repository section, select Master Repository Only.
Click Test to test the connection, and fix any errors. After the test is successful, click OK to create the connection.
If you want to keep your Oracle Data Integrator and repository passwords encrypted, select Store passwords in secure wallet, then specify and confirm a new wallet password on the New Wallet Password screen.
If you do not want to encrypt your credentials, select Store passwords without secure wallet.
After you have successfully created a new login, you are returned to ODI Studio.
Select Connect to Repository and, when prompted, provide your new wallet password.
After providing your wallet password, the Oracle Data Integrator Login screen appears. Provide the following information to log in:
In the drop-down menu in the Login Name field, select the name of the new login you just created.
SUPERVISOR as the user name.
Provide the password for the Supervisor user.
When you are logged in, follow the instructions in Section 4.3.3 to create the Java EE agent.
Follow the instructions in this section to create an ODI agent after you have connected to the repository in ODI Studio.
In the navigation pane on the left side, select the Topology tab, then right-click Agents, then select New Agent.
Specify the new agent details as summarized in the following table:
Enter the IP address or name of the machine where the agent is running. Do not use "localhost."
Enter the port number on which the agent listens.
If your environment includes a cluster with Oracle HTTP Server acting as a front-end to the cluster, you should provide the host name and port of the Oracle HTTP Server host instead.
From the ODI Studio menu, select File, then select Save All to save your changes.
After configuration is complete, do the following to access the tools with which you can manage your domain:
For more information on additional tools you can use to manage your domain, see "Overview of Oracle Fusion Middleware Administration Tools" in Administering Oracle Fusion Middleware.
To start your per-domain Node Manager, go to the
On UNIX operating systems, start the Node Manager as shown below, using
nm.out as an example output file:
nohup ./startNodeManager.sh > nm.out&
On Windows operating systems, run:
On Windows operating systems, it is recommended that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.
For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.
For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
To start the Administration Server, go the
On UNIX operating systems, run:
On Windows operating systems, run:
If you selected Production Mode on the Domain Mode and JDK screen in Task 5, you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in Task 4.
For more information about starting the Administration Server, see "Starting and Stopping Administration Servers" in Administering Oracle Fusion Middleware.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
You can verify that the Administration Server is up and running by access the Administration Server Console. The URL is provided on the Configuration Success screen in Task 20.
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
The default Administration Server port number is
For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.
To start the Managed Server:
Login to Oracle Fusion Middleware Control:
The Administration Server host and port number were in the URL on the Configuration Success screen (Task 20). The default Administration Server port number is
The login credentials were provided on the Administrator Account screen (Task 4).
From the "Target Navigation" pane, click the arrows to expand the domain until the Managed Servers (
ODI_server1) is visible.
In the Target Navigation page, select your domain name to see that all the servers are up and running.
More information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware Control can be found in Administering Oracle Enterprise Manager Fusion Middleware Control.
Section 7.1 contains basic administration tasks. You should familiarize yourself with the tasks described in this section and perform them as needed to verify that your domain is properly configured.
Section 7.2 contains additional domain configuration tasks that take advantage of additional Oracle Fusion Middleware products and features.
Section 7.3 contains common tasks to help prepare your Oracle Data Integrator environment for development.
Section 7.4 contains important tasks to help prepare your environment to move to a highly available environment.