1 Introduction to Upgrading Oracle Data Integrator to 12c (12.2.1.3.0)
Before you begin, review all introductory information to understand the standard upgrade topologies and upgrade paths for Oracle Data Integrator 12c (12.2.1.3.0).
Following the pre-upgrade information and preparation steps, the procedures in this guide are divided into two sections:
-
Upgrades from 11g, described in Upgrading Oracle Data Integrator from 11g.
Note:
Versions of Interfaces created in Oracle Data Integrator 11g are not migrated when upgrading Oracle Data Integrator from 11g to 12c.
-
Upgrades from a previous 12c release, described in Upgrading Oracle Data Integrator from a Previous 12c Release.
Note:
For general information about Fusion Middleware upgrade planning and other upgrade concepts and resources, see the following sections in Planning an Upgrade of Oracle Fusion Middleware:The following topics describe the concepts related to upgrading Oracle Data Integrator:
- About the Valid Starting Points for the Oracle Data Integrator Upgrade
You can upgrade Oracle Data Integrator from 11g or from a previous 12c release. - About the Oracle Data Integrator Standard Topologies
The steps to upgrade Oracle Data Integrator to 12c (12.2.1.3.0) depend on the existing production topology (either 11g or a previous 12c release). - About the New Features for Oracle Data Integrator 12c
There are several changes between Oracle Data Integrator 11g and 12c.
Parent topic: Getting Started
About the Valid Starting Points for the Oracle Data Integrator Upgrade
You can upgrade Oracle Data Integrator from 11g or from a previous 12c release.
The following supported starting points are supported for an upgrade to Oracle Data Integrator 12c (12.2.1.3.0):
-
Oracle Data Integrator 11g Release 1 (11.1.1.7, 11.1.1.8, and 11.1.1.9)
-
Oracle Data Integrator 12c (12.1.2.0, 12.1.3.0, 12.2.1.0, 12.2.1.1, 12.2.1.2, and 12.2.1.2.6)
The upgrade procedures in this guide explain how to upgrade an existing Oracle Data Integrator 11g domain and existing 12c domain to Oracle Fusion Middleware 12c (12.2.1.3.0). If your domain contains other components that also need to be upgraded, links to supporting documentation are provided.
If your existing version of Oracle Data Integrator is earlier than 11g Release 1 (11.1.1.6.0), you must first upgrade your software to one of the following supported versions before you can upgrade to 12c (12.2.1.3.0):
-
To upgrade to 11g Release 1 (11.1.1.6.0), see the Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator in the 11g Release 1 (11.1.1.6.0) documentation library.
-
To upgrade to 11g Release 1 (11.1.1.7.0), see the Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator in the 11g Release 1 (11.1.1.7.0) documentation library.
Note:
If your current starting point is 11g Release 1 (11.1.1.6.0), Oracle recommends upgrading to 11.1.1.7 first, and then upgrading to 12c (12.2.1.3.0).
About the Oracle Data Integrator Standard Topologies
The steps to upgrade Oracle Data Integrator to 12c (12.2.1.3.0) depend on the existing production topology (either 11g or a previous 12c release).
As a result, it is difficult to provide exact upgrade instructions for every possible Oracle Data Integrator installation. Therefore, this guide provides instructions for upgrading several typical Oracle Data Integrator topologies. These typical topologies are referred to as standard upgrade topologies.
Note:
For additional information about the upgrade process and planning resources to ensure your upgrade is successful, see Planning an Upgrade to Oracle Fusion Middleware 12c (12.2.1.3.0) in Planning an Upgrade of Oracle Fusion Middleware.If you are upgrading from a previous 12c release, the standard topology remains unchanged. See Upgrading Oracle Data Integrator from a Previous 12c Release.
If you are upgrading from 11g, refer to the following sections to upgrade the following specific topologies:
Oracle Data Integrator Standard Upgrade Topology for Standalone Agents
When upgrading from 11g to 12c (12.2.1.3.0), the Oracle Data Integrator topology for standalone agents that are not configured in a WebLogic domain is updated as described here. If you are upgrading from a previous 12c release, the existing topology remains unchanged.
A standalone agent runs in a separate Java Virtual Machine (JVM) process. It connects to the work repository and to the source and target data servers using JDBC. Standalone agents can be installed on any server with a Java Virtual Machine installed. This type of agent is appropriate when you have to use a resource that is local to one of your data servers (for example, the file system or a loader utility installed with the database instance), and you do not want to install a Java EE application server on this machine.
In 11g, the following standalone agent configurations are possible:
-
Standalone agent as a standalone Oracle instance, not managed by OPMN. In this configuration, the Upgrade Assistant does not support the upgrade of standalone system component configurations to 12c (12.2.1.3.0).
-
Standalone agent managed by OPMN. In this configuration, the Upgrade Assistant supports the upgrade of standalone system component configurations to 12c (12.2.1.3.0).
Figure 1-1 shows the 11g Oracle Data Integrator standard installation topology for a standalone agent managed by OPMN and the resulting 12c topology as it appears after you complete the upgrade procedures in this guide.
The upgrade roadmap and procedures for this topology are provided in Upgrading an Oracle Data Integrator Standalone Agent Environment from 11g.
Figure 1-1 Oracle Data Integrator Standard Upgrade Topology for a Standalone Agent
Description of "Figure 1-1 Oracle Data Integrator Standard Upgrade Topology for a Standalone Agent"
All the elements in the above topology illustration are described in the following table.
Table 1-1 Description of the Elements in the Standalone Agent Standard Upgrade Topology for Standalone Agents
| Element | Description and Links to Additional Documentation |
|---|---|
|
11g Oracle Data Integrator Standalone Standard Installation Topology |
This is the label for the left side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 11g Oracle Data Integrator installer. It consists of a single standalone agent ( A relational database for the Master and Work Repository is also required, as shown in the figure. |
|
12c Oracle Data Integrator Standalone Agent Standard Installation Topology |
This is the label for the right side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 12c Oracle Data Integrator distribution. It consists of a single standalone agent ( |
|
APPHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the database. |
|
Standalone Agent |
The standalone Oracle Data Integrator agent that runs in a separate Java Virtual Machine (JVM) process. In 11g, the standalone agent is created directly as part of the installation. |
|
Standalone Domain |
See Standalone Domain in Administering Oracle HTTP Server. |
|
System Component |
In 12c, a standalone domain must be created before a standalone agent can be created. A system component corresponds to a standalone agent. |
Parent topic: About the Oracle Data Integrator Standard Topologies
Oracle Data Integrator Standard Upgrade Topology for Standalone Collocated Agents
When upgrading from 11g to 12c (12.2.1.3.0), the Oracle Data Integrator topology for standalone agents that are configured in a WebLogic domain is updated as described here. If you are upgrading from a previous 12c release, the existing topology remains unchanged.
A standalone collocated agent runs in a separate Java Virtual Machine (JVM) process but is part of a WebLogic Server domain and controlled by a WebLogic Administration Server. Standalone collocated agents can be installed on any server with a Java Virtual Machine installed, but require a connection to the WebLogic Administration Server. This type of agent is appropriate when you need to use a resource that is local to one of your data servers, but you want centralized management of all applications in an enterprise application server.
In 11g, the following standalone collocated agent configurations are possible:
-
Standalone collocated agent not managed by OPMN. In this configuration, the Upgrade Assistant does not support the upgrade of WebLogic domain component configurations to 12c (12.2.1.3.0).
-
Standalone collocated agent managed by OPMN. In this configuration, the Upgrade Assistant supports the upgrade of WebLogic domain component configurations to 12c (12.2.1.3.0).
Figure 1-2 shows the 11g Oracle Data Integrator standard installation topology for a standalone collocated agent managed by OPMN and the resulting 12c topology as it appears after you complete the upgrade procedures in this guide.
The upgrade roadmap and procedures for this topology are provided in Upgrading an Oracle Data Integrator Standalone Collocated Agent Environment from 11g.
Figure 1-2 Oracle Data Integrator Standard Upgrade Topology for a Standalone Collocated Agent
Description of "Figure 1-2 Oracle Data Integrator Standard Upgrade Topology for a Standalone Collocated Agent"
All the elements in the above topology illustration are described in the following table.
Table 1-2 Description of the Elements in the Standard Upgrade Topology for Standalone Collocated Agents
| Element | Description and Links to Additional Documentation |
|---|---|
|
11g Oracle Data Integrator Standalone Standard Installation Topology |
This is the label for the left side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 11g Oracle Data Integrator installer. It consists of a single standalone agent ( A relational database for the Master and Work Repository is also required, as shown in the Figure 1-2. |
|
12c Oracle Data Integrator Standalone Standard Installation Topology |
This is the label for the right side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 12c Oracle Data Integrator distribution. It consists of a single standalone agent ( |
|
APPHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the database. |
|
WebLogic Domain |
A logically related group of Java components (in this case, the Administration Server, Managed Servers, Standalone Agent, and other related software components). See What Is an Oracle WebLogic Server Domain? in Understanding Oracle Fusion Middleware. |
|
Administration Server |
The central control entity of a domain that maintains the domain's configuration objects and distributes configuration changes to Managed Servers. See What Is the Administration Server? in Understanding Oracle Fusion Middleware. |
|
Enterprise Manager |
Oracle Enterprise Manager Fusion Middleware Control. See Oracle Enterprise Manager Fusion Middleware Control in Understanding Oracle Fusion Middleware. |
|
Standalone Agent |
The standalone Oracle Data Integrator agent that runs in a separate Java Virtual Machine (JVM) process. In 11g, the standalone agent is created directly as part of the installation. |
|
System Component |
A system component corresponds to a standalone agent managed with the WebLogic Management Framework. |
Parent topic: About the Oracle Data Integrator Standard Topologies
Oracle Data Integrator Standard Upgrade Topology for Java EE Agents
When upgrading from 11g to 12c (12.2.1.3.0), the Oracle Data Integrator topology for Java EE agents is updated as described here. If you are upgrading from a previous 12c release, the existing topology remains unchanged.
A Java EE agent is deployed as a web application in a Java EE application server, such as Oracle WebLogic Server. The Java EE agent can benefit from all the features of the application server (for example, JDBC data sources or clustering for Oracle WebLogic Server). This type of agent is appropriate when there is a need for centralizing the deployment and management of all applications in an enterprise application server, or when you have requirements for high availability.
Figure 1-3 shows the 11g Oracle Data Integrator Java EE standard installation topology and the resulting 12c topology as it appears after you complete the upgrade procedures in this guide.
The upgrade roadmap and procedures for this topology are provided in Upgrading an Oracle Data Integrator Java EE Agent Environment from 11g.
Figure 1-3 Oracle Data Integrator Standard Upgrade Topology for a Java EE Agent
Description of "Figure 1-3 Oracle Data Integrator Standard Upgrade Topology for a Java EE Agent "
All the elements in the above topology illustration are described in the following table.
Table 1-3 Description of the Elements in the Standard Upgrade Topology for Java EE Agents
| Element | Description and Links to Additional Documentation |
|---|---|
|
11g Oracle Data Integrator Java EE Topology |
This is the label for the left side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 11g Oracle Data Integrator installer. It consists of a single domain that contains a cluster of two managed servers, a Java EE agent, and the Administration Server. The domain also requires a relational database for the Master and Work Repository schema, and either an LDAP-based or file store for Oracle Platform Security Services (OPSS). |
|
12c Oracle Data Integrator Java EE Standard Installation Topology |
This is the label for the right side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 12c Oracle Data Integrator distribution. Like the 11g topology, it also consists of a single domain that contains a cluster of two managed servers, a Java EE agent, the Administration Server, and a database for the Master and Work Repository schema. Unlike the 11g topology, only an LDAP based store can be used for OPSS; file-based stores are not allowed in 12c. |
|
APPHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the application tier. |
|
DBHOST |
Standard term used in Oracle documentation referring to the machine that is hosting the database. |
|
WebLogic Domain |
A logically related group of Java components (in this case, the Administration Server, Managed Servers, Java EE agent, and other related software components). See What Is an Oracle WebLogic Server Domain? in Understanding Oracle Fusion Middleware. |
|
Administration Server |
The central control entity of a domain that maintains the domain's configuration objects and distributes configuration changes to Managed Servers. See What Is the Administration Server? in Understanding Oracle Fusion Middleware. |
|
Enterprise Manager |
Oracle Enterprise Manager Fusion Middleware Control. 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. 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. See Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware. |
|
Java EE Agent |
A Java EE agent is a JEE application that is deployed and runs on a Managed Server configured in a WebLogic domain. For more information about these agents and how they fit into the overall Oracle Data Integrator topology, see Introduction to the Oracle Data Integrator Topology in Developing Integration Projects with Oracle Data Integrator. |
|
Oracle JRF |
Oracle JRF (Java Required Files) consists of components that are not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle business applications and application frameworks. JRF consists of several independently developed libraries and applications that are deployed into a common location. The components that are considered part of Java Required Files include Oracle Application Development Framework shared libraries and ODL logging handlers. |
|
Infrastructure |
Oracle Fusion Middleware 12c term (similar to Oracle JRF) that refers to the collection of services that include the following:
|
|
Database with Schemas |
Represents a supported database, where the Oracle Fusion Middleware schemas have been created using the Repository Creation Utility (RCU). |
Parent topic: About the Oracle Data Integrator Standard Topologies
About the New Features for Oracle Data Integrator 12c
There are several changes between Oracle Data Integrator 11g and 12c.
See New and Changed Features for 12c in Understanding Oracle Fusion Middleware.
If your environment includes Oracle WebLogic Server with Oracle ADF, see Key Differences Between Application Developer 11g and Infrastructure 12c in Upgrading to the Oracle Fusion Middleware Infrastructure.
The following key differences exist between Oracle Data Integrator 11g and 12c:
Standalone Agents are Managed by the WebLogic Management Framework
In 12c, system components, like the Oracle Data Integrator standalone agent, are managed by the WebLogic Management Framework.
See What Is the WebLogic Management Framework? in Understanding Oracle Fusion Middleware.
Parent topic: About the New Features for Oracle Data Integrator 12c
Standalone Agents are Installed in Their Own Directories
In 12c, standalone agents that are configured within a WebLogic Server domain are installed in a separate directory and not within the product installation directory.
See About the Oracle Data Integrator Standalone Agent Standard Installation Topology in Installing and Configuring Oracle Data Integrator.
Parent topic: About the New Features for Oracle Data Integrator 12c
Repository Upgrade Validates Name Uniqueness for Objects
During the repository upgrade to 12c, the upgrade process checks for duplicated names (according to the namespace rules) for a number of objects. The check is done before the actual upgrade starts and if duplicates are detected, then you must print a report with the list of duplicates in the upgrade log and stop the upgrade. You should then connect to the 11g repository using ODI Studio to manually fix the duplicates (either by rename or delete), and then restart the upgrade.
In 12c, the following objects must have unique names:
-
Folder
-
Interface
-
Procedure/ KM
Note:
The Knowledge Modules must have unique names within the parent scope. This applies to either their own project or for global Knowledge Modules.
-
Package
-
Profile
-
User Functions
Parent topic: About the New Features for Oracle Data Integrator 12c