Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Data Integrator
11g Release 1 (11.1.1.7.0)

Part Number E16453-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Installation Overview for Oracle Data Integrator

This chapter provides an overview of the Oracle Data Integrator (ODI) installation process including a description of the installable components, pre and post-installation tasks, and process flow.

The chapter includes the following topics:

1.1 Oracle Data Integrator Applications

Oracle Data Integrator includes the following applications:

1.2 ODI Installation Types

The Oracle Data Integrator installer provides the following installation options; you can select any combination of these options during the installation:

See Section 2.4, "Installing Oracle Data Integrator" for more information about installing the different ODI installation types.

1.3 Installation Roadmap

The process of installing and configuring Oracle Data Integrator includes these high-level tasks:

  1. Preparing your system environment for installation

  2. Creating schemas for applications

  3. Installing an Application Server and Oracle Fusion Middleware

  4. Installing Oracle Data Integrator

  5. Configuring Oracle Data Integrator

  6. Performing Postinstallation Configuration

  7. Verifying the Configuration

Figure 1-1 shows these steps in the installation process.

Figure 1-1 Roadmap for Installing and Configuring Oracle Data Integrator

Surrounding text describes Figure 1-1 .

Table 1-1 describes the high-level tasks for installing and configuring Oracle Data Integrator. The table also provides information on where to get more details about each task.

Table 1-1 Tasks in the Oracle Data Integrator Installation Procedure

Task Description More Information

Complete the installation planning requirements

Prior to installation you must prepare your system environment for installation. Review the general installation requirements for Oracle Fusion Middleware, as well as any specific configuration requirements for Oracle Data Integrator.

Section 2.1, "Verifying Your System and Network Environment"

For Oracle Data Integrator-specific information, see the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

Create the necessary schemas using the Repository Creation Utility (RCU) or ODI Studio.

The Oracle Repository Creation Utility (RCU) allows you to create and load a Master Repository and a Work Repository in a single database schema.

The Oracle Data Integrator Studio can also be used to manually create the repository after installation.

Section 2.2, "Installing a Database and Creating the ODI Database Schemas"

Note that RCU supports only the Oracle, Microsoft SQL Server and DB2 technologies. RCU only supports a single schema containing both the Master Repository and one Work Repository. Other technologies and configurations are supported by manually creating the repositories using the Oracle Data Integrator Studio after the installation phase.

For more information, see Appendix E, "Creating Repositories with Oracle Data Integrator Studio"

Install an application server and create an Oracle Fusion Middleware home if you will be installing the ODI Java EE components.

Installing Oracle WebLogic Server or the IBM WebSphere application server is not required to run ODI. The application server and Middleware home directory are prerequisites for using the Java EE components.

Oracle WebLogic Server installation instructions are provided in Section 2.3, "Installing an Application Server and Creating the Middleware Home"; detailed information is available in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

IBM WebSphere installation instructions are provided in Oracle Fusion Middleware Third-Party Application Server Guide.

Run Oracle Universal Installer (OUI) to install Oracle Data Integrator 11g.

The Oracle Universal Installer automates many of the ODI installation and configuration tasks.

Section 2.4, "Installing Oracle Data Integrator"

Perform any post installation steps for ODI Studio, repositories and standalone agent.

After installing ODI you may need to manually create repositories, connect to repositories or add additional drivers. Depending on your installation type, you may also need to manually configure the standalone agent.

Section 3.1, "Manual Steps for Configuring ODI Studio, Repositories, and the Standalone Agent"

Deploy Java EE components (if applicable).

If you installed Java EE components you will need to declare the Java EE agent in Topology. You may also need to create a WebLogic domain or generate and deploy Java EE Agent templates.

Section 3.2, "Configuring Java EE Components"

Perform any post-deployment configuration tasks for Java EE agent, Oracle Data Integrator Console, and Enterprise Manager (if applicable).

The Java EE Agent, Oracle Data Integrator Console and Enterprise Manager require manual post-deployment configuration tasks.

Section 3.2, "Configuring Java EE Components"


1.4 Topology Summary of ODI

The installation topology of ODI will vary based on the components you choose to install and configure. The installation of ODI requires a Middleware home directory:

When you install Oracle Data Integrator, an ODI Oracle home directory for the suite (ODI_HOME) is created under the Middleware home directory. The ODI Oracle home directory contains the binary and library files for Oracle Data Integrator.

When you configure your Java EE components and create an Oracle WebLogic Server domain, a Domain home directory (DOMAIN_HOME) is created; this directory can reside anywhere on your system.

Figure 1-2 shows a typical ODI installation topology, with Java EE components configured in a domain and WebLogic Server as the application server. Note that the domain contains two Managed Servers: odi_server1 is the default Managed Server created during domain configuration for ODI, and bam_server1 is the default Managed Server created during domain configuration for Oracle BAM. It is common to have both of these in the same domain, as so it is illustrated here to show that other products can be configured in the same domain as ODI.

Figure 1-2 Topology of an Oracle Data Integrator Installation with Oracle WebLogic Server

Surrounding text describes Figure 1-2 .

1.4.1 Contents of the 11g Installation Directory

Table 1-2 provides a few of the important Oracle Data Integrator 11g installation directories and sub-directories. Note that the installation folders you see will vary depending on the components you have installed.

Note:

See Appendix D, "Oracle Data Integrator Companion Disk Components" for the locations of additional program files and directories.

Table 1-2 OID 11g Installation Directory Contents

Directory Description

/bin

This directory contains the Upgrade Assistant.

/cfgtoollogs

This directory contains configuration and installation log files.

/common

This directory contains the following important directories:

  • /bin (Configuration Wizard, pack and unpack, wlst, and other scripts for agent creation and credential mapping.)

  • /templates/applications (Component template files for WebLogic Server domain creation or extension.)

  • /templates/was (Component template files for IBM WebSphere cell creation or extension.)

/odi_misc

This directory contains some core libraries shared by the Oracle Data Integrator components. Drivers shipped with the product are in this folder.

/oracledi

This directory contains the following important directories:

  • /agent (Oracle Data Integrator Standalone Agent.)

  • /agent/bin (Command line scripts for managing the agent, scenarios and sessions. The scripts are listed in Section 1.4.2.)

  • /agent/drivers (drivers for the Oracle Data Integrator Standalone Agent.)

  • /client (Oracle Data Integrator Studio)

  • /xml-reference (Knowledge Modules, Topology and Security metadata export files.)

/oracledi.common

This directory contains some of the libraries and files shared by Oracle Data Integrator components.

/oracledi.sdk

This directory contains the ODI Public API. Note that the libraries of this API are necessary for the run-time agent.

/oui

This directory contains a /bin directory, which in turns contains the ODI deinstaller.

/setup

This directory contains components that can be manually installed.


1.4.2 Scripts and Tools

Table 1-3 lists the scripts and tools provided in the ODI_HOME /oracledi/agent/bin directory. To launch a script from a command line, enter the name of the script to launch. Type script_name -help from the command line for the on-line help.

The extension for these scripts is .bat for Windows operating systems scripts and .sh for UNIX scripts.

Table 1-3 Oracle Data Integrator Scripts and Tools

File Description

agent

Starts a standalone agent.

agent_agent_name

Starts the standalone agent agent_name. This is the agent that is automatically configured by the installer if you have selected this option.

Example: If you created an agent named agt_007, a file called agent_agt_007 is created in this folder.

agentstop

Stops a standalone agent.

encode

Encodes a password.

getsessionstatusremote

Retrieves the status of session via an agent built-in web service.

This script is only available for UNIX operating systems. You must have wget version 1.12 or higher on your system.

odiparams

This configuration script contains the parameters for starting the other scripts. The parameters can be manually updated in the file.

odi_opmn_addagent

Add a standalone agent to OPMN.

odi_opmn_deleteagent

Removes a standalone agent from OPMN.

restartsession

Restarts a session.

startcmd

Starts an Oracle Data Integrator command.

startscen

Starts the execution of a scenario.

startscenremote

Starts a scenario on a remote agent on its web service.

This script is only available for UNIX operating systems. You must have wget version 1.12 or higher on your system.

restartloadplan

Restarts a load plan instance.

startloadplan

Starts a load plan.

stoploadplan

Stops a load plan instance execution.

stopsession

Stops a session execution.