Oracle® Fusion Middleware

Installing and Configuring Oracle Data Integrator

12c (12.1.2)

E39433-02

November 2013

Documentation for installers and system administrators that describes how to install and configure Oracle Data Integrator.

Oracle Fusion Middleware Installing and Configuring Oracle Data Integrator 12c (12.1.2)

E39433-02

Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author: Kevin Hwang

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Planning Your Oracle Data Integrator Installation

- 1.1 Using This Document

- 1.1.1 Using the Standard Installation Topology as a Starting Point

- 1.1.2 Using this Document in an Upgrade Scenario

- 1.1.3 Using this Document to Extend a Domain

- 1.2 Understanding Oracle Data Integrator Agents

- 1.2.1 Understanding Java EE Agents

- 1.2.2 Understanding Standalone Agents

- 1.2.3 Understanding Colocated Standalone Agents

- 1.3 Understanding Oracle Data Integrator Topology

- 1.4 Understanding the Oracle Data Integrator Install Types

- 1.4.1 Enterprise Install Type

- 1.4.2 Standalone Install Type

- 1.5 Understanding the Oracle Data Integrator Standard Installation Topologies

- 1.5.1 Understanding the Standard Installation Topology for the Java EE Agent

- 1.5.2 Understanding the Standard Installation Topology for the Standalone Agent

- 1.5.3 Understanding the Standard Installation Topology for the Colocated Standalone Agent

- 1.6 Roadmap for Installing and Configuring the Standard Installation Topology

- 1.7 Roadmap for Verifying Your System Environment

- 1.8 Understanding and Obtaining the Oracle Data Integrator Distribution

2 Installing Oracle Data Integrator

- 2.1 Starting the Installation Program

- 2.2 Navigating the Installation Screens to Install Oracle Data Integrator

- 2.3 Verifying the ODI Installation

- 2.3.1 Reviewing Installation Log Files

- 2.3.2 Checking the Directory Structure

3 Creating the Oracle Data Integrator Master and Work Repository Schema

- 3.1 Configuring a Certified Database

- 3.2 Starting RCU

- 3.3 Navigating the RCU Screens to Create the Schema

4 Configuring the Standard Installation Topology for the Java EE Agent

- 4.1 Creating the Database Schema

- 4.2 Configuring Your WebLogic Domain for Your Java EE Agent

- 4.2.1 Starting the Configuration Wizard

- 4.2.2 Navigating the Configuration Wizard Screens to Configure the Domain

- 4.3 Creating a Java EE Agent in the Master Repository Using ODI Studio

- 4.3.1 Starting ODI Studio

- 4.3.2 Connecting to the Master Repository

- 4.3.3 Creating the Java EE Agent

- 4.4 Starting the Servers

- 4.4.1 Starting the Node Manager

- 4.4.2 Starting the Administration Server

- 4.4.3 Starting the Managed Server

- 4.5 Performing Next Steps

5 Configuring the Standalone Installation Topology for the Standalone Agent

- 5.1 Creating the Database Schema

- 5.2 Configuring Your Standalone Domain for the Standalone Agent

- 5.2.1 Starting the Configuration Wizard

- 5.2.2 Navigating the Configuration Wizard Screen to Create the Domain

- 5.3 Creating a Standalone Agent in the Master Repository Using ODI Studio

- 5.3.1 Starting ODI Studio

- 5.3.2 Connecting to the Master Repository

- 5.3.3 Creating the Standalone Agent

- 5.4 Starting the Node Manager and Standalone Agent

- 5.4.1 Starting the Standalone Agent Using Node Manager

- 5.4.1.1 Starting the Node Manager

- 5.4.1.2 Starting the Standalone Agent with Node Manager

- 5.4.2 Starting the Standalone Agent Without Node Manager

- 5.5 Performing Next Steps

6 Configuring the Standard Installation Topology for the Colocated Standalone Agent

- 6.1 Creating the Database Schema

- 6.2 Configuring Your WebLogic Domain for Your Colocated Standalone Agent

- 6.2.1 Starting the Configuration Wizard

- 6.2.2 Navigating the Configuration Wizard Screens to Configure the Domain

- 6.3 Creating a Standalone Agent in the Master Repository Using ODI Studio

- 6.3.1 Starting ODI Studio

- 6.3.2 Connecting to the Master Repository

- 6.3.3 Creating the Standalone Agent

- 6.4 Starting the Servers and Standalone Agent

- 6.4.1 Starting the Administration Server

- 6.4.2 Starting the Colocated Standalone Agent

- 6.4.2.1 Starting the Agent Using Node Manager

- 6.4.2.2 Starting the Agent Without Node Manager

- 6.5 Performing Next Steps

7 Next Steps After Configuring an Oracle Data Integrator Domain

- 7.1 Performing Basic Administrative Tasks

- 7.2 Performing Additional Domain Configuration Tasks

- 7.3 Preparing Oracle Data Integrator for Development

- 7.4 Preparing Your Environment For High Availability

8 Deinstalling Oracle Data Integrator

- 8.1 Understanding Product Deinstallation

- 8.2 Stopping Oracle Fusion Middleware

- 8.2.1 Stopping Your Oracle Data Integrator Agents

- 8.2.2 Stopping the Oracle Fusion Middleware Environment

- 8.3 Removing Your Database Schemas

- 8.4 Deinstalling the Software

- 8.4.1 Starting the Deinstaller

- 8.4.2 Navigating the Deinstallation Screens

- 8.5 Removing the Oracle Home Directory Manually

- 8.6 Removing Your Domain and Application Data

- 8.7 Removing Your ODI Wallet Information

- 8.8 Deinstalling Oracle Fusion Middleware Infrastructure

- 8.9 Reinstalling the Software

A Understanding the Oracle Data Integrator Distribution

B Troubleshooting Oracle Data Integrator

- B.1 Understanding General Troubleshooting Tips

- B.2 Understanding Installation and Configuration Log Files

- B.3 Verifying ODI Client and Repository Compatibility

- B.4 Need More Help?

Preface

This document describes how to use the Oracle Data Integrator installation program to install the Oracle data Integrator software and configure a WebLogic domain.

If you are an existing Oracle Data Integrator user, your path to obtain the most recent version of the software will depend on the version of your existing software. For more information, refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files for the steps you need to take to update or upgrade your existing software.

Audience

This guide is intended for administrators who are responsible for installing and configuring components of Oracle Data Integrator. It is assumed that readers are comfortable running some system administration operations, such as creating users and groups, adding users to groups, and installing operating system patches on the computer where your products will be installed. Users in UNIX systems who are installing need root access to run some scripts.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For important information about Oracle Fusion Middleware products, see the following manuals:

- Planning an Installation of Oracle Fusion Middleware
This book contains useful information you should read before installing any Oracle Fusion Middleware product.

- Understanding Oracle Fusion Middleware
This book introduces the common terms and concepts in an Oracle Fusion Middleware environment.

- Administering Oracle Fusion Middleware
This book contains information for managing your Oracle Fusion Middleware environment after installation and configuration is complete.

For important information about updating or upgrading your existing Oracle Data Integrator software to the latest version, see the following manual:

- Planning an Upgrade of Oracle Fusion Middleware
This book contains important information about planning your 11g upgrade to 12c.

- Upgrading Oracle Data Integrator
This book provides information for upgrading your existing 11g version of Oracle Data Integrator to the latest available version.

For more information about related Oracle Data Integrator products and services, see the following manuals:

- Developer's Guide for Oracle Data Integrator
This book provides guidelines for developers interested in using Oracle Data Integrator for integration projects.

- Connectivity and Knowledge Modules Guide for Oracle Data Integrator
This document describes Oracle Data Integrator Knowledge Modules and technologies and how to use them in integration projects.

- Knowledge Module Developer's Guide for Oracle Data Integrator
This book describes how to develop your own Knowledge Modules for Oracle Data Integrator.

- Application Adapters Guide for Oracle Data Integrator
This book describes Oracle Data Integrator Application Adapters and how to use them in ODI integration projects.

- Getting Started with SAP ABAP ERP Adapter for Oracle Data Integrator
This book describes how to use Oracle Data Integrator with the SAP ABAP ERP Adapter, including configuration, loading a Data Warehouse with data from SAP ERP systems, and validating data quality.

- Getting Started with SAP ABAP BW Adapter for Oracle Data Integrator
This book describes how to use Oracle Data Integrator with the SAP ABAP BW Adapter, including configuration, loading a Data Warehouse with data from SAP BW systems, and validating data quality.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

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.1, "Using This Document"

- Section 1.2, "Understanding Oracle Data Integrator Agents"

- 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:

- Section 1.1.1, "Using the Standard Installation Topology as a Starting Point"

- Section 1.1.2, "Using this Document in an Upgrade Scenario"

- Section 1.1.3, "Using this Document to Extend a Domain"

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.

- Section 1.2.2, "Understanding Standalone Agents"

- Section 1.2.3, "Understanding Colocated Standalone Agents"

- Section 1.2.1, "Understanding Java EE Agents"

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:

- Enterprise Install Type

- Standalone Install Type

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

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:

- Metadata repository (MDS)
This contains metadata for Oracle Fusion Middleware components, such as the Oracle Application Developer Framework.

For more information, see "What is the Metadata Repository" in Understanding Oracle Fusion Middleware.

- Oracle Application Developer Framework (Oracle ADF)

- Oracle Web Services Manager (OWSM)

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

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

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 (odi_121200_generic.jar) distribution is required for all Oracle Data Integrator topologies.

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.

2 Installing Oracle Data Integrator

This chapter describes how to install and configure Oracle Data Integrator. Post-installation configuration parameters are also provided.

The following topics are covered:

- Section 2.1, "Starting the Installation Program"

- Section 2.2, "Navigating the Installation Screens to Install Oracle Data Integrator"

- Section 2.3, "Verifying the ODI Installation"

2.1 Starting the Installation Program

To start the installation program for Oracle Data Integrator, perform the following steps.

1. Log in to the target system.

2. The installer requires that a certified JDK already exists on your system. For more information, see the appropriate certification document for 12c (12.1.2) on the Oracle Fusion Middleware Supported System Configurations page.

3. Go to the directory where you downloaded the installation program.

4. Launch the installation program by invoking java -jar from the JDK directory on your system, as shown in the example below:

/home/Oracle/jdk7_15/jdk1.7.0_15/bin/java -jar odi_121200_generic.jar

Be sure to replace /home/Oracle/jdk7_15/jdk1.7.0_15 in this example with the location of the JDK on your system.

When the installation program appears, you are ready to begin the installation. See Section 2.2 for a description of each installation program screen.

2.2 Navigating the Installation Screens to Install Oracle Data Integrator

The installation program displays a series of screens, in the order listed in Table 2-1.

If you need additional help with any of the installation screens, click the screen name.

Table 2-1 Oracle Data Integrator Install Screens

Screen

Description

Installation Inventory Setup

This screen will appear if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location.

For more information about the central inventory, see "Understanding the Oracle Inventory" in Installing Software with the Oracle Universal Installer.

Welcome

This screen introduces you to the product installer.

Installation Location

Use this screen to specify the location of your Oracle home directory.

For more information, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware.

Installation Type

Use this screen to select the type of installation and consequently, the products and feature sets you want to install.

For more information about the install types, see Section 1.4

Prerequisite Checks

This screen verifies that your system meets the minimum necessary requirements.

If there are any warning or error messages, you can refer to one of the following documents in Section 1.7.

Specify Security Updates

If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates.

If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.

Installation Summary

Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save and provide the location and name of the response file. Response files can be used later in a silent installation situation.

For more information about silent or command line installation, see "Using the Oracle Universal Installer in Silent Mode" in Installing Software with the Oracle Universal Installer.

Installation Progress

This screen allows you to see the progress of the installation.

Installation Complete

This screen appears when the installation is complete. Review the information on this screen, then click Finish to dismiss the installer.

2.3 Verifying the ODI Installation

After you complete the installation, you can verify it by successfully completing the following tasks:

- Reviewing Installation Log Files

- Checking the Directory Structure

2.3.1 Reviewing Installation Log Files

Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see Section B.2, "Understanding Installation and Configuration Log Files".

2.3.2 Checking the Directory Structure

The contents of your ODI installation vary based on the options you selected during the installation.

For more information about the directory structure you should see after installation, see "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware.

3 Creating the Oracle Data Integrator Master and Work Repository Schema

This chapter describes how to create the Master and Work Repository (ODI_REPO) database schemas using the Repository Creation Utility (RCU).

This step is required before any domain is configured for your Oracle Data Integrator agent.

The following topics are covered in this chapter:

- Section 3.1, "Configuring a Certified Database"

- Section 3.2, "Starting RCU"

- Section 3.3, "Navigating the RCU Screens to Create the Schema"

3.1 Configuring a Certified Database

Before you begin, make sure you have installed and configured a certified database.

For more information, see "Installing a Database and Database Schemas" in Planning an Installation of Oracle Fusion Middleware.

3.2 Starting RCU

Navigate to the ORACLE_HOME/oracle_common/bin directory and start RCU.

1. Set the JAVA_HOME environment variable to your JDK location.
On UNIX operating systems:

setenv JAVA_HOME /home/Oracle/Java/jdkversion

On Windows operating systems, right-click on the desktop, then select My Computer, then select Properties. Click Advanced System Settings in the left column, then click Environment Variables in the System Properties window.

In the Environment Variables window, set JAVA_HOME to your JDK location.

2. Start RCU.
On UNIX operating systems:

./rcu

On Microsoft Windows operating systems:

rcu.bat

3.3 Navigating the RCU Screens to Create the Schema

Follow the instructions on this section to complete schema creation for Oracle Data Integrator.

Refer to "Understanding Repository Creation Screens" in Creating Schemas with the Repository Creation Utility for more information about any of the screens mentioned in this section.

- Task 1, "Introducing RCU"

- Task 2, "Selecting a Repository Creation Method"

- Task 3, "Providing Database Connection Details"

- Task 4, "Selecting Components"

- Task 5, "Specifying Schema Passwords"

- Task 6, "Setting Custom Variables"

- Task 7, "Completing Schema Creation"

Task 1   Introducing RCU

Click Next.

Task 2   Selecting a Repository Creation Method

If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load Concurrently. This procedure assumes that you have the necessary privileges.

If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.

Task 3   Providing Database Connection Details

Provide the database connection details for RCU to connect to your database.

Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.

Task 4   Selecting Components

Select Create a new prefix, specify a custom prefix, then select the Oracle Data Integrator schema.

The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.

Tip:

For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.

If you are running RCU from a Standalone installation, you will see the following:

If you are running RCU from an Enterprise installation, you will see the following:

Tip:

You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

Task 5   Specifying Schema Passwords

Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.

Tip:

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

Task 6   Setting Custom Variables

Specify the custom variables for the Master and Work Repository.

Tip:

More information about the fields on this screen can be found in "Custom Variables" in Creating Schemas with the Repository Creation Utility.

Task 7   Completing Schema Creation

Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.

4 Configuring the Standard Installation Topology for the Java EE Agent

This chapter describes how to create and configure the domain for the Java EE agent standard installation topology.

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:

- Section 4.1, "Creating the Database Schema"

- Section 4.2, "Configuring Your WebLogic Domain for Your Java EE Agent"

- Section 4.3, "Creating a Java EE Agent in the Master Repository Using ODI Studio"

- Section 4.4, "Starting the Servers"

- Section 4.5, "Performing Next Steps"

4.1 Creating the Database Schema

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.

4.2 Configuring Your WebLogic Domain for Your Java EE Agent

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:

- Section 4.2.1, "Starting the Configuration Wizard"

- Section 4.2.2, "Navigating the Configuration Wizard Screens to Configure the Domain"

4.2.1 Starting the Configuration Wizard

To begin domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

4.2.2 Navigating the Configuration Wizard Screens to Configure the Domain

Follow the instructions in this section to create and configure the domain for the topology.

Note:

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:

- Task 1, "Selecting the Domain Type and Domain Home Location"

- Task 2, "Selecting the Configuration Templates"

- Task 3, "Selecting the Application Home Location"

- Task 4, "Configuring the Administrator Account"

- Task 5, "Specifying the Domain Mode and JDK"

- Task 6, "Specifying the Datasource Configuration Type"

- Task 7, "Specifying JDBC Component Schema Information"

- Task 8, "Testing the JDBC Connections"

- Task 9, "Specifying Supervisor Credentials"

- Task 10, "Selecting Advanced Configuration"

- Task 11, "Configuring the Administration Server Listen Address"

- Task 13, "Configuring Managed Servers"

- Task 14, "Configuring a Cluster"

- Task 16, "Configuring Coherence Clusters"

- Task 17, "Creating a New Machine"

- Task 19, "Reviewing Your Configuration Specifications and Configuring the Domain"

- Task 20, "Writing Down Your Domain Home and Administration Server URL"

Task 1   Selecting the Domain Type and Domain Home Location

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.

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Templates

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:

- Oracle Enterprise Manager Plugin for ODI - 12.1.2.0 [em]]
Selecting this template automatically selects the following as dependencies:

- Oracle Enterprise Manager - 12.1.2.0 [em]

- Oracle JRF - 12.1.2.0 [oracle_common]

- WebLogic Coherence Cluster Extension - 12.1.2.0 [wlserver]

- Oracle Data Integrator - Agent - 12.1.2.0 [odi]
Selecting this template automatically selects the following as dependencies:

- Oracle Data Integrator - Agent Libraries - 12.1.2.0 [odi]

- Oracle Data Integrator SDK Shared Library Template - 12.1.2.0 [odi]

- Oracle Data Integrator - Console - 12.1.2.0 [odi]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Selecting the Application Home Location

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.

Tip:

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.

Task 4   Configuring the Administrator Account

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.

Task 5   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

- Select Production in the Domain Mode field.

- Select the Oracle HotSpot JDK in the JDK field.

Tip:

More information about the options on this screen can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

Task 6   Specifying the Datasource Configuration Type

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.

Note:

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:

Field

Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number on which the database listens.

Schema Owner

Schema Password

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 prefix_STB, where prefix is the custom prefix that you defined in RCU.

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.

Tip:

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

Task 7   Specifying JDBC Component Schema Information

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.

Tip:

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

- "Configuring GridLink Data Sources with Oracle RAC"

- "Configuring Multi Data Sources"

More information about the other options on this screen can be found in JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Testing the JDBC Connections

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.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard

Task 9   Specifying Supervisor Credentials

Use the Credentials screen to create the following two keys:

1. A key for the Supervisor user already exists. Modify the credential as follows:

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

2. The password must be the same password specified on the Custom Variables screen in RCU during schema creation (see Task 6 in Section 3.3).

2. Create a second credential as follows:

1. Click the Plus sign (+) icon to add a new credential.

2. In the Key Name field, enter the name of this domain as the key.

3. In the Username and Password fields, provide the Administrator user's user name and password.

4. Select oracle.odi.credmap as the store name.

Task 10   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

- Administration Server
This is required to properly configure the listen address of the Administration Server.

- Node Manager
This is required to configure Node Manager.

- Managed Server, Clusters and Coherence
This is required to configure the Oracle Data Integrator Managed Server.

Task 11   Configuring the Administration Server Listen Address

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.

Task 12   Configuring Node Manager

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.

Tip:

More information about the options on this screen can be found in Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

More information about the types of Node Manager can be found in "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server.

Task 13   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server named ODI_server1 is created:

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

2. 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.

Note:

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.

Tip:

More information about the options on this screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

Task 14   Configuring a Cluster

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify ODI_cluster1 in the Cluster Name field.

3. 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

Tip:

More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 15   Assigning the Managed Server to the Cluster

Use the Assign Servers to Clusters screen to assign ODI_server1 to the new cluster ODI_cluster1:

1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, ODI_cluster1.

2. In the Servers pane, assign ODI_server1 to 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.

- Double-click on ODI_server1 to move it beneath the selected cluster (ODI_cluster1) in the clusters pane.

Tip:

More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 16   Configuring Coherence Clusters

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.

Note:

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.

Note:

For Coherence licensing information, refer to "Oracle Coherence" in Licensing Information.

Task 17   Creating a New Machine

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.

Tip:

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.

1. Click the Add button to create a new machine.

2. Specify ODI_machine1 in the Name field.

3. 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.

4. 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.

Note:

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.

Tip:

More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 18   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Server to the new machine you just created:

1. In the Machines pane, select the machine to which you want to assign the servers; in this case, ODI_machine1.

2. In the Servers pane, assign AdminServer to 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.

- Double-click on AdminServer to move it beneath the selected machine (ODI_machine1) in the Machines pane.

3. Repeat to assign ODI_server1 to ODI_machine1.

Tip:

More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 19   Reviewing Your Configuration Specifications and Configuring the Domain

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.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Task 20   Writing Down Your Domain Home and Administration Server URL

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.

4.3 Creating a Java EE Agent in the Master Repository Using ODI Studio

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:

- Section 4.3.1, "Starting ODI Studio"

- Section 4.3.2, "Connecting to the Master Repository"

- Section 4.3.3, "Creating the Java EE Agent"

4.3.1 Starting ODI Studio

To start the ODI Studio:

1. Go to the Oracle home where you have installed Oracle Fusion Middleware Infrastructure and the Enterprise Installation type.

2. Inside that Oracle home, go to the odi/studio directory.

3. Start ODI Studio.
On UNIX operating systems:

./odi.sh

On Windows operating systems:

odi.exe

4.3.2 Connecting to the Master Repository

Before an agent can be created you must connect to the Master repository:

- Task 1, "Getting Started"

- Task 2, "Creating a Login"

- Task 3, "Specifying a New Wallet Password"

- Task 4, "Logging in to the Master Repository"

Note:

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.

Task 1   Getting Started

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.

Task 2   Creating a Login

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.

- User: Specify 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 prefix_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.

Task 3   Specifying a New Wallet Password

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.

Task 4   Logging in to the Master Repository

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:

1. In the drop-down menu in the Login Name field, select the name of the new login you just created.

2. Specify SUPERVISOR as the user name.

3. 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.

4.3.3 Creating 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.

- Task 1, "Adding an Agent to the Oracle Data Integrator Topology"

- Task 2, "Specifying the Agent Details"

- Task 3, "Saving Your Changes"

Task 1   Adding an Agent to the Oracle Data Integrator Topology

In the navigation pane on the left side, select the Topology tab, then right-click Agents, then select New Agent.

Task 2   Specifying the Agent Details

Specify the new agent details as summarized in the following table:

Field

Description

Name

Specify OracleDIAgent as the agent name.

Host

Enter the IP address or name of the machine where the agent is running. Do not use "localhost."

Port

Enter the port number on which the agent listens.

Note:

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.

Task 3   Saving Your Changes

From the ODI Studio menu, select File, then select Save All to save your changes.

4.4 Starting the Servers

After configuration is complete, do the following to access the tools with which you can manage your domain:

Note:

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.

- Section 4.4.2, "Starting the Administration Server"

- Section 4.4.3, "Starting the Managed Server"

4.4.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

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.

4.4.2 Starting the Administration Server

To start the Administration Server, go the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

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.

Tip:

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.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

http://administration_server_host:administration_server_port/console

The default Administration Server port number is 7001.

For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.

4.4.3 Starting the Managed Server

To start the Managed Server:

1. Login to Oracle Fusion Middleware Control:

http://administration_server_host:administration_server_port/em

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 7001.

The login credentials were provided on the Administrator Account screen (Task 4).

2. From the "Target Navigation" pane, click the arrows to expand the domain until the Managed Servers (ODI_server1) is visible.

3. Select the Managed Server (ODI_server1).

4. Next to the WebLogic Server menu, select Start Up.

5. In the Target Navigation page, select your domain name to see that all the servers are up and running.

Tip:

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.

4.5 Performing Next Steps

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.

5 Configuring the Standalone Installation Topology for the Standalone Agent

This chapter describes how to create and configure your domain for the standalone agent.

Before you continue, make sure that you have completed the following:

- Completed the Enterprise Installation install type (Chapter 2) in an Oracle home. ODI Studio is only available with this install type.

- Completed the Standalone Installation install type (Chapter 2) into a second Oracle home. This is the Oracle home from which you will configure your standalone agent.

The following topics are covered in this chapter:

- Section 5.1, "Creating the Database Schema"

- Section 5.2, "Configuring Your Standalone Domain for the Standalone Agent"

- Section 5.3, "Creating a Standalone Agent in the Master Repository Using ODI Studio"

- Section 5.4, "Starting the Node Manager and Standalone Agent"

- Section 5.5, "Performing Next Steps"

5.1 Creating the Database Schema

Before you can configure the topology for your standalone agent, make sure you have created the necessary schema in your database. See Chapter 3 for instructions.

5.2 Configuring Your Standalone Domain for the Standalone Agent

This section provides instructions for creating a standalone domain for your standalone 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.

This section includes the following topics:

- Section 5.2.1, "Starting the Configuration Wizard"

- Section 5.2.2, "Navigating the Configuration Wizard Screen to Create the Domain"

5.2.1 Starting the Configuration Wizard

To begin domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.

Note:

Make sure the Oracle home is the location where you completed the Standalone Installation install type.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

5.2.2 Navigating the Configuration Wizard Screen to Create the Domain

Follow the instructions in this section to create and configure the domain for the topology.

- Task 1, "Selecting the Domain Type and Domain Home Location"

- Task 2, "Selecting the Configuration Template"

- Task 3, "Selecting the JDK"

- Task 4, "Specifying the Datasource Configuration Type"

- Task 5, "Specifying JDBC Component Schema Information"

- Task 6, "Testing the JDBC Connections"

- Task 7, "Creating Your ODI System Component"

- Task 8, "Configuring Your ODI Server"

- Task 9, "Configuring Node Manager"

- Task 10, "Reviewing Your Configuration Specifications and Configuring the Domain"

Task 1   Selecting the Domain Type and Domain Home Location

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.

Tip:

More information about the Domain home directory can be found in "Choosing a Domain Home" in Planning an Installation of Oracle Fusion Middleware.

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

On the Templates screen, select the following template:

Oracle Data Integrator - Standalone Agent - 12.1.2.0 [odi]

Task 3   Selecting the JDK

On the JDK Selection screen, select the JDK on your system that is certified for use with Oracle Fusion Middleware.

Task 4   Specifying the Datasource Configuration Type

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.

Note:

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:

Field

Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number on which the database listens.

Schema Owner

Schema Password

Enter the user name and password for connecting to the database's Service Table schema. This is the schema user name and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Section 5.1).

The default user name is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Click RCU Data 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.

Tip:

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

Task 5   Specifying JDBC Component Schema Information

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.

Tip:

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

- "Configuring GridLink Data Sources with Oracle RAC"

- "Configuring Multi Data Sources"

More information about the other options on this screen can be found in JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

Task 6   Testing the JDBC Connections

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.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard

Task 7   Creating Your ODI System Component

Use the System Component screen to create a new ODI system component. Click Add and do the following:

1. Under System Component, you can either use the default ODI component (OracleDIAgent1) name, or specify a name of your choice.

2. Under Component Type, ensure that ODI is selected from the drop-down list.

Tip:

More information about the options on this screen can be found in System Components in Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Configuring Your ODI Server

Use the ODI Server Configuration screen to configure access to your ODI server:

Field

Description

System Component

Select the ODI system component (OracleDIAgent1).

Server Listen Address

Specify the IP address of the server where the ODI server should listen. Do not use "localhost."

Server Listen Port

Enter the port number on which ODI server listens.

Supervisor Username

Specify SUPERVISOR as the user name.

Supervisor Password

Specify the Supervisor user password, as specified in Task 6 in Chapter 3 during schema creation.

Preferred Datasource

Use the default OdiMasterRepository; do not change this field.

Tip:

More information about the options on this screen can be found in ODI Server Configuration in Creating WebLogic Domains Using the Configuration Wizard.

Task 9   Configuring Node Manager

The Node Manager screen can be used to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Note:

This screen appears by default in the standalone agent configuration scenario, meaning that you must configure a Node Manager. However, when you start your standalone agent, you have the option of starting the agent without using Node Manager:

- See Section 5.4.1 to start the standalone agent using Node Manager.

- See Section 5.4.2 to start the standalone agent without Node Manager.

Select Per Domain as the Node Manager type, then specify the Node Manager credentials. You will be asked for these credentials when starting your system component with the startComponent command.

Tip:

More information about the options on this screen can be found in Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

More information about the types of Node Manager can be found in "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server.

Task 10   Reviewing Your Configuration Specifications and Configuring the Domain

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.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Click Finish to dismiss the configuration wizard.

5.3 Creating a Standalone Agent in the Master Repository Using ODI Studio

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:

- Section 5.3.1, "Starting ODI Studio"

- Section 5.3.2, "Connecting to the Master Repository"

- Section 5.3.3, "Creating the Standalone Agent"

5.3.1 Starting ODI Studio

To start the ODI Studio:

1. Go to the Oracle home where you have installed Oracle Fusion Middleware Infrastructure and the Enterprise Installation type.

2. Inside that Oracle home, go to the odi/studio directory.

3. Start ODI Studio.
On UNIX operating systems:

./odi.sh

On Windows operating systems:

odi.exe

5.3.2 Connecting to the Master Repository

Before an agent can be created you must connect to the Master repository:

- Task 1, "Getting Started"

- Task 2, "Creating a Login"

- Task 3, "Specifying a New Wallet Password"

- Task 4, "Logging in to the Master Repository"

Note:

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.

Task 1   Getting Started

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.

Task 2   Creating a Login

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.

- User: Specify 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 prefix_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.

Task 3   Specifying a New Wallet Password

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.

Task 4   Logging in to the Master Repository

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:

1. In the drop-down menu in the Login Name field, select the name of the new login you just created.

2. Specify SUPERVISOR as the user name.

3. Provide the password for the Supervisor user.

When you are logged in, follow the instructions in Section 5.3.3 to create the standalone agent.

5.3.3 Creating the Standalone Agent

Follow the instructions in this section to create an ODI agent after you have connected to the repository in ODI Studio.

- Task 1, "Adding an Agent to the Oracle Data Integrator Topology"

- Task 2, "Specifying the Agent Details"

- Task 3, "Saving Your Changes"

Task 1   Adding an Agent to the Oracle Data Integrator Topology

In the navigation pane on the left side, select the Topology tab, then right-click Agents, then select New Agent.

Task 2   Specifying the Agent Details

Specify the new agent details as summarized in the following table:

Field

Description

Name

Specify OracleDIAgent1 as the agent name.

This name must match the system component name specified in Task 8 in Section 5.2.2.

Host

Enter the IP address or name of the machine where the agent is running. Do not use "localhost."

Port

Enter the port number on which the agent listens.

Note:

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.

Task 3   Saving Your Changes

From the ODI Studio menu, select File, then select Save All to save your changes.

5.4 Starting the Node Manager and Standalone Agent

There are two ways to start the standalone agent:

- Section 5.4.1, "Starting the Standalone Agent Using Node Manager"

- Section 5.4.2, "Starting the Standalone Agent Without Node Manager"

5.4.1 Starting the Standalone Agent Using Node Manager

This section contains instructions for:

- Starting the Node Manager

- Starting the Standalone Agent with Node Manager

5.4.1.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

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.

5.4.1.2 Starting the Standalone Agent with Node Manager

After the Node Manager is started, start your standalone agent by going to the DOMAIN_HOME/bin directory and running the following commands:

On UNIX operating systems:

./startComponent.sh OracleDIAgent1

On Windows operating systems:

startComponent.cmd OracleDIAgent1

You will be prompted for the Administrator password for the domain.

To verify that your agent was started, go to the following URL in your browser:

http://examplehost.exampledomain.com:port/oraclediagent

5.4.2 Starting the Standalone Agent Without Node Manager

To start your standalone agent without Node Manager, go to the DOMAIN_HOME/bin directory and run the following commands:

On UNIX operating systems:

./agent.sh -NAME=OracleDIAgent1

On Windows operating systems:

agent.cmd -NAME=OracleDIAgent1

The -NAME parameter must be entered in all CAPS and the name of the agent (in this case, OracleDIAgent1) is also case-sensitive.

5.5 Performing Next Steps

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.

6 Configuring the Standard Installation Topology for the Colocated Standalone Agent

This chapter describes how to create and configure your domain for the colocated standalone agent.

Before you continue, make sure that you have completed the Enterprise Installation install type (Chapter 2). This is for obtaining ODI Studio, which is only available with this install type, and also for obtaining the files necessary to configure a WebLogic domain and colocated standalone agent.

The following topics are covered in this chapter:

- Section 6.1, "Creating the Database Schema"

- Section 6.2, "Configuring Your WebLogic Domain for Your Colocated Standalone Agent"

- Section 6.3, "Creating a Standalone Agent in the Master Repository Using ODI Studio"

- Section 6.4, "Starting the Servers and Standalone Agent"

- Section 6.5, "Performing Next Steps"

6.1 Creating the Database Schema

Before you can configure the topology for your colocated standalone agent, make sure you have created the necessary schema in your database. See Chapter 3 for instructions.

6.2 Configuring Your WebLogic Domain for Your Colocated Standalone Agent

This section provides instructions for creating a WebLogic domain for your colocated standalone 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:

- Section 6.2.1, "Starting the Configuration Wizard"

- Section 6.2.2, "Navigating the Configuration Wizard Screens to Configure the Domain"

6.2.1 Starting the Configuration Wizard

To begin domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

6.2.2 Navigating the Configuration Wizard Screens to Configure the Domain

Follow the instructions in this section to create and configure the domain for the topology.

- Task 1, "Selecting the Domain Configuration Type and Existing Domain"

- Task 2, "Selecting the Configuration Templates"

- Task 3, "Configuring the Administrator Account"

- Task 4, "Specifying the Domain Mode and JDK"

- Task 5, "Specifying the Datasource Configuration Type"

- Task 6, "Specifying JDBC Component Schema Information"

- Task 7, "Testing the JDBC Connections"

- Task 8, "Selecting Advanced Configuration"

- Task 9, "Configuring the Administration Server Listen Address"

- Task 10, "Configuring Node Manager"

- Task 11, "Configuring Your ODI System Component"

- Task 12, "Configuring Your ODI Server"

- Task 13, "Designating a Machine for Your Standalone Colocated Agent"

- Task 14, "Assigning Your System Component to a Machine"

- Task 15, "Reviewing Your Configuration Specifications and Configuring the Domain"

- Task 16, "Writing Down Your Domain Home and Administration Server URL"

Task 1   Selecting the Domain Configuration Type and Existing Domain

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.

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Templates

On the Templates screen, select the Oracle Data Integrator - Standalone Colocated Agent - 12.1.2.0 [odi] template.

Selecting this template automatically selects the following as dependencies:

- Oracle JRF - 12.1.2.0 [oracle_common]

- Oracle Coherence Cluster Extension - 12.1.2.0 [wlserver]

Task 3   Configuring the Administrator Account

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.

Task 4   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

- Select Production in the Domain Mode field.

- Select the Oracle HotSpot JDK in the JDK field.

Tip:

More information about the options on this screen can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

Task 5   Specifying the Datasource Configuration Type

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.

Note:

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:

Field

Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number on which the database listens.

Schema Owner

Schema Password

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 Task 5 in Section 3.3).

The default username is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Click Get RCU Configuration. The following output in the Connection Result Log indicates that the operating succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Tip:

More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard

Task 6   Specifying JDBC Component Schema Information

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.

Tip:

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

- "Configuring GridLink Data Sources with Oracle RAC"

- "Configuring Multi Data Sources"

More information about the other options on this screen can be found in JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

Task 7   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the datasource connections.

A green check mark in the Status column will appear next to the ODI Master Repository component, indicating a successful test. The template you have selected does not require the other datasource connections in the domain to be tested.

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.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard

Task 8   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

- Administration Server
This is required to properly configure the listen address of the Administration Server.

- Node Manager
This is required to configure Node Manager.

Note:

If you want to create a standalone agent for use without an Administration Server or Node Manager (create an agent not managed by WebLogic components), do not select either Administration Server or Node Manager:

1. Skip ahead to Task 11 and follow the instructions to complete domain configuration.

2. Start your standalone agent by using the instructions in Section 6.4.2.2.

- System Components
This is required to configure the standalone agent.

Task 9   Configuring the Administration Server Listen Address

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.

Task 10   Configuring Node Manager

The Node Manager screen can be used to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Note:

This screen will only appear if you selected Node Manager in Task 8:

- After the Node Manager and agent are configured, you start the agent using the instructions in Section 6.4.2.1.

- If you chose not to configure Node Manager, start the agent using the instructions in Section 6.4.2.2.

Select Per Domain as the Node Manager type, then specify the Node Manager credentials.

Tip:

More information about the options on this screen can be found in Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

More information about the types of Node Manager can be found in "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server.

Task 11   Configuring Your ODI System Component

On the System Components screen, specify OracleDIAgent1 in the System Component column as the name of the agent (the name of the Java EE agent created earlier is OracleDIAgent), and make sure ODI is selected in the Component Type column.

Task 12   Configuring Your ODI Server

On the ODI Server Configuration screen, provide the information as described in the following table.

Field

Value

System Component

Make sure OracleDIAgent1 is selected from the drop-down list.

Server Listen Address

Enter the host name or IP address of the system on which the agent resides. Do not use "localhost."

Server Listen Port

Specify the port number on which this agent will listen.

Supervisor Username

Make sure this user name is SUPERVISOR (all CAPS).

Supervisor Password

Specify the password for the SUPERVISOR user, as previously configured in the domain.

Preferred Datasource

Use the default OdiMasterRepository; do not change this field.

Note:

Oracle recommends that you write down the host name and port number of the agent; you will need this later when you create the agent in the master repository (Section 6.3).

Tip:

More information about the other options on this screen can be found in ODI Server Configuration in Creating WebLogic Domains Using the Configuration Wizard

Task 13   Designating a Machine for Your Standalone Colocated Agent

The system component you just created is automatically assigned to a machine called LocalODIMachine. The Machines screen shows that this machine is already created.

In the Node Manager Listen Address field, select the IP address of the host running Node Manager. Do not use "localhost".

Task 14   Assigning Your System Component to a Machine

On the Assign System Components to Machines screen, verify that your system component OracleDIAgent1 is already assigned to the LocalODIMachine.

Tip:

More information about the options on this screen can be found in Assign System Components to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 15   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to update. 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 Update.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Task 16   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the Domain home location and URL of the Administration Server you just configured:

When domain creation is complete, click Finish to dismiss the configuration wizard.

6.3 Creating a Standalone Agent in the Master Repository Using ODI Studio

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:

- Section 6.3.1, "Starting ODI Studio"

- Section 6.3.2, "Connecting to the Master Repository"

- Section 6.3.3, "Creating the Standalone Agent"

6.3.1 Starting ODI Studio

To start the ODI Studio, go to the ORACLE_HOME/odi/studio directory and run the following commands:

On UNIX operating systems:

./odi.sh

On Windows operating systems:

odi.exe

6.3.2 Connecting to the Master Repository

Before an agent can be created you must connect to the Master repository:

- Task 1, "Getting Started"

- Task 2, "Creating a Login"

- Task 3, "Specifying a New Wallet Password"

- Task 4, "Logging in to the Master Repository"

Note:

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.

Task 1   Getting Started

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.

Task 2   Creating a Login

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.

- User: Specify 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 prefix_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.

Task 3   Specifying a New Wallet Password

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.

Task 4   Logging in to the Master Repository

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:

1. In the drop-down menu in the Login Name field, select the name of the new login you just created.

2. Specify SUPERVISOR as the user name.

3. Provide the password for the Supervisor user.

When you are logged in, follow the instructions in Section 6.3.3 to create the standalone agent.

6.3.3 Creating the Standalone Agent

Follow the instructions in this section to create an ODI agent after you have connected to the repository in ODI Studio.

- Task 1, "Adding an Agent to the Oracle Data Integrator Topology"

- Task 2, "Specifying the Agent Details"

- Task 3, "Saving Your Changes"

Task 1   Adding an Agent to the Oracle Data Integrator Topology

In the navigation pane on the left side, select the Topology tab, then right-click Agents, then select New Agent.

Task 2   Specifying the Agent Details

Specify the new agent details as summarized in the following table:

Field

Description

Name

Specify OracleDIAgent1 as the agent name.

This name must match the system component name in Task 11 in Section 6.2.2.

Host

Enter the IP address or name of the machine where the agent is running. Do not use "localhost."

Port

Enter the port number on which the agent listens.

Note:

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.

Task 3   Saving Your Changes

From the ODI Studio menu, select File, then select Save All to save your changes.

6.4 Starting the Servers and Standalone Agent

After configuration is complete, do the following to access the tools with which you can manage your domain:

Note:

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.

- Section 6.4.1, "Starting the Administration Server"

- Section 6.4.2, "Starting the Colocated Standalone Agent"

6.4.1 Starting the Administration Server

Starting the Administration Server enables you to manage your agent using Oracle Fusion Middleware control. If you do not want to do this, skip this section and go to Section 6.4.2.2 to start your agent.

If you want to start the Administration Server, go the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen in Task 4, you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in Task 3.

Tip:

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 16.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

http://administration_server_host:administration_server_port/console

The default Administration Server port number is 7001.

For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.

6.4.2 Starting the Colocated Standalone Agent

There are two ways to start the standalone agent:

- If you chose to configure a Node Manager (Task 10), use the instructions in Section 6.4.2.1 to start your standalone agent.

- If you want to start your standalone agent without Node Manager, use the instructions in Section 6.4.2.2.

6.4.2.1 Starting the Agent Using Node Manager

This section contains instructions for:

- Starting the Node Manager

- Starting the Agent

6.4.2.1.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

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.

6.4.2.1.2 Starting the Agent

After the Node Manager is started, go to the DOMAIN_HOME/bin directory and run the following commands:

On UNIX operating systems:

./startComponent.sh OracleDIAgent1

On Windows operating systems:

startComponent.cmd OracleDIAgent1

You will be prompted for the Administrator password for the domain.

To verify that your agent was started, go to the following URL in your browser:

http://examplehost.exampledomain.com:port/oraclediagent

6.4.2.2 Starting the Agent Without Node Manager

To start your standalone agent without Node Manager, go to the DOMAIN_HOME/bin directory and run the following commands:

On UNIX operating systems:

./agent.sh -NAME=OracleDIAgent1

On Windows operating systems:

agent.cmd -NAME=OracleDIAgent1

The -NAME parameter must be entered in all CAPS and the name of the agent (in this case, OracleDIAgent1) is also case-sensitive.

6.5 Performing Next Steps

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.

7 Next Steps After Configuring an Oracle Data Integrator Domain

This chapter describes common tasks you might want to perform on a newly created domain for Oracle Data Integrator.

The following sections are included in this chapter:

- Section 7.1, "Performing Basic Administrative Tasks"

- Section 7.2, "Performing Additional Domain Configuration Tasks"

- Section 7.3, "Preparing Oracle Data Integrator for Development"

- Section 7.4, "Preparing Your Environment For High Availability"

7.1 Performing Basic Administrative Tasks

Table 7-1 lists some common administration tasks you will likely want to perform on your newly created domain.

Table 7-1 Basic Administration Tasks for a New Domain

Task

Description

More Information

Getting familiar with Fusion Middleware administration tools

Get familiar with the various tools available which you can use to manage your environment.

"Overview of Oracle Fusion Middleware Administration Tools" in Administering Oracle Fusion Middleware.

Starting and stopping products and servers

Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components.

"Starting and Stopping Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

Configuring Secure Sockets Layer (SSL)

Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL.

"Configuring SSL in Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

Monitoring Oracle Fusion Middleware

Learn how to keep track of the status of Oracle Fusion Middleware components.

"Monitoring Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

Understanding Backup and Recovery Procedures

Learn the recommended backup and recovery procedures for Oracle Fusion Middleware.

"Introducing Backup and Recovery" in Administering Oracle Fusion Middleware.

7.2 Performing Additional Domain Configuration Tasks

Table 7-2 lists some additional tasks you will likely want to perform on your newly created domain.

Table 7-2 Additional Domain Configuration Tasks

Task

Description

More Information

Deploying Applications

Learn how to deploy your applications to Oracle Fusion Middleware.

"Deploying Applications" part in Administering Oracle Fusion Middleware.

Adding a Web Tier front-end to your domain

Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server.

Follow the instructions to install and configure Oracle HTTP Server in the WebLogic Server domain in Installing and Configuring Oracle HTTP Server.

Also refer to "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middleware for important information.

Tuning and configuring Coherence for your topology

The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment.

For information about Coherence clusters, see "Configuring and Managing Coherence Clusters" in Administering Clusters for Oracle WebLogic Server.

For information about tuning Coherence, see Administering Oracle Coherence.

For information about storing HTTP session data in Coherence, see "Using Coherence*Web with WebLogic Server" in Administering HTTP Session Management with Oracle Coherence*Web.

For more information about creating and deploying Coherence applications, see Developing Oracle Coherence Applications for Oracle WebLogic Server.

7.3 Preparing Oracle Data Integrator for Development

ITable 7-3 lists additional tasks that you may perform to prepare Oracle Data Integrator for development.

Table 7-3 Tasks for Preparing Oracle Data Integrator for Development

Task

Description

More Information

Creating a logical agent

Multiple physical agents having identical roles in different environments can be grouped under the same logical agent. A logical agent is related to physical agents through contexts. When starting an execution, you indicate the logical agent and the context. Oracle Data Integrator will translate this information into a single physical agent that will receive the execution request.

To create a new logical agent, see the instructions in "Creating a Logical Agent" in Developer's Guide for Oracle Data Integrator.

Managing the agents

Once your agents are defined in the topology, you can start, deploy, and stop your agents as needed.

See "Managing Agents" in Developer's Guide for Oracle Data Integrator.

Administer your repositories

Additional tasks are available to create and connect to new master and work repositories, changing passwords, and other administrative tasks to help you customize your environment

See "Administering Repositories" in Developer's Guide for Oracle Data Integrator.

Create a server template for your Java EE agent

Oracle Data Integrator provides a Server Template Generation wizard to help you create a server template for a run-time agent.

"Creating a Server Template for the Java EE Agent" in Developer's Guide for Oracle Data Integrator.

7.4 Preparing Your Environment For High Availability

Table 7-4 provides a list of tasks to perform if you want to scale out your standard installation environment for high availability.

Table 7-4 Tasks Required to Prepare Your Environment for High Availability

Task

Description

More Information

Configuring Node Manager

Node Manager enables you to start, shut down, and restart the Administration Server and Managed Server instances from a remote location, making this an essential utility for any high availability environment.

Administering Node Manager for Oracle WebLogic Server.

Scaling out to multiple host computers

To enable high availability, it is important to provide failover capabilities to another host computer. That way, if one computer goes down, your environment can continue to serve the consumers of your deployed applications.

"Scaling Out a Topology (Machine Scaleout)" in the High Availability Guide.

Configuring high availability for your Web Tier components.

If you have added a Web tier front-end, then you must configure the Web Tier for high availability, as well as the WebLogic Server software.

"Configuring High Availability for Web Tier Components" in High Availability Guide.

Setting up a front-end load balancer

A load balancer can be used to distribute requests across servers more evenly.

"Server Load Balancing in a High Availability Environment" and "Configure Load Balancer" in High Availability Guide.

8 Deinstalling Oracle Data Integrator

This chapter describes how to deinstall or reinstall Oracle Data Integrator.

You should always use the instructions provided in this chapter for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this chapter will ensure that the software is properly removed.

The following topics are covered in this chapter:

- Section 8.1, "Understanding Product Deinstallation"

- Section 8.2, "Stopping Oracle Fusion Middleware"

- Section 8.3, "Removing Your Database Schemas"

- Section 8.4, "Deinstalling the Software"

- Section 8.5, "Removing the Oracle Home Directory Manually"

- Section 8.6, "Removing Your Domain and Application Data"

- Section 8.7, "Removing Your ODI Wallet Information"

- Section 8.8, "Deinstalling Oracle Fusion Middleware Infrastructure"

- Section 8.9, "Reinstalling the Software"

8.1 Understanding Product Deinstallation

The Oracle Fusion Middleware deinstaller removes the software from the Oracle home directory from which it is started. Table 8-1 summarizes the procedure and provides links to supporting documentation.

Table 8-1 Roadmap for Deinstalling Oracle Data Integrator

Task

Description

Documentation

Stop Oracle Fusion Middleware.

All servers and processes in your domain should be stopped before running the deinstaller.

See Section 8.2.

Remove your database schemas.

Run Repository Creation Utility to remove your database schemas.

See Section 8.3.

Remove the software.

Run the product deinstaller to remove Oracle Fusion Middleware Infrastructure.

See Section 8.4.

Remove the Oracle home directory.

The deinstaller does not remove all files and folders from the Oracle home directory. After the deinstaller is finished, you must manually remove the Oracle home to complete your product removal.

See Section 8.5.

Remove your domain and application data.

The deinstaller does not remove data contained in your Domain home or Application home directories, even if they are located inside the Oracle home. You must remove these directories manually.

See Section 8.6.

Remove Oracle Fusion Middleware Infrastructure.

In you created the topology for Java EE agents, you can also remove the Oracle Fusion Middleware Infrastructure software from your system.

See Section 8.8.

8.2 Stopping Oracle Fusion Middleware

Stopping Oracle Fusion Middleware involves the following:

- Section 8.2.1, "Stopping Your Oracle Data Integrator Agents"

- Section 8.2.2, "Stopping the Oracle Fusion Middleware Environment"

8.2.1 Stopping Your Oracle Data Integrator Agents

Before running the deinstaller, you should stop all agents that are running.

To stop your standalone agent, go to the DOMAIN_HOME/bin directory and run the following commands:

On UNIX operating systems:

./stopComponent.sh OracleDIAgent1

On Windows operating systems:

stopComponent.cmd OracleDIAgent1

8.2.2 Stopping the Oracle Fusion Middleware Environment

Before running the deinstaller, you should stop all servers and processes associated with the Oracle home you are going to remove.

For more information, see "Stopping an Oracle Fusion Middleware Environment" in Administering Oracle Fusion Middleware.

8.3 Removing Your Database Schemas

Before your Oracle home is removed, you should run Repository Creation Utility to remove the database schemas associated with this domain. Each domain has its own set of schemas, uniquely identified by a custom prefix (see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility). This set of schemas cannot be shared with any other domain (see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility).

If there are multiple sets of schemas on your database, be sure to identify the schema prefix associated with the domain you are removing.

For schema removal instructions, see "Dropping Schemas" in Creating Schemas with the Repository Creation Utility.

8.4 Deinstalling the Software

Follow the instructions in this section to start the product deinstaller and remove the software.

- Section 8.4.1, "Starting the Deinstaller"

- Section 8.4.2, "Navigating the Deinstallation Screens"

If you want to perform a silent (command-line) deinstallation, see "Running the Oracle Universal Installer for Silent Deinstallation" in Installing Software with the Oracle Universal Installer.

8.4.1 Starting the Deinstaller

To start the deinstaller on a Windows operating system, do one of the following:

1. Use a file manager window to go to the ORACLE_HOME\oui\bin directory and double click on deinstall.cmd.

2. From the command line, go to the ORACLE_HOME\oui\bin and enter the following command:

deinstall.cmd

3. From the Start menu, select All Programs, then select Oracle, then select OracleHome, then select Uninstall Oracle Middleware.

To start the deinstaller on a UNIX operating system, go to the ORACLE_HOME/oui/bin directory and enter the following command:

./deinstall.sh

8.4.2 Navigating the Deinstallation Screens

The deinstallation program displays a series of screens, in the order listed in Table 8-2.

If you need additional help with any of the deinstallation screens, click the screen name.

Table 8-2 Deinstall Screens and Descriptions

Screen

Description

Welcome

This screen introduces you to the product deinstaller.

Deinstallation Summary

This screen shows the Oracle home directory and its contents that will be deinstalled. Verify that this is the correct directory.

Click Deinstall to begin removing the software.

Deinstallation Progress

This screen shows the progress of the deinstallation.

Deinstallation Complete

This screen appears when the deinstallation is complete. Review the information on this screen, then click Finish to dismiss the deinstaller.

8.5 Removing the Oracle Home Directory Manually

After the deinstaller is finished, you must manually remove your Oracle home directory and any existing sub-directories that were not removed by the deinstaller. For example, if your Oracle home directory was /home/oracle/product/Oracle_Home on a UNIX operating system:

> cd /home/oracle/product
> rm -rf Oracle_Home

On a Windows operating system, if your Oracle home directory was C:\Oracle\Product\Oracle_Home, use a file manager window and navigate to the C:\Oracle\Product directory, then right-click on the Oracle_Home folder and select Delete.

8.6 Removing Your Domain and Application Data

To remove your domain and application data:

1. Manually remove your Domain home directory.
For example, if your Domain home directory was /home/oracle/config/domains/odi_domain on a UNIX operating system:

> cd /home/oracle/config/domains
> rm -rf odi_domain

On a Windows operating system, if your Domain home directory was C:\Oracle\Config\domains\odi_domain, use a file manager window and navigate to the C:\Oracle\Config\domains directory, then right-click on the odi_domain folder and select Delete.

2. Manually remove your Application home directory.
For example, if your Application home directory was /home/Oracle/config/applications/odi_domain on a UNIX operating system:

> cd /home/Oracle/config/applications
> rm -rf odi_domain

On a Windows operating system, if your Application home directory was C:\Oracle\Config\applications\odi_domain, use a file manager window and navigate to the C:\Oracle\Config\applications directory, then right-click on the odi_domain folder and select Delete.

3. Backup the domain_registry.xml file in your Oracle home, then edit the file and remove the line associated with the domain you are removing. For example, to remove the odi_domain, find the following line and remove it:

<domain location="/home/Oracle/config/domains/odi_domain"/>

Save and exit the file when you are finished.

8.7 Removing Your ODI Wallet Information

ODI wallet information should be manually removed; the deinstaller does not remove this information. In the event that Oracle Data Integrator is reinstalled on the same system by the same user, the wallet information will be remembered unless it is manually removed.

Wallet information is stored in a directory inside the user's home directory. For example, on a UNIX operating system:

/home/exampleuser/.odi

On a Windows operating system:

C:\Users\exampleuser\AppData\Roaming\odi

8.8 Deinstalling Oracle Fusion Middleware Infrastructure

After you have removed your Oracle Data Integrator software, you can choose to remove the Oracle Fusion Middleware Infrastructure from your machine. Before doing so, make sure there are no other products using the Infrastructure; those products will no longer function once the Infrastructure is removed.

For deinstallation instructions, see "Deinstalling Oracle Fusion Middleware Infrastructure" in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

8.9 Reinstalling the Software

You can reinstall your software into the same Oracle home as a previous installation only if you have deinstalled the software according to the instructions in this chapter, including manually removing the Oracle home directory. When you reinstall, you can then specify the same Oracle home as your previous installation.

Consider the following cases where the Oracle home is not empty:

- Installing in an existing Oracle home that contains the same feature sets.
The installer will warn you that the Oracle home you specified during the installation already contains the same software you are trying to install. Your options are to:

1. Select a different installation type. In this case, only the feature sets that do not already exist in the Oracle home directory will be installed.

2. Select a different Oracle home directory.

- Installing in an existing, non-empty Oracle home.
For example, suppose that you have chosen to create your Domain home or Application home somewhere inside your existing Oracle home. This data is not removed during the deinstallation process, so if you attempt to reinstall into the same Oracle home, the installer will not allow it. Your options are to:

1. Deinstall your software from the Oracle home as described in this chapter, and then remove the Oracle home directory. After this is complete, you can reinstall and reuse the same Oracle home location, using the instructions in Chapter 2. Any domain or application data that was in the Oracle home will have to be re-created.

2. Select a different Oracle home directory.

A Understanding the Oracle Data Integrator Distribution

This appendix describes the products and feature sets available in the Oracle Data Integrator distribution.

The Oracle Data Integrator distribution contains the products and feature sets described in Table A-1. Unless otherwise noted, all products and feature sets are available with both Standalone Installation and Enterprise Installation types.

Table A-1 Oracle Data Integrator Products and Feature Sets

Product

Feature Set

Description

Oracle Data Integrator features

ODI SDK

The ODI Software Development Kit (SDK) is a Java API for performing run-time and design-time operations.

ODI 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.

This feature set is only available with the Enterprise Installation type.

ODI Standalone Agent

The standalone agent runs as its own process and is deployed in a domain as a system component.

It can be configured in a standalone domain and managed by WebLogic Management Framework, or it can be colocated in a WebLogic domain and managed by Fusion Middleware Control.

ODI J2EE

This is the Java EE agent, which is a Java EE application that is deployed and runs on a Managed Server configured in a WebLogic domain.

This feature set is only available with the Enterprise Installation type.

ODI Standalone Agent Template

This template provides the domain files required when your Oracle Data Integrator installation is not being managed by Oracle WebLogic Server.

This feature set is only available with the Standalone Installation type.

Internal Features

Apache Ant

This is a software tool used for automating build processes.

FMW Upgrade

This is the upgrade assistant that can be used to upgrade your 11g Oracle Data Integrator software to 12c.

For more information, see Upgrading Oracle Data Integrator.

OPatch

The OPatch utility is a tool that allows the application and rollback of interim patches to Oracle products.

Repository Creation Utility

The Repository Creation Utility (RCU) is used for creating database schemas.

This feature set is included with the Standalone Installation type. The Enterprise Installation type does not include RCU since Oracle Fusion Middleware Infrastructure is a requirement and RCU is included with the Oracle Fusion Middleware Infrastructure distribution.

B Troubleshooting Oracle Data Integrator

This appendix describes solutions to common problems that you might encounter when installing Oracle Data Integrator.

The following sections are included:

- Section B.1, "Understanding General Troubleshooting Tips"

- Section B.2, "Understanding Installation and Configuration Log Files"

- Section B.3, "Verifying ODI Client and Repository Compatibility"

- Section B.4, "Need More Help?"

B.1 Understanding General Troubleshooting Tips

If you encounter an error during installation:

- Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network:

http://www.oracle.com/technetwork/documentation/index.html#middleware

- Verify your system and configuration is certified. Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

- Verify your system meets the minimum system requirements. Refer to the System Requirements and Specifications document:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

- If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

- If an error occurred while the installer is copying or linking files:

1. Note the error and review the installation log files.

2. Remove the failed installation by following the steps in Chapter 8.

3. Correct the issue that caused the error.

4. Restart the installation.

B.2 Understanding Installation and Configuration Log Files

The installation and configuration log files can contain useful information to help troubleshoot any issues you may encounter. For more information about these log files and their contents, see "Configuring Installation and Configuration Log Files" in Installing Software with the Oracle Universal Installer.

B.3 Verifying ODI Client and Repository Compatibility

If you are using Oracle Data Integrator with other Oracle Fusion Middleware products, make sure you have read the Understanding Interoperability and Compatibility.

Oracle strongly recommends that you use identical versions of different ODI components such as ODI Studio, ODI Console, standalone and J2EE Agents, and executable scripts for a specific site or platform. In addition, you should make sure your Master and Work Repository versions are compatible with these components (Table B-1).

Table B-1 ODI Component and Repository Compatibility

Oracle Data Integrator Component Version

Repository Version

12c (12.1.2)

05.01.01.16

11g Release 1 (11.1.1.0.7)

04.03.04.02

11g Release 1 (11.1.1.6.0)

04.03.04.02

B.4 Need More Help?

If this appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support (formerly OracleMetaLink):

https://support.oracle.com/

If you are unable to find a solution for your problem, open a service request.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.