Oracle® Fusion Middleware

Installing and Configuring Oracle Data Integrator

12c (12.2.1)

E55859-04

January 2017

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.2.1)

E55859-04

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

Primary Author: Uma Shankar

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, then 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.

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

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Contents

List of Examples

List of Figures

List of Tables

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Planning the Oracle Data Integrator Installation

- 1.1 Introduction to Oracle Data Integrator

- 1.2 About Oracle Data Integrator Installation

- 1.2.1 Using the Standard Installation Topology as a Starting Point

- 1.2.2 Using this Document in an Upgrade Scenario

- 1.2.3 Using this Document to Create a Domain

- 1.3 About Oracle Data Integrator Run-Time Agents

- 1.4 About Oracle Data Integrator Studio

- 1.5 About the Oracle Data Integrator Topology

- 1.6 Understanding the Oracle Data Integrator Standard Installation Topologies

- 1.6.1 About the Oracle Data Integrator Java EE Agent Standard Installation Topology

- 1.6.2 About the Oracle Data Integrator Standalone Agent Standard Installation Topology

- 1.6.3 About the Oracle Data Integrator Standalone Collocated Agent Standard Installation Topology

- 1.7 Roadmap for Installing and Configuring a Standard Installation Topology

- 1.8 Obtaining the Necessary Product Distributions

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

- 2.4 Installing Oracle Data Integrator in Silent Mode

3 Creating the Master and Work Repository Schemas

- 3.1 Configuring a Certified Database

- 3.2 Starting the Repository Creation Utility

- 3.3 Navigating the Repository Creation Utility Screens to Create the Schema

4 Configuring Oracle Data Integrator Studio

- 4.1 About Oracle Data Integrator Studio

- 4.2 Creating the Database Schemas

- 4.3 Setting the Same Time Zone for the Agent and Repository

- 4.4 Adding Libraries to ODI Studio

- 4.5 Setting Java Home for ODI Studio

- 4.6 Starting ODI Studio

- 4.7 Connecting to the Master Repository

- 4.8 Creating an Agent in the Master Repository with ODI Studio

- 4.9 Starting the New Agent

- 4.10 Performing Next Steps

5 Configuring the Domain for a Java EE Agent

- 5.1 Creating the Database Schema

- 5.2 Generating a Template for a Java EE Agent

- 5.3 Creating a Java EE Agent with Oracle Data Integrator Studio

- 5.4 Configuring the Domain for a Java EE Agent

- 5.4.1 Starting the Configuration Wizard

- 5.4.2 Navigating the Configuration Wizard Screens to Configure the Domain

- 5.5 Adding Libraries to a Java EE Agent

- 5.6 Starting a Java EE Agent

- 5.6.1 Starting Node Manager

- 5.6.2 Starting the Administration Server

- 5.6.3 Starting the ODI Managed Server

- 5.7 Performing Next Steps

6 Configuring the Domain for a Standalone Agent

- 6.1 Creating the Database Schema

- 6.2 Creating a Standalone Agent in the Master Repository with ODI Studio

- 6.3 Configuring the Standalone Domain for the Standalone Agent

- 6.3.1 Starting the WebLogic Server Configuration Wizard

- 6.3.2 Navigating the Configuration Wizard Screen to Create the Domain

- 6.4 Adding Libraries to a Standalone or Standalone Collocated Agent

- 6.5 Starting a Standalone or Standalone Collocated Agent Using Node Manager

- 6.5.1 Starting Node Manager

- 6.5.2 Starting a Standalone or Standalone Collocated Agent

- 6.6 Starting a Standalone or Standalone Collocated Agent Without Node Manager

- 6.7 Performing Next Steps

7 Configuring the Domain for a Standalone Collocated Agent

- 7.1 Creating the Database Schema

- 7.2 Creating a Standalone Agent in the Master Repository Using Oracle Data Integrator Studio

- 7.3 Configuring Your WebLogic Domain for Your Standalone Collocated Agent

- 7.3.1 Starting the Configuration Wizard

- 7.3.2 Navigating the Configuration Wizard Screens to Configure the Domain

- 7.4 Adding Libraries to a Standalone or Standalone Collocated Agent

- 7.5 Starting a Standalone Collocated Agent with Node Manager

- 7.5.1 Starting Node Manager

- 7.5.2 Starting the Standalone Collocated Agent

- 7.6 Starting a Standalone Collocated Agent Without Node Manager

- 7.7 Performing Next Steps

8 Configuring an Oracle Data Integrator New Domain

- 8.1 Performing Basic Administrative Tasks

- 8.2 Performing Additional Domain Configuration Tasks

- 8.3 Preparing Oracle Data Integrator for Development

- 8.4 Preparing Your Environment For High Availability

9 Uninstalling Oracle Data Integrator

- 9.1 Understanding Product Uninstallation

- 9.2 Stopping Agents and Oracle Fusion Middleware

- 9.2.1 Stopping the Oracle Data Integrator Agents

- 9.2.2 Stopping the Oracle Fusion Middleware Environment

- 9.3 Removing Database Schemas

- 9.4 Uninstalling the Software

- 9.4.1 Starting the Uninstaller

- 9.4.2 Navigating the Uninstallation Screens

- 9.5 Removing the Oracle Home Directory Manually

- 9.6 Removing the Program Shortcuts on Windows Operating Systems

- 9.7 Removing Your Domain and Application Data

- 9.8 Removing Oracle Data Integrator Wallet Information

- 9.9 Uninstalling Oracle Fusion Middleware Infrastructure

- 9.10 Reinstalling the Software

A Understanding Oracle Data Integrator Distribution

- A.1 Oracle Data Integrator Components

B Troubleshooting Oracle Data Integrator

- B.1 General Troubleshooting Tips

- B.2 Troubleshooting Using Installation and Configuration Log Files

- B.3 Verifying ODI Client and Repository Compatibility

- B.4 Need More Help?

C About the Secondary Topologies for Oracle Data Integrator

- C.1 Oracle Data Integrator Topology with the Oracle Data Integrator Console

- C.2 Using the Oracle Data Integrator Console

List of Examples

List of Figures

- 1-1 Standard Installation Topology for an ODI Java EE Agent

- 1-2 Standard Installation Topology for the Standalone Agent

- 1-3 Standard Installation Topology for the Standalone Collocated Agent

- C-1 Secondary Installation Topology including the ODI Console

List of Tables

- 1-1 Description of the Elements in the Java EE Standard Installation Topology

- 1-2 Description of the Elements in the Standalone Agent Standard Installation Topology

- 1-3 Description of the Elements in the Standalone Collocated Agent Standard Installation Topology

- 1-4 Oracle Data Integrator Installation Roadmap

- 2-1 Oracle Data Integrator Installation Screens

- 8-1 Basic Administration Tasks for a New Domain

- 8-2 Additional Domain Configuration Tasks

- 8-3 Tasks for Preparing Oracle Data Integrator for Development

- 9-1 Roadmap to Uninstall Oracle Fusion Middleware

- 9-2 Uninstaller Screens Descriptions

- A-1 Oracle Data Integrator Components and Features

- B-1 ODI and Repository Compatible Versions

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

- Documentation Accessibility

- Related Documents

- Conventions

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.

Parent topic: Preface

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 that have purchased support 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.

Parent topic: Preface

Related Documents

Refer to the Oracle Fusion Middleware Library for additional information.

- For Oracle Data Integrator information, see Oracle Data Integrator Documentation.

- For installation information, see Fusion Middleware Installation Documentation.

- For upgrade information, see Fusion Middleware Upgrade Documentation.

- For administration-related information, see Fusion Middleware Administration Documentation.

- For release-related information, see Fusion Middleware Release Notes.

Parent topic: Preface

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.

Parent topic: Preface

1 Planning the Oracle Data Integrator Installation

Learn how to prepare your system before you install Oracle Data Integrator.

Understand the information in this chapter thoroughly to minimize issues during product installation and configuration.

This chapter includes the following sections:

- Introduction to Oracle Data Integrator
Install Oracle Data Integrator (ODI) on your system or visit the Oracle Java Cloud as a Service to install and configure ODI.

- About Oracle Data Integrator Installation
Learn about installing Oracle Data Integrator in the standard topology, when upgrading a domain, or when extending a domain.

- About Oracle Data Integrator Run-Time Agents
At design time, developers generate scenarios from the business rules that they have designed. The code of these scenarios is then retrieved from the repository by a run-time agent. This agent then connects to the data servers and orchestrates the code execution on these servers.

- About Oracle Data Integrator Studio
Oracle Data Integrator Studio is a developer's interface for configuring and managing ODI.

- About the Oracle Data Integrator Topology
The Oracle Data Integrator topology is the physical and logical representation of the Oracle Data Integrator architecture and components.

- Understanding the Oracle Data Integrator Standard Installation Topologies
Learn how to install and configure a standard installation topology for Oracle Data Integrator.

- Roadmap for Installing and Configuring a Standard Installation Topology
This roadmap provides all the steps required to install and configure a standard Oracle Data Integrator installation topology.

- Obtaining the Necessary Product Distributions
Learn about the pre-requisites to create a Java EE or standalone collocated agent.

1.1 Introduction to Oracle Data Integrator

Install Oracle Data Integrator (ODI) on your system or visit the Oracle Java Cloud as a Service to install and configure ODI.

This guide explains how to install ODI on your local disks using your on-premises hardware. An alternative is to subscribe to the Oracle Cloud Java as a Service (JCS) and then install and configure ODI on JCS.

For details on how to install and configure ODI on JCS, see Provisioning ODI.

1.2 About Oracle Data Integrator Installation

Learn about installing Oracle Data Integrator in the standard topology, when upgrading a domain, or when extending a domain.

This topic the following topics:

- Using the Standard Installation Topology as a Starting Point
Use the standard installation topology when installing Oracle Data Integrator. Other starting point topologies are available.

- Using this Document in an Upgrade Scenario
Install Oracle Data Integrator when you are updating the product.

- Using this Document to Create a Domain
The procedures in this guide describe how to create a new domain. The assumption is that no other Oracle Fusion Middleware products are installed on your system.

1.2.1 Using the Standard Installation Topology as a Starting Point

Use the standard installation topology when installing Oracle Data Integrator. Other starting point topologies are available.

This guide helps you create the standard installation topologies for Oracle Data Integrator (Understanding the Oracle Data Integrator Standard Installation Topologies). The Java EE Agent topology (About the Oracle Data Integrator Java EE Agent Standard Installation Topology) can be extended to be highly available and secure, making it 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.

1.2.2 Using this Document in an Upgrade Scenario

Install Oracle Data Integrator when you are updating the product.

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.2.3 Using this Document to Create a Domain

The procedures in this guide describe how to create a new domain. The assumption is that no other Oracle Fusion Middleware products are installed on your system.

If you have installed and configured other Oracle Fusion Middleware products on your system (for example, Fusion Middleware Infrastructure, with a domain that is up and running), use the same instructions to extend your existing domain. If you choose extend an existing domain, read Installing Multiple Products in the Same Domain in Planning an Installation of Oracle Fusion Middleware.

1.3 About Oracle Data Integrator Run-Time Agents

At design time, developers generate scenarios from the business rules that they have designed. The code of these scenarios is then retrieved from the repository by a run-time agent. This agent then connects to the data servers and orchestrates the code execution on these servers.

The types of run-time agents that can be configured in the ODI installation topology are:

- Standalone agent

- Standalone collocated agent

- Java EE agent

For more information, see Run-Time Agent in Understanding Oracle Data Integrator.

1.4 About Oracle Data Integrator Studio

Oracle Data Integrator Studio is a developer's interface for configuring and managing ODI.

To learn how to use ODI Studio to configure and manage your ODI topology, see Configuring Oracle Data Integrator Studio.

1.5 About the Oracle Data Integrator Topology

The Oracle Data Integrator topology is the physical and logical representation of the Oracle Data Integrator architecture and components.

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.

For more information, see Setting up a Topology in Developing Integration Projects with Oracle Data Integrator.

1.6 Understanding the Oracle Data Integrator Standard Installation Topologies

Learn how to install and configure a standard installation topology for Oracle Data Integrator.

You can install and configure any of the following Oracle Data Integrator standard installation topologies:

- Standard installation topology for the Java EE agent.
See About the Oracle Data Integrator Java EE Agent Standard Installation Topology.

- Standard installation topology for the standalone agent.
The standalone agent is installed and configured in a standalone domain. See About the Oracle Data Integrator Standalone Agent Standard Installation Topology.

- Standard installation topology for the standalone colocated agent.
The standalone agent is installed and configured with a WebLogic domain and managed using the Node Manager and Administration Server. SeeAbout the Oracle Data Integrator Standalone Collocated Agent Standard Installation Topology.

For procedure details, see Roadmap for Installing and Configuring a Standard Installation Topology.

This topic incudes the following tasks:

- About the Oracle Data Integrator Java EE Agent Standard Installation Topology
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.

- About the Oracle Data Integrator Standalone Agent Standard Installation Topology
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.

- About the Oracle Data Integrator Standalone Collocated Agent Standard Installation Topology
This installation topology represents a standalone agent configured in a WebLogic domain, managed by an Administration Server and Node Manager. The domain is configured on a single host and requires a supported database where the required Fusion Middleware schemas are installed.

1.6.1 About the Oracle Data Integrator Java EE Agent Standard Installation Topology

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. The Java EE agent is installed into an existing Oracle home containing Oracle Fusion Middleware Infrastructure. ODI Console, ODI Studio, and the plugin for Fusion Middleware Control are also installed in the topology.

Note:

The infrastructure can use more than one machine for scalability and high-availability considerations. See Preparing Your Environment For High Availability for more information.

Figure 1-1 shows the standard installation topology for an Oracle Data Integrator Java EE agent.

Figure 1-1 Standard Installation Topology for an ODI Java EE Agent

For configuration instructions, see Configuring the Domain for a Java EE Agent.

Table 1-1 describes all elements in this standard installation topology illustration.

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.

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 Overview of 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 Overview of 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 run-time agent.

1.6.2 About the Oracle Data Integrator Standalone Agent Standard Installation Topology

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.

Figure 1-2 shows the standard installation topology for the Oracle Data Integrator standalone agent.

Figure 1-2 Standard Installation Topology for the Standalone Agent

For configuration instructions, see Configuring the Domain for a Standalone Agent.

Table 1-2 describes all elements in this standard installation topology illustration.

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. A system component corresponds to a standalone agent.

For more information, see What Is a System Component? in Understanding Oracle Fusion Middleware.

1.6.3 About the Oracle Data Integrator Standalone Collocated Agent Standard Installation Topology

This installation topology represents a standalone agent configured in a WebLogic domain, managed by an Administration Server and Node Manager. The domain is configured on a single host and requires a supported database where the required Fusion Middleware schemas are installed.

Figure 1-3 shows the standard installation topology for the standalone collocated agent.

Figure 1-3 Standard Installation Topology for the Standalone Collocated Agent

For configuration instructions, see Configuring the Domain for a Standalone Collocated Agent.

Table 1-3 describes all elements in this standard installation topology.

Table 1-3 Description of the Elements in the Standalone Collocated 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.

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. A system component corresponds to a standalone agent.

For more information, see What Is a System Component? in Understanding Oracle Fusion Middleware.

1.7 Roadmap for Installing and Configuring a Standard Installation Topology

This roadmap provides all the steps required to install and configure a standard Oracle Data Integrator installation topology.

Table 1-4 shows the high-level 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.

Check for any mandatory patches that will be required before or after the installation

Review the Oracle Fusion Middleware Infrastructure release notes to see if there are any mandatory patches required for the software products you are installing.

See Install and Configure in Release Notes for Oracle Fusion Middleware Infrastructure.

Obtain the appropriate distribution

See Obtaining the Necessary Product Distributions.

Determine your installation directories

Verify that the installer can access or create the required installer directories. Also, verify that the directories exist on systems that meet the minimum requirements.

See What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

Install prerequisite software

Install Oracle Fusion Middleware Infrastructure to create the Oracle home directory for Oracle Data Integrator.

For Oracle Fusion Middleware Infrastructure , seeOracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure. You only need to perform the installation for Infrastructure. You do not need to configure a domain for Infrastructure.

Install the software

Run the Oracle Universal Installer to install Oracle Data Integrator.

Installing the software transfers the software to your system and creates the Oracle home directory.

See Installing Oracle Data Integrator.

Create the Master and Work Repository schemas.

Use the Repository Creation Utility (RCU) to create the Master and Work Repository database schemas.

See Creating the Master and Work Repository Schemas.

Create the physical domain

Use ODI Studio to create the physical agent.

See Configuring Oracle Data Integrator Studio to create the physical agent.

Create and configure your domain

Use the configuration wizard to create and configure your domain.

See Configuring the Domain for a Standalone Agent to create the topology for a standalone agent.

See Configuring the Domain for a Standalone Collocated Agent to create the topology for a standalone collocated agent.

See Configuring the Domain for a Java EE Agent to create the topology for a Java EE agent.

Administer and prepare your domain for high availability

Discover additional tools and resources to administer your domain.

If you have configured a Java EE agent, you can also prepare and configure your domain to be highly available.

See Preparing Your Environment For High Availability.

1.8 Obtaining the Necessary Product Distributions

Learn about the pre-requisites to create a Java EE or standalone collocated agent.

To create a Java EE or standalone collocated agent, you must first install Oracle Fusion Middleware Infrastructure to create an Oracle home directory. See Installing and Configuring the Oracle Fusion Middleware Infrastructure.

The Oracle Data Integrator distribution contains the products and feature sets described in Understanding Oracle Data Integrator Distribution.

2 Installing Oracle Data Integrator

Learn how to install and configure Oracle Data Integrator, and how to verify your installation.

This chapter includes the sections:

- Starting the Installation Program
Learn how to launch the installer for Oracle Data Integrator.

- Navigating the Installation Screens to Install Oracle Data Integrator
Learn how to navigate and understand Oracle Data Integrator installation screens.

- Verifying the ODI Installation
Learn how to verify an Oracle Data Integrator installation.

- Installing Oracle Data Integrator in Silent Mode
You can install Oracle Data Integrator in silent mode by using the silent flag.

2.1 Starting the Installation Program

Learn how to launch the installer for Oracle Data Integrator.

To begin installing Oracle Data Integrator:

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.2.1) on the Oracle Fusion Middleware Supported System Configurations page.

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

4. Unzip the installer fmw_12.2.1.3.0_odi_Disk1_1of2.zip and fmw_12.2.1.3.0_odi_Disk1_2of2.zip files.

5. Launch the installation program by invoking java -jar from the JDK directory on your system, as illustrated below:

/home/Oracle/Java/jdk1.8.0_101/bin/java -jar fmw_12.2.1.3.0_odi.jar

Be sure to replace /home/Oracle/Java//Oracle/jdk1.8.0_101/bin/java with the location of the JDK on your system.

When the installation program appears, you are ready to install. See Navigating the Installation Screens to Install Oracle Data Integrator for a description of each installation program screen.

2.2 Navigating the Installation Screens to Install Oracle Data Integrator

Learn how to navigate and understand Oracle Data Integrator installation screens.

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

Welcome

This screen introduces you to the product installer.

Installation Location

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

- The Java EE and standalone colocated agent must be installed into an existing Oracle Home directory containing Oracle Fusion Middleware Infrastructure.

- The standalone agent must be installed into a new, empty Oracle Home directory.

For more information, see Selecting Directories for Installation and Configuration.

Installation Type

Use this screen to select an installation type.

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 documents referenced in Verifying Certification, System Requirements, and Interoperability.

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.

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 terminate the installer.

2.3 Verifying the ODI Installation

Learn how to verify an Oracle Data Integrator installation.

To verify an ODI installation, complete the following tasks:

- Reviewing Installation Log Files
The log files generated during your ODI installation help you determine whether any problems occurred during installation.

- Checking the Directory Structure
Check the directory structure of your ODI installation. This structure varies according to the options you selected during installation.

2.3.1 Reviewing Installation Log Files

The log files generated during your ODI installation help you determine whether any problems occurred during installation.

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 Troubleshooting Using Installation and Configuration Log Files.

2.3.2 Checking the Directory Structure

Check the directory structure of your ODI installation. This structure varies according to the options you selected during installation.

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

2.4 Installing Oracle Data Integrator in Silent Mode

You can install Oracle Data Integrator in silent mode by using the silent flag.

To install Oracle Data Integrator in silent mode, use the -silent flag on the command line when you start the installer.

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

Example Response Files

The following are response file examples when installing Oracle Data Integrator in Silent mode:

For an Enterprise installation:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#The oracle home location. This can be an existing Oracle Home or a new Oracle Home
ORACLE_HOME=/scratch/aganeriw/odi1213enterprise

#Set this variable value to the Installation Type selected. e.g. Standalone Installation, Enterprise Installation.
INSTALL_TYPE=Enterprise Installation

#Type String (URL format) Indicates the OCM Repeater URL which should be of the format [scheme[Http/Https]]://[repeater host]:[repeater port]
COLLECTOR_SUPPORTHUB_URL=

For a Standalone Installation:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#The oracle home location. This can be an existing Oracle Home or a new Oracle Home
ORACLE_HOME=/scratch/aganeriw/odi1213standalone

#Set this variable value to the Installation Type selected. e.g. Standalone Installation, Enterprise Installation.
INSTALL_TYPE=Standalone Installation

#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=

#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=<SECURE VALUE>

#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=true

#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false

#Provide the Proxy Host
PROXY_HOST=

#Provide the Proxy Port
PROXY_PORT=

#Provide the Proxy Username
PROXY_USER=

#Provide the Proxy Password
PROXY_PWD=<SECURE VALUE>

#Type String (URL format) Indicates the OCM Repeater URL which should be of the format [scheme[Http/Https]]://[repeater host]:[repeater port]
COLLECTOR_SUPPORTHUB_URL=

3 Creating the Master and Work Repository Schemas

Before you can configure an Oracle Data Integrator domain, you must create the Master and Work Repository (ODI_REPO) schemas on a certified database for use with this release of Oracle Fusion Middleware.

- Configuring a Certified Database
Learn how to configure a certified database.

- Starting the Repository Creation Utility
Learn how to start Repository Creation Utility.

- Navigating the Repository Creation Utility Screens to Create the Schema
Learn how to create a database schema for Oracle Data Integrator with Repository Creation Utility (RCU).

3.1 Configuring a Certified Database

Learn how to configure 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.

Understanding Database Requirements for an Oracle Fusion Middleware Installation in ASINS

3.2 Starting the Repository Creation Utility

Learn how to start Repository Creation Utility.

Navigate to the ORACLE_HOME/oracle_common/bin directory:

1. Start RCU.

On UNIX operating systems:

./rcu

On Microsoft Windows operating systems:

rcu.bat

3.3 Navigating the Repository Creation Utility Screens to Create the Schema

Learn how to create a database schema for Oracle Data Integrator with Repository Creation Utility (RCU).

Refer to Understanding Repository Creation Screens for more information about any of the screens mentioned in this topic.

To create a schema for Oracle Data Integrator:

1. Start RCU - Click Next.

2. Select a Repository Creation Method.

If you have permission to perform DBA activities on your database, select System Load and Product Load Concurrently.

If you do not have the permission 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.

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

Note:

If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For Oracle RAC databases, specify the service name of one of the nodes in this field. For example:

examplehost.exampledomain.com

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

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

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:

Note:

If you have already created the ODI repository using ODI Studio, uncheck the ODI entry here and create only the dependent schema. In the Configuration Wizard, after retrieving the dependent schema connectivity from STB schema, manually fill in the ODI repository details

.

Tip:

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

Select Oracle Data Integrator and click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

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

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

7. 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 Oracle Data Integrator Studio

Oracle Data Integrator Studio (ODI Studio) is the interface you use to manage and configure Oracle Data Integrator (ODI).

- About Oracle Data Integrator Studio
Oracle Data Integrator Studio (ODI Studio) is the developer’s interface that you use to configure and manage Oracle Data Integrator (ODI).

- Creating the Database Schemas
Before you can configure an Oracle Data Integrator domain, you must create the Master and Work Repository (ODI_REPO) schemas on a certified database for use with this release of Oracle Fusion Middleware.

- Setting the Same Time Zone for the Agent and Repository
Ensure that schedules are not affected by out-of-sync time zones by setting the same time zone for your agent and for the repository.

- Adding Libraries to ODI Studio
You can add third-party libraries to ODI Studio.

- Setting Java Home for ODI Studio
Set the JAVA_HOME environment variable to the location of the certified JDK before you start ODI Studio.

- Starting ODI Studio
Start ODI Studio with the odi command.

- Connecting to the Master Repository
Connect to the master repository before creating an agent.

- Creating an Agent in the Master Repository with ODI Studio
A physical agent corresponds to a single standalone agent or a Java EE agent and should have a unique name in the topology. You create an ODI agent in the master repository with ODI Studio.

- Starting the New Agent
Learn how to start a Java EE, standalone, or standalone collocated agent.

- Performing Next Steps
Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

4.1 About Oracle Data Integrator Studio

Oracle Data Integrator Studio (ODI Studio) is the developer’s interface that you use to configure and manage Oracle Data Integrator (ODI).

ODI Studio is installed as part of standalone or enterprise option under the specified ORACLE_HOME directory. ODI Studio provides four graphical Navigators for managing ODI artifacts: Designer, Operator, Topology, and Security. ODI Studio can also directly execute jobs on demand, and can be used for development and initial testing.

4.2 Creating the Database Schemas

Before you can configure an Oracle Data Integrator domain, you must create the Master and Work Repository (ODI_REPO) schemas on a certified database for use with this release of Oracle Fusion Middleware.

Follow the instructions in Creating the Master and Work Repository Schemas to create the required schemas.

4.3 Setting the Same Time Zone for the Agent and Repository

Ensure that schedules are not affected by out-of-sync time zones by setting the same time zone for your agent and for the repository.

Each database has its own way of identifying the configured time zone. To ensure that scheduling is not affected by out-of-sync time zones, make sure Oracle Data Integrator Studio and the agent are started with the time zones identical to the time zone of the repository.

4.4 Adding Libraries to ODI Studio

You can add third-party libraries to ODI Studio.

All files required by ODI Studio, such as third-party JDBC drivers, Open Tools, and libraries, should be deployed into the userlib directory. The location of this directory is:

- On UNIX systems: $HOME/.odi/oracledi/userlib

- On Windows systems: %APPDATA%\odi\oracledi\userlib
where %APPDATA% is C:\Documents and Settings\Application Data (in Windows XP), andC:\Users\myUserName\AppData\Roaming (on Windows 7 and Windows 8).

The userlib directory contains the additional_path.txt file, where you can declare additional files or folders outside of the userlib directory from which ODI Studio acquires other libraries and drivers, as illustrated in the following example:

; Additional paths file
; You can add here paths to additional libraries
; Examples:
;       C:\ java\libs\myjar.jar
;       C:\ java\libs\myzip.zip
;       C:\java\libs\*.jar will add all jars contained in the C:\java\libs\ directory
;       C:\java\libs\**\*.jar will add all jars contained in the C:\java\libs\ directory and subdirectories

D:\java\libs\*.jar
D:\ODI\JDBC_drivers\sqljdbc_1.2\enu\sqljdbc.jar

You must restart ODI Studio after editing the additional_path.txt file for the changes to take effect.

4.5 Setting Java Home for ODI Studio

Set the JAVA_HOME environment variable to the location of the certified JDK before you start ODI Studio.

To set JAVA_HOME for ODI Studio:

1. Go to the ORACLE_HOME/odi/studio/bin directory.

2. Open the odi.conf file in an editor.

3. Add a line at the bottom of the file specifying the location of a certified JDK. . For 12c (12.2.1.3), the certified JDK is 1.8.0_101 and later. For example:

- (UNIX) setenv JAVA_HOME/home/Oracle/Java/jdk1.8.0_101

- (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_101

4. Save the file.

4.6 Starting ODI Studio

Start ODI Studio with the odi command.

To start ODI Studio:

1. Go to the ORACLE_HOME/odi/studio directory.

2. Enter the following command:

- (UNIX) ./odi.sh

- (Windows) odi.exe

Note:
On Windows operating systems only the user who installed ODI can start ODI Studio. No other user has privileges to start ODI Studio.

4.7 Connecting to the Master Repository

Connect to the master repository before creating an agent.

Before you create an agent, you must connect to the master repository.

Note:

If you have installed any previous version of Oracle Data Integrator (ODI) 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 Oracle Data Integrator Studio (ODI Studio). The procedure assumes that no previous versions of ODI exist on your computer.

For more information, refer to the topics in the ODI Studio Help menu.

To connect to the master repository:

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

2. 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 capital letters).

- Password: Specify the supervisor password of RCU Custom Variable screen.

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

3. Specify and confirm a new wallet password on the New Wallet Password screen.

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

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

b. Specify SUPERVISOR as the user name.

c. Provide the password for the Supervisor user.

When you are logged in, follow the instructions in Creating an Agent in the Master Repository with ODI Studio to create the agent.

4.8 Creating an Agent in the Master Repository with ODI Studio

A physical agent corresponds to a single standalone agent or a Java EE agent and should have a unique name in the topology. You create an ODI agent in the master repository with ODI Studio.

As part of its startup sequence, an agent connects to the master repository to verify that there is a physical agent defined in the master repositpry 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 them. If it does not find a physical agent entry for an agent, then the startup fails.

Before you can create an ODI agent, you must first start ODI Studio and connected to the master repository in ODI Studio. See:

- Starting ODI Studio

- Connecting to the Master Repository

To create a physical agent in the master repository with ODI Studio:

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

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

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, provide the host name and port of the Oracle HTTP Server host instead. The name should be OracleDIAgent, not OracleDIAgent1.

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

4.9 Starting the New Agent

Learn how to start a Java EE, standalone, or standalone collocated agent.

For details, consult one of the following topics:

To start a new Java EE agent, see Starting a Java EE Agent.

To start a new standalone agent, see Starting a Standalone or Standalone Collocated Agent Using Node Manager.

To start a new standalone collocated agent, see Starting a Standalone Collocated Agent with Node Manager.

4.10 Performing Next Steps

Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

Performing Basic Administrative Tasks 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.

Performing Additional Domain Configuration Tasks contains additional domain configuration tasks that take advantage of additional Oracle Fusion Middleware products and features.

Preparing Oracle Data Integrator for Development contains common tasks to help prepare your Oracle Data Integrator environment for development.

Preparing Your Environment For High Availability contains important tasks to help prepare your environment to move to a highly available environment.

5 Configuring the Domain for a Java EE Agent

Create and configure a WebLogic domain for a Java EE agent in the standard installation topology.

- Creating the Database Schema
Ensure that you have created the required schema in your database for your Java EE agent.

- Generating a Template for a Java EE Agent
Use the Server Template Generation wizard to generate the non-default template for deploying a Java EE agent defined in the ODI master repository.

- Creating a Java EE Agent with Oracle Data Integrator Studio
Create a Java EE agent in the Master Repository using Oracle Data Integrator Studio (ODI Studio).

- Configuring the Domain for a Java EE Agent
Create and configure a WebLogic domain for a Java EE agent in the standard installation topology.

- Adding Libraries to a Java EE Agent
After configuring a Java EE agent, you can specify additional libraries if required.

- Starting a Java EE Agent
Start Node Manager, then the WebLogic Administration Server and WebLogic Managed Servers for the Java EE agent.

- Performing Next Steps
Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

5.1 Creating the Database Schema

Ensure that you have created the required schema in your database for your Java EE agent.

Before you can configure the topology for your Java EE agent, make sure you have created the necessary schema in your database. See Creating the Master and Work Repository Schemas for instructions.

5.2 Generating a Template for a Java EE Agent

Use the Server Template Generation wizard to generate the non-default template for deploying a Java EE agent defined in the ODI master repository.

Use this procedure if you require changes to the default template that deploys a Java EE agent with default name and settings. To create a Java EE agent with the Server Template Generation wizard:

1. From the Physical Agent Editor menu, select Generate Server Template to start the Template Generation wizard.

2. In the Agent Information step, review the agent information and modify the default configuration as appropriate. This information includes the following parameters: the Agent Name, the Datasource JNDI Name, the Connection Retry Count, the Retry Delay, and the Supervisor Key.

- The Connection Retry Count specifies the number of retry attempts if the agent loses the connection to the repository. Note that setting this parameter to a non-zero value enables a high availability connection retry feature if the ODI repository resides on an Oracle RAC database. If this feature is enabled, the agent can continue to execute sessions without interruptions even if one or more Oracle RAC nodes become unavailable.

- The Retry Delay specifies the number of milliseconds between connection retry attempts.

- The Supervisor Key specifies the name of the key in the application server credential store that contains the login and the password of an ODI user with Supervisor privileges. The agent uses these credentials to connect to the repository.

3. Click Next.

4. To add domain and shared libraries for the agent, navigate to the Libraries and Drivers page, and then check the libraries you want to deploy with your agent. Libraries can be any JAR or ZIP files required by the agent. Select any additional JDBC drivers or libraries for accessing the source and target data servers in this page. Note that library name validation is limited within the newly added libraries, not against already deployed shared libraries.

- Domain libraries are the libraries deployed in a domain that are available to all applications running in the domain. This approach to adding libraries is typically used when adding infrequently changed JAR files. Note that when using this approach, you must reboot all servers in the domain for the change to take effect.

- Shared libraries are libraries you specify in the agent deployment descriptor before deploying the agent to the domain. In this way, multiple applications can use the libraries resources and duplication is avoided. This approach to adding libraries is used for libraries that may need modifications or upgrade. Shared libraries allow you to change libraries without restarting the server, but you may need to restart the application.

5. Click Next.

6. In Template Target and Summary step, enter the Target Template Path that specifies the location where the server template is generated.

7. Click Finish to close the wizard and generate the server template with your specifications.

The generated template can be used to deploy the agent in an Oracle WebLogic Server domain.

5.3 Creating a Java EE Agent with Oracle Data Integrator Studio

Create a Java EE agent in the Master Repository using Oracle Data Integrator Studio (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. The default agent name configured with the installer is OracleDIAgent and the port to be configured for this agent is the managed server port.

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.

To create an agent using ODI Studio, see Creating an Agent in the Master Repository with ODI Studio.

5.4 Configuring the Domain for a Java EE Agent

Create and configure a WebLogic domain for a Java EE agent in the standard installation topology.

- Starting the Configuration Wizard
This task explains how to start the WebLogic Server Configuration Wizard.

- Navigating the Configuration Wizard Screens to Configure the Domain
This task explains how to create and configure a domain.

5.4.1 Starting the Configuration Wizard

This task explains how to start the WebLogic Server 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

5.4.2 Navigating the Configuration Wizard Screens to Configure the Domain

This task explains how to create and configure a 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.

To create and configure a domain:

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

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

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

- Oracle Enterprise Manager

- Oracle JRF

- WebLogic Coherence Cluster Extension

- Oracle Data Integrator - Agent
Selecting this template automatically selects the following as dependencies:

- Oracle Data Integrator - Agent Libraries

- Oracle Data Integrator SDK Shared Library Template

In addition, select the following templates:

- Oracle Data Integrator - JFR

- Oracle Data Integrator - REST Services

- Oracle Data Integrator - Console

Note:

For information about configuring and managing a secondary topology using the Oracle Data Integrator Console see About the Secondary Topologies for Oracle Data Integrator.

Tip:

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

3. 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 set your Application home in accordance with the directory structure summarized in Understanding the Recommended Directory Structure, to 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.

More information about the options on this screen can be found in Application Location.

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

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

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

More information about the other options on this screen can be found in Datasource Defaults

7. Verify that the values on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately. For information about each of the schemas, see Understanding Repository Creation Utility Schemas, IDs, and Tablespaces in Creating Schemas with the Repository Creation Utility.

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.

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

9. Use the Credentials screen to create the following two keys:

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

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

ii. The password must be the same password specified on the Custom Variables screen in RCU during schema creation (see step 6 in procedure in Navigating the Repository Creation Utility Screens to Create the Schema).

b. Create a second credential as follows:

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

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

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

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

Note:
If the repository is configured in external authentication mode, then the SUPERVISOR user name and password should be entered according to your external authentication settings.

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

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

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

More information about the types of Node Manager can be found in Node Manager Overview.

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

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

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

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.

14. Use the Clusters screen to create a new cluster:

a. Click the Add button.

b. Specify ODI_cluster1 in the Cluster Name field.

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

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.

Tip:

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

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

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

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

16. 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 8-2 for more information and next steps for configuring Coherence.

Note:

For Coherence licensing information, see Oracle Coherence Products in Licensing Information.

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

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

b. Specify ODI_machine1 in the Name field.

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

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

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

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

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

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

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

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

5.5 Adding Libraries to a Java EE Agent

After configuring a Java EE agent, you can specify additional libraries if required.

To add libraries to a Java EE agent:

1. Set the environment variable ODI_ADDITIONAL_CLASSPATH to locate additional jars before starting the agent. For example:
ODI_ADDITIONAL_CLASSPATH=/share/libs/mytool.jar:/share/libs/drivers/mydriver.jar

2. Do one the following:

- Copy the additional libraries to the DOMAIN_HOME/lib directory. The Java EE will automatically add these libaries to the agent’s classpath.

- Follow the steps below to use the generate_agent_wls_template.sh script or ODI Studio to generate an agent template and then create/extend a WebLogic domain with that template.

To generate a template for a Java EE agent using the generate_agent_wls_template.sh script, specify domain and shared libraries with the -domainLibraries and -sharedLibraries arguments as illustrated in the following example:

./generate_agent_wls_template.sh
-agentName sample
-agentContextName context
-odiUser SUPERVISOR
-destinationJar /home/userName/NewFormaterJar.jar
-retryCount 10
-retryDelayMS 1
-createDatasourceForMasterRepository false
-masterDataSource jdbc/odiMasterRepository,oracle.jdbc.OracleDriver,jdbc:oracle:thin:@mycompany.com-isESSDependency false
-addToPath /home/userName
-domainLibraries /home/userName/odi/myDomain/userlib/myLib.jar
-sharedLibraries MessageBox

To generate a template for a Java EE agent and specify additional libraries for the agent using ODI Studio:

1. Start ODI Studio.

2. Select Generate Server Template, to start the Template Generation wizard.

3. In the Agent Information page, enter the agent information, such as the Java EE agent name, the datasource JNDI name, the connection retry count, and the Supervisor key.

4. In the Libraries and Drivers page, select the libraries you want to deploy with your Java EE agent from the list of external libraries. Note that library name validation is limited within the newly added libraries, not against already deployed shared libraries. You can select a domain library or a shared library. Domain libraries are the libraries deployed in the WebLogic domain and are available to a Java EE agent, since they are available to all applications running in the domain. Domain libraries are typically used when adding infrequently changed JAR files. Note that when using this approach, you must reboot all servers in the domain for the change to take effect. Shared libraries are libraries you specify in the agent deployment descriptor, before deploying the agent to the domain. With shared libraries, multiple applications can use the libraries resources and duplication is avoided. Shared libraries are used for libraries that may need modifications or upgrade. These libraries allow you to change libraries without restarting the server, but you may need to restart the application

5. Click Next to display the Datasources page.

6. In that page, select the datasource definitions that you want to include in the agent template. You can only select datasources using this wizard. To add datasources use the Data Sources tab.

7. Click Next to display the Template Target and Summary page.

8. In that page, specify where the template should be generated in the Target Template Path box.

9. Click Finish to close the wizard and generate the agent template.

5.6 Starting a Java EE Agent

Start Node Manager, then the WebLogic Administration Server and WebLogic Managed Servers for the Java EE agent.

Note:

If you have not yet configured the physical agent in the master repository, go to Creating an Agent in the Master Repository with ODI Studio.

- Starting Node Manager
Learn how to start Oracle Node Manager in your domain.

- Starting the Administration Server
Learn how to start the WebLogic Administration Server.

- Starting the ODI Managed Server
Learn how to start the ODI Managed Server.

5.6.1 Starting Node Manager

Learn how to start Oracle Node Manager in your domain.

To start Node Manager in a domain, first go to the domain DOMAIN_HOME/bin directory. Then start Node Manager as follows:

On UNIX operating systems, use nohup and nm.out as output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

On Windows operating systems, Oracle recommends configuring 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".

For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

5.6.2 Starting the Administration Server

Learn how to start the WebLogic 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

Note:

When you run ./startWebLogic.sh in the foreground, control does not return to the terminal. If you terminate the terminal, the Admin Server is also terminated. Therefore, Oracle recommends running the start script in the background to avoid killing the servers even if the terminal is closed.

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

Tip:

For more information about starting the Administration Server, see Starting and Stopping Administration Servers.

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.

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.

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.

5.6.3 Starting the ODI Managed Server

Learn how to start the ODI Managed Server.

To start a WebLogic 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. The default Administration Server port number is 7001.

The login credentials were provided on the Administrator Account screen.

2. Bring up the Target Navigation, and expand domains until the ODI_server1 server (a WebLogic Managed Server) is visible.

3. Select ODI_server1 server, to display the server’s page.

4. In that page, select Start Up to start the ODI_server1 server.

5. In the Target Navigation page, select the odi_domain to verify that the server you started is up and running.

Tip:

For information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware Control, see Administering Oracle Fusion Middleware with Fusion Middleware Control.

5.7 Performing Next Steps

Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

Performing Basic Administrative Tasks 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.

Performing Additional Domain Configuration Tasks contains additional domain configuration tasks that take advantage of additional Oracle Fusion Middleware products and features.

Preparing Oracle Data Integrator for Development contains common tasks to help prepare your Oracle Data Integrator environment for development.

Preparing Your Environment For High Availability contains important tasks to help prepare your environment to move to a highly available environment.

6 Configuring the Domain for a Standalone Agent

Create and configure a standalone domain for a standalone agent in the standard installation topology.

- Creating the Database Schema
Ensure that you have created the required schema in your database for your standalone agent.

- Creating a Standalone Agent in the Master Repository with ODI Studio
This topic explains how to create a standalone or Java EE agent for a topology.

- Configuring the Standalone Domain for the Standalone Agent
Learn how to create a domain for your standalone agent.

- Adding Libraries to a Standalone or Standalone Collocated Agent
After configuring a standalone or standalone collocated agent, you can specify additional libraries if required.

- Starting a Standalone or Standalone Collocated Agent Using Node Manager
Start Node Manager, then start the standalone or standalone collocated agent.

- Starting a Standalone or Standalone Collocated Agent Without Node Manager
Start a standalone or standalone collocated agent without Node Manager, use the agent command.

- Performing Next Steps
Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

6.1 Creating the Database Schema

Ensure that you have created the required schema in your database for your standalone agent.

Before you can configure the topology for your standalone agent, make sure you have created the necessary schema in your database. See Creating the Master and Work Repository Schemas for instructions.

6.2 Creating a Standalone Agent in the Master Repository with ODI Studio

This topic explains how to create a standalone or Java EE agent for a topology.

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.

To create an agent using ODI Studio, see Creating an Agent in the Master Repository with ODI Studio.

6.3 Configuring the Standalone Domain for the Standalone Agent

Learn how to create a domain for your standalone agent.

For more information on other methods available for domain creation, see Additional Tools for Creating, Extending, and Managing WebLogic Domains.

This topic includes the following t:asks:

- Starting the WebLogic Server Configuration Wizard
The WebLogic Server Configuration Wizard is the tool you use to configure your domain.

- Navigating the Configuration Wizard Screen to Create the Domain
Learn how to use the WebLogic Server Configuration Wizard to create a domain.

6.3.1 Starting the WebLogic Server Configuration Wizard

The WebLogic Server Configuration Wizard is the tool you use to configure your domain.

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.3.2 Navigating the Configuration Wizard Screen to Create the Domain

Learn how to use the WebLogic Server Configuration Wizard to create a domain.

To create and configure the domain for the topology:

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

More information about the other options on this screen can be found in Configuration Type.

2. On the Templates screen, select the following template:
Oracle Data Integrator - Standalone Agent

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

4. 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 Creating the Database Schema).

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.

More information about the other options on this screen can be found in Datasource Defaults.

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

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

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

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

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

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

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

More information about the types of Node Manager can be found in Node Manager Overview.

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

Click Finish to terminate the Configuration Wizard.

6.4 Adding Libraries to a Standalone or Standalone Collocated Agent

After configuring a standalone or standalone collocated agent, you can specify additional libraries if required.

To add libraries to a ODI standalone or standalone collocated agent:

1. Set the environment variable ODI_ADDITIONAL_CLASSPATH to locate additional jars before starting the agent. For example:
ODI_ADDITIONAL_CLASSPATH=/share/libs/mytool.jar:/share/libs/drivers/mydriver.jar

2. Do one the following:

- Copy the additional libraries to the DOMAIN_HOME/lib directory. The ODI standalone and standalone collocated agents will automatically add these libaries to the agent’s classpath.

- Edit the DOMAIN_HOME/config/fmwconfig/components/ODI/Agent Name/bin/instance.sh/cmd command to add the libraries to the ODI_POST_CLASSPATH variable.

6.5 Starting a Standalone or Standalone Collocated Agent Using Node Manager

Start Node Manager, then start the standalone or standalone collocated agent.

Note:

If you have not yet configured the physical agent in the master repository, go to Creating an Agent in the Master Repository with ODI Studio.

- Starting Node Manager
Learn how to start the Node Manager for your domain.

- Starting a Standalone or Standalone Collocated Agent

6.5.1 Starting Node Manager

Learn how to start the Node Manager for your domain.

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

On UNIX operating systems, start the Node Manager 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, Oracle recommends configuring 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 .

For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

6.5.2 Starting a Standalone or Standalone Collocated Agent

To start an ODI standalone agent when using Node Manager:

1. Go to the DOMAIN_HOME/bin directory.

2. Start the agent:

- (UNIX) ./startComponent.sh OracleDIAgent1

- (Windows) startComponent.cmd OracleDIAgent1

3. At the prompt, enter the Administrator password for the domain.

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

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

6.6 Starting a Standalone or Standalone Collocated Agent Without Node Manager

Start a standalone or standalone collocated agent without Node Manager, use the agent command.

To start a standalone agent without Node Manager:

1. Go to the DOMAIN_HOME/bin directory.

2. Start the agent:

- (UNIX) ./agent.sh -NAME=OracleDIAgent1

- (Windows) agent.cmd -NAME=OracleDIAgent1

where -NAME must be entered in all capital letters, and the name of the agent (in this example, OracleDIAgent1) is case-sensitive.

6.7 Performing Next Steps

Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

Performing Basic Administrative Tasks 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.

Performing Additional Domain Configuration Tasks contains additional domain configuration tasks that take advantage of additional Oracle Fusion Middleware products and features.

Preparing Oracle Data Integrator for Development contains common tasks to help prepare your Oracle Data Integrator environment for development.

Preparing Your Environment For High Availability contains important tasks to help prepare your environment to move to a highly available environment.

7 Configuring the Domain for a Standalone Collocated Agent

Create and configure a WebLogic domain for a standalone collocated agent in the standard installation topology.

- Creating the Database Schema
Ensure that you have created the required schema in your database for your standalone collocated agent.

- Creating a Standalone Agent in the Master Repository Using Oracle Data Integrator Studio
Learn how to create a standalone agent for a topology with Oracle Data Integrator Studio (ODI Studio).

- Configuring Your WebLogic Domain for Your Standalone Collocated Agent
Learn how to create a WebLogic domain for your standalone collocated agent with the Configuration Wizard.

- Adding Libraries to a Standalone or Standalone Collocated Agent
After configuring a standalone or standalone collocated agent, you can specify additional libraries if required.

- Starting a Standalone Collocated Agent with Node Manager
Learn how to start a standalone collocated agent with Node Manager.

- Starting a Standalone Collocated Agent Without Node Manager
Learn how to start a standalone collocated agent without using Node Manager.

- Performing Next Steps
Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

7.1 Creating the Database Schema

Ensure that you have created the required schema in your database for your standalone collocated agent.

Before you can configure the topology for your standalone collocated agent, make sure you have created the necessary schema in your database. See Creating the Master and Work Repository Schemas for instructions.

7.2 Creating a Standalone Agent in the Master Repository Using Oracle Data Integrator Studio

Learn how to create a standalone agent for a topology with Oracle Data Integrator Studio (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.

To create a standalone agent using ODI Studio, see Creating an Agent in the Master Repository with ODI Studio.

7.3 Configuring Your WebLogic Domain for Your Standalone Collocated Agent

Learn how to create a WebLogic domain for your standalone collocated agent with the Configuration Wizard.

For more information on other methods available for domain creation, see Additional Tools for Creating, Extending, and Managing WebLogic Domains.

This topic contains the following tasks:

- Starting the Configuration Wizard
The WebLogic Server Configuration Wizard is the tool you use to configure your domain.

- Navigating the Configuration Wizard Screens to Configure the Domain
Learn how to use the WebLogic Server Configuration Wizard to create a domain.

7.3.1 Starting the Configuration Wizard

The WebLogic Server Configuration Wizard is the tool you use to configure your domain.

To start 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

7.3.2 Navigating the Configuration Wizard Screens to Configure the Domain

Learn how to use the WebLogic Server Configuration Wizard to create a domain.

To create and configure the domain for the topology:

1. 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 (Creating a Standalone Agent in the Master Repository Using Oracle Data Integrator Studio).

Tip:

More information about the other options on this screen can be found in ODI Server Configuration.

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

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

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

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

7.4 Adding Libraries to a Standalone or Standalone Collocated Agent

After configuring a standalone or standalone collocated agent, you can specify additional libraries if required.

To add libraries to a ODI standalone or standalone collocated agent:

1. Set the environment variable ODI_ADDITIONAL_CLASSPATH to locate additional jars before starting the agent. For example:
ODI_ADDITIONAL_CLASSPATH=/share/libs/mytool.jar:/share/libs/drivers/mydriver.jar

2. Do one the following:

- Copy the additional libraries to the DOMAIN_HOME/lib directory. The ODI standalone and standalone collocated agents will automatically add these libaries to the agent’s classpath.

- Edit the DOMAIN_HOME/config/fmwconfig/components/ODI/Agent Name/bin/instance.sh/cmd command to add the libraries to the ODI_POST_CLASSPATH variable.

7.5 Starting a Standalone Collocated Agent with Node Manager

Learn how to start a standalone collocated agent with Node Manager.

Note:

If you have not yet configured the physical agent in the master repository, go to Creating an Agent in the Master Repository with ODI Studio.

To start your standalone collocated agent with Node Manager:

- Starting Node Manager
Learn how to start Oracle Node Manager in your domain.

- Starting the Standalone Collocated Agent
Learn how to start the standalone collocated agent.

7.5.1 Starting Node Manager

Learn how to start Oracle Node Manager in your domain.

To start Node Manager in a domain, first go to the domain DOMAIN_HOME/bin directory. Then start Node Manager as follows:

On UNIX operating systems, use nohup and nm.out as output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems::

startNodeManager.cmd

Note:

On Windows operating systems, Oracle recommends configuring 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.

For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

7.5.2 Starting the Standalone Collocated Agent

Learn how to start the standalone collocated agent.

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

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

7.6 Starting a Standalone Collocated Agent Without Node Manager

Learn how to start a standalone collocated agent without using Node Manager.

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

On UNIX operating systems:

./agent.sh -NAME=OracleDIAgent1

On Windows operating systems:

agent.cmd -NAME=OracleDIAgent1

Enter the -NAME parameter in capital letters; the name of the agent (in this case, OracleDIAgent1) is case-sensitive.

7.7 Performing Next Steps

Learn about domain administration and configuration, and other tasks that prepare your Oracle Data Integrator environment for development.

Performing Basic Administrative Tasks 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.

Performing Additional Domain Configuration Tasks contains additional domain configuration tasks that take advantage of additional Oracle Fusion Middleware products and features.

Preparing Oracle Data Integrator for Development contains common tasks to help prepare your Oracle Data Integrator environment for development.

Preparing Your Environment For High Availability contains important tasks to help prepare your environment to move to a highly available environment.

8 Configuring an Oracle Data Integrator New Domain

Configure a new domain for Oracle Data Integrator.

This chapter includes the following sections:

- Performing Basic Administrative Tasks
Learn about the administration tasks typically performed on a new domain.

- Performing Additional Domain Configuration Tasks
Learn about additional tasks typically performed after configuring a new domain.

- Preparing Oracle Data Integrator for Development
Review tasks you can perform to prepare Oracle Data Integrator for development.

- Preparing Your Environment For High Availability
Learn how to set up a high availability environment.

8.1 Performing Basic Administrative Tasks

Learn about the administration tasks typically performed on a new domain.

Table 8-1 lists some common administration tasks typically performed on a new domain.

Table 8-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 .

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.

Configuring Secure Sockets Layer (SSL)

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

Configuring a Standalone or Standalone Collocated Agent to Use a Secure Transport.

Monitoring Oracle Fusion Middleware

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

Monitoring Oracle Fusion Middleware.

Understanding Backup and Recovery Procedures

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

Introducing Backup and Recovery.

8.2 Performing Additional Domain Configuration Tasks

Learn about additional tasks typically performed after configuring a new domain.

Table 8-2 lists additional tasks typically performed after configuring a new domain.

Table 8-2 Additional Domain Configuration Tasks

Task

Description

More Information

Deploying Applications

Learn how to deploy your applications to Oracle Fusion Middleware.

Deploying Applications.

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.

For additional information, see Installing Multiple Products in the Same Domain.

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.

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.

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

8.3 Preparing Oracle Data Integrator for Development

Review tasks you can perform to prepare Oracle Data Integrator for development.

Table 8-3 lists tasks that prepare Oracle Data Integrator for development.

Table 8-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.

Creating a Logical Agent

Managing the agents

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

Managing Agents

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.

Administering Repositories

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

Include libraries in classpath

Libraries that enable usage of ODI SDK APIs.

Client Libraries for SDK APIs

8.4 Preparing Your Environment For High Availability

Learn how to set up a high availability environment.

For information about configuring your environment for high availability, see Roadmap for Setting Up a High Availability Topology.

9 Uninstalling Oracle Data Integrator

Learn how to uninstall and reinstall Oracle Data Integrator (ODI).

Use the instructions in this chapter to remove the software. If you remove the software manually, you may experience problems when reinstalling ODI at a later time.

This chapter includes the following sections:

- Understanding Product Uninstallation
To uninstall Oracle Data Integrator (ODI), follow the roadmap in this topic.

- Stopping Agents and Oracle Fusion Middleware
Before running the deinstaller, stop running ODI agents and the Oracle Fusion Middleware environment.

- Removing Database Schemas
Use Repository Creation Utility (RCU) to remove your database schemas.

- Uninstalling the Software
Learn how to use the uninstaller to uninstall Oracle products.

- Removing the Oracle Home Directory Manually
Learn how to remove an Oracle home directory manually.

- Removing the Program Shortcuts on Windows Operating Systems
Learn how to remove program shortcuts on the Windows operating system.

- Removing Your Domain and Application Data
Learn how to remove a domain and application data.

- Removing Oracle Data Integrator Wallet Information
The ODI wallet holds encrypted data credentials that must be removed manually.

- Uninstalling Oracle Fusion Middleware Infrastructure
Learn how to uninstall Oracle Fusion Middleware Infrastructure after Oracle Data Integrator is removed.

- Reinstalling the Software
Learn how to reinstall Oracle software in an Oracle home.

9.1 Understanding Product Uninstallation

To uninstall Oracle Data Integrator (ODI), follow the roadmap in this topic.

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

Table 9-1 Roadmap to Uninstall Oracle Fusion Middleware

Task

Description

Documentation

Stop Oracle Fusion Middleware.

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

See Stopping Agents and Oracle Fusion Middleware.

Remove your database schemas.

Run Repository Creation Utility to remove your database schemas.

See Removing Database Schemas.

Remove the software.

Run the product uninstaller to remove Oracle Fusion Middleware Infrastructure.

See Uninstalling the Software.

Remove the Oracle home directory.

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

See Removing the Oracle Home Directory Manually.

Remove your domain and application data.

The uninstaller 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 Removing Your Domain and Application Data.

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 Uninstalling Oracle Fusion Middleware Infrastructure.

9.2 Stopping Agents and Oracle Fusion Middleware

Before running the deinstaller, stop running ODI agents and the Oracle Fusion Middleware environment.

- Stopping the Oracle Data Integrator Agents
Before running the deinstaller, stop all running agents.

- Stopping the Oracle Fusion Middleware Environment
Learn how to stop all processes and servers in your Oracle Fusion Middleware environment.

9.2.1 Stopping the Oracle Data Integrator Agents

Before running the deinstaller, stop all running agents.

To stop agents:

1. Go to the DOMAIN_HOME/bin directory.

2. Enter the following command:

- (UNIX) ./stopComponent.sh OracleDIAgent1

- (Windows) stopComponent.cmd OracleDIAgent1

9.2.2 Stopping the Oracle Fusion Middleware Environment

Learn how to stop all processes and servers in your Oracle Fusion Middleware environment.

Before running the uninstaller, 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.

9.3 Removing Database Schemas

Use Repository Creation Utility (RCU) to remove your database schemas.

Before removing your Oracle home, run RCU to remove the database schemas associated with the domain. Each domain has its own set of schemas, uniquely identified by a custom prefix (see Understanding Custom Prefixes). This set of schemas cannot be shared with any other domain (see Planning Your Schema Creation).

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.

9.4 Uninstalling the Software

Learn how to use the uninstaller to uninstall Oracle products.

To perform a silent (command-line) uninstallation, see Running the Oracle Universal Installer for Silent Deinstallation.

To uninstall and remove the software with the uninstaller, perform the following tasks:

- Starting the Uninstaller
Learn how to start the uninstaller on your system.

- Navigating the Uninstallation Screens
Understand the screens displayed by the uninstaller.

9.4.1 Starting the Uninstaller

Learn how to start the uninstaller on your system.

To start the uninstaller 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 uninstaller on a UNIX operating system, go to the ORACLE_HOME/oui/bin directory and enter the following command:

./deinstall.sh

9.4.2 Navigating the Uninstallation Screens

Understand the screens displayed by the uninstaller.

The uninstaller displays the series of screens in the order listed in Table 9-2. For additional help with a screen, click the screen name.

Table 9-2 Uninstaller Screens Descriptions

Screen

Description

Welcome

This screen introduces you to the product uninstaller.

Uninstallation Summary

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

Click Deinstall to begin removing the software.

Uninstallation Progress

This screen shows the progress of the uninstallation.

Uninstallation Complete

This screen appears when the uninstallation is complete. Review the information on this screen, then click Finish to terminate the uninstaller.

9.5 Removing the Oracle Home Directory Manually

Learn how to remove an Oracle home directory manually.

After the uninstaller is finished, manually remove your Oracle home directory and any existing sub-directories that were not removed by the uninstaller.

If your Oracle home directory was /home/oracle/product/Oracle_Home on a UNIX operating system:

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

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

9.6 Removing the Program Shortcuts on Windows Operating Systems

Learn how to remove program shortcuts on the Windows operating system.

On your Windows operating system, you must remove the program shortcuts manually. The uninstaller does not remove them.

Go to the C:\Program Data\Microsoft\Windows\Start Menu\Programs\Oracle\Oracle Home\Product directory. If you only have one product installed in your Oracle home, remove the Oracle Home directory. If you have multiple products installed in your Oracle home, remove all products before removing the Oracle Home.

9.7 Removing Your Domain and Application Data

Learn how to remove a domain and application data.

To remove your domain and application data:

1. Manually remove your domain home directory.

On a UNIX operating system, if your domain home directory was /home/oracle/config/domains/odi_domain :

> 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 to navigate to the C:\Oracle\Config\domains directory, then right-click the odi_domain folder and select Delete.

2. Manually remove your Application home directory.

On a UNIX operating system, if your Application home directory was /home/Oracle/config/applications/odi_domain :

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

9.8 Removing Oracle Data Integrator Wallet Information

The ODI wallet holds encrypted data credentials that must be removed manually.

The deinstaller does not remove the ODI wallet, and it must be manually removed. Wallet information is stored in a directory inside the user's home directory as follows:

- (UNIX) /home/exampleuser/.odi

- (Windows) C:\Users\exampleuser\AppData\Roaming\odi

9.9 Uninstalling Oracle Fusion Middleware Infrastructure

Learn how to uninstall Oracle Fusion Middleware Infrastructure after Oracle Data Integrator is removed.

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 uninstallation instructions, see Deinstalling Oracle Fusion Middleware Infrastructure.

9.10 Reinstalling the Software

Learn how to reinstall Oracle software in an Oracle home.

You can reinstall your software into the same Oracle home as a previous installation only if you have uninstalled 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 uninstallation process, so if you attempt to reinstall into the same Oracle home, the installer will not allow it. Your options are to:

1. Uninstall 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 Uninstalling Oracle Data Integrator. 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 Oracle Data Integrator Distribution

Learn about the products and feature sets available with the Oracle Data Integrator distribution.

This appendix includes the following section:

- Oracle Data Integrator Components
The Oracle Data Integrator (ODI) distribution incudes several products and feature sets.

A.1 Oracle Data Integrator Components

The Oracle Data Integrator (ODI) distribution incudes several products and feature sets.

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

Table A-1 Oracle Data Integrator Components and Features

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.

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.

ODI Console

Oracle Data Integrator Console is a web-based console available for different types of users.

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 from 11g in 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

Learn techniques for troubleshooting issues with Oracle Data Integrator (ODI).

- General Troubleshooting Tips
Troubleshoot most common issues with Oracle Data Integrator installation.

- Troubleshooting Using Installation and Configuration Log Files
Use the installation and configuration log files to troubleshoot Oracle Data Integrator issues.

- Verifying ODI Client and Repository Compatibility
Troubleshoot potential compatibility issues between Oracle Data Integrator (ODI) and Repository versions.

- Need More Help?
Access additional help through My Oracle Support.

B.1 General Troubleshooting Tips

Troubleshoot most common issues with Oracle Data Integrator installation.

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 the Oracle Technology Network (OTN) at:

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 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 Uninstalling Oracle Data Integrator.

3. Correct the issue that caused the error.

4. Restart the installation.

B.2 Troubleshooting Using Installation and Configuration Log Files

Use the installation and configuration log files to troubleshoot Oracle Data Integrator issues.

The installation and configuration log files 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

Troubleshoot potential compatibility issues between Oracle Data Integrator (ODI) and Repository versions.

If you are using Oracle Data Integrator with other Oracle Fusion Middleware products, make sure you have read Oracle Data Integration Interoperability with Other Fusion Middleware Products in 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 and Repository Compatible Versions

ODI Version

Repository Version

12c (12.2.1.2.0)

05.01.02.02

12c (12.2.1.1.0)

05.01.02.02

12c (12.1.2)

05.01.01.16

11g Release 1 (11.1.1.7.0)

04.03.04.02

11g Release 1 (11.1.1.6.0)

04.03.04.02

B.4 Need More Help?

Access additional help through My Oracle Support.

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.

C About the Secondary Topologies for Oracle Data Integrator

This appendix provides alternate topologies for Oracle Data Integrator.

The following topologies are covered in this appendix:

- Oracle Data Integrator Topology with the Oracle Data Integrator Console
Oracle Data Integrator (ODI) Console is a web-based console that administrators and developers can use to configure the ODI topology and browse development artifacts.

- Using the Oracle Data Integrator Console
The Oracle Data Integrator (ODI) Console is available for selection in the Configuration Wizard.

C.1 Oracle Data Integrator Topology with the Oracle Data Integrator Console

Oracle Data Integrator (ODI) Console is a web-based console that administrators and developers can use to configure the ODI topology and browse development artifacts.

ODI Console is a web-based console available to:

- Administrators use Oracle Data Integrator Console to create and import repositories and to configure the topology.

- Business users and developers to browse development artifacts in this interface, using, for example, the Data Lineage and Flow Map features.

This ODI Console integrates with Oracle Fusion MiddlewareControl Console and allows Fusion Middleware administrators to drill down into the details of Oracle Data Integrator components and sessions.

Figure C-1 illustrates an Oracle Data Integrator topology including the ODI Console.

Figure C-1 Secondary Installation Topology including the ODI Console

C.2 Using the Oracle Data Integrator Console

The Oracle Data Integrator (ODI) Console is available for selection in the Configuration Wizard.

To access the ODI Console, select Oracle Data Integrator - Console - 12.2.1.3.0[odi] in the Configuration Wizard Templates screen.

To use the ODI Console, follow the instructions in Using Oracle Data Integrator Console in Administering Oracle Data Integrator.

Oracle Legal Notices

Copyright Notice

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

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, then 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.

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability 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.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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 that have purchased support 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.