Home / Middleware / Oracle Fusion Middleware Online Documentation Library, 11g Release 1 (11.1.1.3.0) / Installation Guides
Fusion Middleware Installation Guide for Oracle Data Integrator
ContentsOpens a new window
Opens a new window
Page 5 of 20

1 Oracle Data Integrator Installation Overview

This chapter provides an overview of the Oracle Data Integrator 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 Components

Oracle Data Integrator includes the following components:

  • Oracle Data Integrator Repository

    The Oracle Data Integrator Repository is composed of a Master Repository and one or more Work Repositories. Objects developed or configured through the user interfaces are stored in these repositories.

  • Oracle Data Integrator Studio

    Oracle Data Integrator Studio is used for administering the infrastructure (security and topology), reverse-engineering the metadata, developing projects, scheduling, operating and monitoring executions.

  • Oracle Data Integrator Standalone Agent

    The Standalone Agent is the run-time component of Oracle Data Integrator that executes the integration flows. It runs in a Java Virtual Machine and can be deployed where needed to run the flows.

    Note:

    The ODI Standalone Agent includes command line scripts for managing scenarios and sessions and encoding passwords. For more information see Section 1.3.2Opens a new window.

  • Java EE Components

    These components can be deployed in an application server. These include:

    • Java EE Agent

      Java EE Agent is the Java EE version of the run-time component of Oracle Data Integrator. The Java EE agent provides the same features as the standalone agent, but can also benefit from the features of an application server.

    • Oracle Data Integrator Console

      This component is a web interface for run-time, monitoring and metadata browsing operations. It also contains an extension integrated into the Fusion Middleware Control. Oracle Data Integrator components can be monitored as a domain using this extension.

    • Public Web Services

      ODI comes with several run-time web services. These include the "Public Web Service" and the "Agent Web Service".

      • The Public Web Service connects to the repository to retrieve a list of context and scenarios. This web service is deployed in a Java EE application server.

      • The Agent Web Service commands the Oracle Data Integrator Agent to start and monitor a scenario. Note that this web service is built-in the Java EE or Standalone Agent.

1.2 Installation Roadmap

Table 1-1Opens a new window 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 Documentation Mandatory or Optional?

Task 1 - 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.

For general planning information refer to the Oracle Fusion Middleware Installation Planning GuideOpens a new window.

For system requirements information, go to:

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htmOpens a new window

For Oracle Data Integrator-specific information, see the Oracle Fusion Middleware Developer's Guide for Oracle Data IntegratorOpens a new window

Mandatory

Task 2 - 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.1.4, "Create ODI Repositories with the Repository Creation Utility (RCU)"Opens a new window

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 G, "Creating Repositories with Oracle Data Integrator Studio"Opens a new window

Optional

Task 3 - Install Oracle WebLogic Server and create an Oracle Fusion Middleware home if you will be installing the ODI Java EE components.

Installing the WebLogic Server is not required to run ODI. The WebLogic Server (or another application server) is a prerequisite for using the Java EE components.

Oracle WebLogic Server installation instructions are provided in Section 2.1.5, "Install Oracle WebLogic Server and Create the Middleware Home"Opens a new window.

Additional information is available in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic ServerOpens a new window

Optional

Task 4 - 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.2, "ODI Installation Instructions"Opens a new window

Mandatory

Task 5 - 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 2.4, "Manual Configuration Tasks for ODI Studio, Repositories, and Standalone Agent"Opens a new window

Optional

Task 6 - 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 2.5, "Manual Configuration Tasks for Java EE Components"Opens a new window

Mandatory if Java EE components are installed

Task 7 - 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 2.5, "Manual Configuration Tasks for Java EE Components"Opens a new window

Mandatory if Java EE Agent, Oracle Data Integrator Console or Enterprise Manager are installed

1.3 Oracle Data Integrator Directory Structure

This section describes the ODI_HOME directory structure.

1.3.1 Contents of the 11g Installation Directory

The following table 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 selected installation type:

Directory Description
/bin This directory contains the Upgrade Assistant
/cfgtoologs This directory contains configuration and installation log files
/oracledi This directory contains the following:

  • /client (Oracle Data Integrator Studio)

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

  • /agent (Oracle Data Integrator Standalone Agent.)
/oracledi/agent This folder also includes other directories:

  • /bin (Command line scripts for managing the agent, scenarios and sessions. The scripts are listed in Section 1.3.2Opens a new window.)

  • /drivers (drivers for the Oracle Data Integrator Standalone Agent.)
/oracledi.common This directory contains some of the libraries and files shared by Oracle Data Integrator components.
/oracledi.sdk This directory contains java source code of Public API usage samples.
/setup This directory contains components that can be manually installed.
/odi_misc This directory contains some core libraries shared by the Oracle Data Integrator components. Drivers shipped with the product are in this folder.

1.3.2 Scripts and Tools

Table 1-2Opens a new window 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 scripts and .sh for UNIX scripts.

Table 1-2 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 LINUX/UNIX operating systems.

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 a the execution of a scenario.

startscenremote

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

This script is only available for LINUX/UNIX operating systems.