1 Planning Your Oracle Data Integrator Installation
This chapter helps to prepare you for your Oracle Data Integrator installation.
Various topics are covered that should be reviewed thoroughly to help ensure that you do not encounter any problems either during or after the product installation and domain configuration.
This chapter includes the following sections:
-
Section 1.3, "Understanding Oracle Data Integrator Topology"
-
Section 1.4, "Understanding the Oracle Data Integrator Install Types"
-
Section 1.5, "Understanding the Oracle Data Integrator Standard Installation Topologies"
-
Section 1.6, "Roadmap for Installing and Configuring the Standard Installation Topology"
-
Section 1.7, "Roadmap for Verifying Your System Environment"
-
Section 1.8, "Understanding and Obtaining the Oracle Data Integrator Distribution"
1.1 Using This Document
This section contains the following topics:
1.1.1 Using the Standard Installation Topology as a Starting Point
This guide will help you create the standard installation topologies for Oracle Data Integrator (Section 1.5). These topologies can be extended to be highly available and secure, making them suitable for a production system.
A standard installation topology represents a sample topology for this product; it is not the only topology that is supported. For more information, see "Understanding the Standard Installation Topology" in Planning an Installation of Oracle Fusion Middleware.
1.1.2 Using this Document in an Upgrade Scenario
If you are installing Oracle Data Integrator as part of an upgrade procedure, follow the instructions in this book to install the software, but do not run the Configuration Wizard to create a WebLogic domain.
After the software is installed, refer to Upgrading Oracle Data Integrator.
1.1.3 Using this Document to Extend a Domain
The instructions in this document describe how to create a new domain, and assumes that no other Oracle Fusion Middleware products are installed on your system. All of the instructions for installation and domain creation are based on this assumption.
In the event that you already have other Oracle Fusion Middleware products installed on your system (for example, you are creating the Java EE agent topology and you already have Oracle Fusion Middleware Infrastructure installed with a domain that is up and running), the same instructions can be used to extend your existing domain. If you choose to do this, be sure to read "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middleware for important information.
If you are creating a new domain but your needs do not match the instructions given in the procedure, be sure to make your selections accordingly and refer to the supporting documentation for additional details.
1.2 Understanding Oracle Data Integrator Agents
This section describes the different types of agents that can be configuring in Oracle Data Integrator. Understanding this will help you determine which sort of topology you need to create, based on your needs.
Tip:
More information about these agents and how they fit into the overall Oracle Data Integrator topology can be found in "Introduction to the Oracle Data Integrator Topology" in Developer's Guide for Oracle Data Integrator.
1.2.1 Understanding Java EE Agents
A Java EE agent is a JEE application that is deployed and runs on a Managed Server configured in a WebLogic domain.
It is recommended to install this agent when high availability, scalability, security and better manageability are desired. The Java EE agent is best suited for environments where Oracle Data Integrator interoperates with other Oracle Fusion Middleware products.
Section 1.5.1 provides an overview of the standard installation topology for a Java EE agent.
1.2.2 Understanding Standalone Agents
A standalone agent runs as its own process and is managed by the WebLogic Management Framework (see "What is the WebLogic Management Framework?" in Understanding Oracle Fusion Middleware).
Typically, you would install a standalone agent so that it runs in any environment where the agent process should be lightweight and local WebLogic Server operations are not supported.
Section 1.5.2 provides an overview of the standard installation topology for a standalone agent.
1.2.3 Understanding Colocated Standalone Agents
A colocated standalone agent is a standalone agent that is configured in a WebLogic domain and is managed by an Administration Server. The WebLogic domain makes Oracle Fusion Middleware Infrastructure services available for managing the agent.
Section 1.5.3 provides an overview of the standard installation topology for a colocated standalone agent.
1.3 Understanding Oracle Data Integrator Topology
Before you can begin developing using Oracle Data Integrator, you must first set up an Oracle Data Integrator topology, which is the physical and logical representation of the Oracle Data Integrator architecture and components. The Oracle Data Integrator topology defines where to find the sources and targets of the data that you are integrating.
Note that this topology is not the same as the standard installation topology, which is the layout of files installed and configured on your computer by the Oracle Universal Installer and the configuration wizard.
More information about the Oracle Data Integrator topology can be found in "Setting up a Topology" in Developer's Guide for Oracle Data Integrator.
1.4 Understanding the Oracle Data Integrator Install Types
The Oracle Data Integrator product installer provides two install types:
For more information about the contents of the Oracle Data Integrator distribution, see Appendix A.
1.4.1 Enterprise Install Type
This install type should be used:
-
To install ODI Studio
-
To create a managed environment using WebLogic Server
Note:
If you only want to use ODI studio and do not wish to configure a domain, you can skip the domain creation instructions in this guide. ODI Studio is available for use after the Enterprise Installation install type is completed and database schemas are created.
-
To create a Java EE agent
-
To create a colocated standalone agent in a WebLogic domain
1.4.2 Standalone Install Type
This install type should be used to create a standalone agent.
Note:
You must also install the Enterprise Installation install type into a separate Oracle home if you want to use ODI Studio (Section 1.4.1).
1.5 Understanding the Oracle Data Integrator Standard Installation Topologies
This document describes how to install and configure the following standard installation topologies for Oracle Data Integrator:
-
Standard installation topology for the Java EE agent.
The Java EE agent is installed into an existing Oracle home containing Oracle Fusion Middleware Infrastructure (Section 1.5.1). Along with the Java EE agent, ODI Console, ODI Studio, and the plugin for Fusion Middleware Control are also installed in the topology.
-
Standard installation topology for the standalone agent.
The standalone agent is installed and configured in a standalone domain and managed by the WebLogic Management Framework (Section 1.5.2).
-
Standard installation topology for the colocated standalone agent.
The standalone agent is installed and configured in a WebLogic domain and managed using the Node Manager and Administration Server (Section 1.5.3).
A roadmap describing the necessary steps to arriving at these topologies can be found in Section 1.6.
1.5.1 Understanding the Standard Installation Topology for the Java EE Agent
Figure 1-1 shows the standard installation topology for Oracle Data Integrator Java EE agent.
Figure 1-1 Standard Installation Topology for the Java EE Agent
Description of "Figure 1-1 Standard Installation Topology for the Java EE Agent"
This topology represents a standard WebLogic Server domain that contains an Administration Server and a Managed Server on which the Infrastructure and Java EE agent are deployed. The Managed Server is targeted to a machine inside a cluster. The domain is configured on a single host and requires a supported database where the required Fusion Middleware schemas are installed.
All elements in this standard installation topology illustration are described in Table 1-1.
Table 1-1 Description of the Elements in the Java EE Standard Installation Topology
| Element | Description and Links to Additional Documentation |
|---|---|
|
APPHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the database. |
|
WebLogic Domain |
A logically related group of Java components (in this case, the administration Server, Managed Servers, and other related software components). For more information, see "What is an Oracle WebLogic Server Domain" in Understanding Oracle Fusion Middleware. |
|
Administration Server |
The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers. For more information, see "What is the Administration Server" in Understanding Oracle Fusion Middleware. |
|
Enterprise Manager |
Oracle Enterprise Manager Fusion Middleware Control. This is the main tool that can be used to manage your domain. For more information, see "Oracle Enterprise Manager Fusion Middleware Control" in Understanding Oracle Fusion Middleware. |
|
Cluster |
A collection of multiple WebLogic Server instances running simultaneously and working together. For more information, see "Understanding Managed Servers and Managed Server Clusters" in Understanding Oracle Fusion Middleware. |
|
Machine |
Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between WebLogic Managed Servers and the Node Manager; in order to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine. |
|
Managed Server |
Host for your applications, application components, Web services, and their associated resources. For more information, see "Understanding Managed Servers and Managed Server Clusters" in Understanding Oracle Fusion Middleware. |
|
Infrastructure |
Collection of services that include the following:
|
|
Java EE Agent |
The Java EE agent. For more information about Java EE agents, see Section 1.2.1. |
1.5.2 Understanding the Standard Installation Topology for the Standalone Agent
Figure 1-2 shows the standard installation topology for the standalone agent.
Figure 1-2 Standard Installation Topology for the Standalone Agent
Description of "Figure 1-2 Standard Installation Topology for the Standalone Agent"
This topology represents a standalone agent configured in a standalone domain, managed by the WebLogic Management Framework. The domain is configured on a single host and requires a supported database where the required Fusion Middleware schemas are installed.
All elements in this standard installation topology illustration are described in Table 1-2.
Table 1-2 Description of the Elements in the Standalone Agent Standard Installation Topology
| Element | Description and Links to Additional Documentation |
|---|---|
|
APPHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the database. |
|
Standalone Domain |
A container for system components, such as Oracle HTTP Server or Oracle Data Integrator standalone agents. For more information, see "What is a Standalone Domain" in Understanding Oracle Fusion Middleware. |
|
System Component |
A manageable process that is not deployed in a Java application container. For more information, see "What is a System Component?" in Understanding Oracle Fusion Middleware. |
1.5.3 Understanding the Standard Installation Topology for the Colocated Standalone Agent
Figure 1-3 shows the standard installation topology for the colocated standalone agent.
Figure 1-3 Standard Installation Topology for the Colocated Standalone Agent
Description of "Figure 1-3 Standard Installation Topology for the Colocated Standalone Agent"
This standard installation topology represents a standalone agent configured in a WebLogic domain, managed by an Administration Server. The domain is configured on a single host and requires a supported database where the required Fusion Middleware schemas are installed.
All elements in this standard installation topology illustration are described in Table 1-3.
Table 1-3 Description of the Elements in the Colocated Standalone Agent Standard Installation Topology
| Element | Description and Links to Additional Documentation |
|---|---|
|
APPHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the computer that is hosting the database. |
|
Administration Server |
The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers. For more information, see "What is the Administration Server" in Understanding Oracle Fusion Middleware. |
|
Enterprise Manager |
Oracle Enterprise Manager Fusion Middleware Control. This is the main tool that can be used to manage your domain. For more information, see "Oracle Enterprise Manager Fusion Middleware Control" in Understanding Oracle Fusion Middleware. |
|
Machine |
Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between WebLogic Managed Servers and the Node Manager; in order to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine. |
|
System Component |
A standalone process that is managed by the WebLogic Management Framework. For more information, see "What is a System Component?" in Understanding Oracle Fusion Middleware. |
1.6 Roadmap for Installing and Configuring the Standard Installation Topology
This guide provides all the steps required to install and configure the standard Oracle Data Integrator topology. Within the procedures, the guide also provides references to additional information you can use if you want to create a slightly modified version of this topology.
Table 1-4 show the steps required to install and configure the topology.
Table 1-4 Oracle Data Integrator Installation Roadmap
| Task | Description | Documentation |
|---|---|---|
|
Verify your system environment |
Before beginning the installation, verify that the minimum system and network requirements are met. |
See Section 1.7. |
|
Obtain the appropriate distribution |
The Oracle Data Integrator ( |
See Section 1.8. |
|
Determine your installation directories |
Verify that the directories that will need to be created can be created or accessed by the installer, and exist on systems that meet the minimum requirements. |
See "Understanding the Recommended Directory Structure" in Planning an Installation of Oracle Fusion Middleware. |
|
Install the software |
Installing software transfers the software to your system and creates the Oracle home directory. |
For more information about the install types available during installation, see Section 1.4. For installation instructions, see Chapter 2. |
|
Create the Master and Work Repository schemas. |
Use the Repository Creation Utility (RCU) to create the Master and Work Repository database schemas. |
See Chapter 3. |
|
Create and configure your domain. |
Use the configuration wizard to create and configure your domain. NOTE: If you only want ODI Studio and do not wish to configure a domain, you can skip this step. ODI Studio is available for use after the Enterprise Installation type is installed and the database schemas are created. |
See Chapter 4 to create the topology for a Java EE agent. See Chapter 5 to create the topology for a standalone agent. See Chapter 6 to create the topology for a colocated standalone agent. |
|
Administer and prepare your domain for high availability |
Discover additional tools and resources to administer your domain and configure your domain to be highly available. |
See Chapter 7. |
1.7 Roadmap for Verifying Your System Environment
This section (Table 1-5) contains important information that you must read and understand prior to beginning the installation and configuration process. It identifies important tasks and checks to perform to make sure your environment is properly prepared for installing and configuring Oracle Data Integrator.
Table 1-5 Roadmap for Verifying Your System Environment
| Task | Description | Documentation |
|---|---|---|
|
Verify certification and system requirements. |
Verify that your operating system is certified and properly configured for Oracle Fusion Middleware Infrastructure installation and configuration. |
See "Verifying Certification and System Requirements" in Planning an Installation of Oracle Fusion Middleware. |
|
Prepare your system for installation. |
Verify that the necessary environment variables are set, and you have identified a proper installation user. |
See "Prepare Your System for Installation" in Planning an Installation of Oracle Fusion Middleware. |
|
Install a certified JDK. |
The installation program for the distribution requires a certified JDK present on your system. |
See "Installing a JDK" in Planning an Installation of Oracle Fusion Middleware. |
|
Install and configure a database. |
To configure your domain, you must have access to a certified database that is properly configured for schemas required by the Oracle Data Integrator. |
See "Installing a Database and Database Schemas" in Planning an Installation of Oracle Fusion Middleware. |
1.8 Understanding and Obtaining the Oracle Data Integrator Distribution
The Oracle Data Integrator distribution is available as a .jar file. You must have a certified JDK already installed on your system in order to install and configure this distribution.
Tip:
For more information about distributions, see "Understanding and Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.
The distribution contains the products and feature sets described in Appendix A.
For information on how to obtain the distribution, see "Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.