1 Introduction to Upgrading Oracle Identity Manager to 12c (12.2.1.4.0)
Before you begin, review all introductory information to understand the standard upgrade topologies and upgrade paths for Oracle Identity Manager 12c (12.2.1.4.0).
Note:
- The product Oracle Identity Manager is referred to as Oracle Identity Manager (OIM) and Oracle Identity Governance (OIG) interchangeably in the guide.
- Oracle recommends that you perform the upgrade as documented in this guide. If you require design/architectural changes (for example: changing the directory structure), complete them as separate steps during the post-upgrade validations.
- 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 Identity Manager:
- About the Starting Points for a Oracle Identity Manager Upgrade
The starting points for an upgrade to Oracle Identity Manager 12c (12.2.1.4.0) is Oracle Identity Manager 11g (11.1.2.3), 11g (11.1.2.2), or 12c (12.2.1.3) release. - About the Oracle Identity Manager Upgrade Scenarios
The steps to upgrade Oracle Identity Manager to 12c (12.2.1.4.0) depend on the existing production topology. - About the New Features for Oracle Identity Manager 12c (12.2.1.4.0)
Several changes have been made to Oracle Identity Manager between 12c (12.2.1.3.0) and 12c (12.2.1.4.0). - About Upgrade Restrictions
If you are using two or more Oracle Fusion Middleware products of the same or different versions in a single, supported, Oracle Fusion Middleware configuration, you must consider the interoperability and compatibility factors before planning the upgrade. - Terminology Used in this Guide
For consistency, the following terminology is used in this guide. - How to Use This Guide
This guide covers various upgrade scenarios.
About the Starting Points for a Oracle Identity Manager Upgrade
The starting points for an upgrade to Oracle Identity Manager 12c (12.2.1.4.0) is Oracle Identity Manager 11g (11.1.2.3), 11g (11.1.2.2), or 12c (12.2.1.3) release.
Upgrading From 11g (11.1.2.3)
You can upgrade from 11g (11.1.2.3) directly to 12c (12.2.1.4.0) by using the one-hop upgrade process. If you are not using the 11g (11.1.2.3) version of Oracle Identity Manager, you must first upgrade to 11g (11.1.2.3) using the in-place upgrade process, and then use the one-hop process to upgrade to 12c (12.2.1.4.0). See One-Hop Upgrade of Oracle Identity Manager.
Upgrade From 11.1.2.2 or Previous Releases
There are two options:
If you have configured Oracle Identity and Access Management by using the Oracle Universal Installer and Fusion Middleware Configuration Wizard, you must use the manual upgrade procedure to upgrade your existing Oracle Identity and Access Management environment to 11g Release 2 (11.1.2.3.0). For more information about manual upgrade, see Understanding the Oracle Identity and Access Management Manual Upgrade.
Oracle Identity Manager 11.1.2.3 and 11.1.2.2 support cloning. See OIG Migration Strategy to 12cPS3 (Doc ID 2621548.1) and Oracle Identity Manager 11gR2 PS3 (11.1.2.3) Upgrade Advisor (Doc ID 2002373.2).
Oracle recommends you to use the clone and upgrade approach if the starting points are 11.1.2.3 or 11.1.2.2. In case of 11.1.2.3.0 as starting point, you can opt for one-hop upgrade after cloning. See One-Hop Upgrade of Oracle Identity Manager.
You can perform an out-of-place upgrade. See Out-of-Place Upgrade of Oracle Identity Manager.
Upgrading From 12c (12.2.1.3)
- In-place upgrade: See In-Place Upgrade of Oracle Identity Manager.
- Out-of-place cloned upgrade: See Out-of-Place Cloned Upgrade of Oracle Identity Manager.
If the starting point is not 12c (12.2.1.3.0) version of Oracle Identity Manager, see Upgrading From 11g (11.1.2.3) and Upgrade From 11.1.2.2 or Previous Releases.
For information about upgrading Oracle Identity Manager to 12c (12.2.1.3.0), see Introduction to Upgrading Oracle Identity Manager to 12c (12.2.1.3.0) in the Upgrading Oracle Identity Manager for 12c (12.2.1.3.0).
Note:
The upgrade of an SSL enabled installation of Oracle Identity Manager 12c (12.2.1.3.0) to Oracle Identity Manager 12c (12.2.1.4.0) is not supported in this release.The upgrade procedures in this guide explain how to upgrade an existing Oracle Identity Manager to Oracle Identity Manager 12c (12.2.1.4.0). If your domain contains other components, you will have to upgrade those components as well.
About the Oracle Identity Manager Upgrade Scenarios
The steps to upgrade Oracle Identity Manager to 12c (12.2.1.4.0) depend on the existing production topology.
Oracle Identity Manager can be deployed in a number of different ways. This upgrade documentation provides instructions for the common deployment topologies. However, it can be used as a guide for the less common deployment topologies as well.
Note:
For additional information about the upgrade process and planning resources to ensure your upgrade is successful, see Preparing to Upgrade in Planning an Upgrade of Oracle Fusion Middleware.You can upgrade the following topologies or deployments using the procedure described in this guide:
About the New Features for Oracle Identity Manager 12c (12.2.1.4.0)
Several changes have been made to Oracle Identity Manager between 12c (12.2.1.3.0) and 12c (12.2.1.4.0).
To understand what's new in general in 12c (12.2.1.4.0), see New and Changed Features 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 (12.2.1.4.0).
For more information about Oracle Identity Governance 12c (12.2.1.4.0), refer to the following topics in the Administering Oracle Identity Governance:
About Upgrade Restrictions
If you are using two or more Oracle Fusion Middleware products of the same or different versions in a single, supported, Oracle Fusion Middleware configuration, you must consider the interoperability and compatibility factors before planning the upgrade.
Interoperability
In the context of Oracle Fusion Middleware products, Interoperability is defined as the ability of two Oracle Fusion Middleware products or components of the same version (or release) to work together (interoperate) in a supported Oracle Fusion Middleware configuration. Specifically, interoperability applies when the first 4 digits of the release or version number are the same. For example, Oracle Fusion Middleware 12c (12.2.1.4.0) components are generally interoperable with other 12c (12.2.1.4.0) components. See Interoperability with Oracle Identity Management Products.
Compatibility
In the context of Oracle Fusion Middleware products, Compatibility is defined as the ability of two Oracle Fusion Middleware components of different versions (or releases) to interoperate.
For a list of products and features available in Oracle Fusion Middleware Release 12.2.1.4.0, see Products and Features Available in Oracle Fusion Middleware 12c (12.2.1.4.0) in Understanding Interoperability and Compatibility.
Terminology Used in this Guide
For consistency, the following terminology is used in this guide.
Table 1-1 Terminology
| Information | Example Value | Description |
|---|---|---|
|
|
|
Environment variable that points to the Java JDK home directory. |
|
Database host |
|
Name and domain of the host where the database is running. |
|
Database port |
|
Port number that the database listens on. The default Oracle database listen port is |
|
Database service name |
|
Oracle databases require a unique service name. The default service name is |
|
DBA username |
|
Name of user with database administration privileges. The default DBA user on Oracle databases is |
|
DBA password |
|
Password of the user with database administration privileges. |
|
|
|
12c directory in which you will install your software. This directory will include Oracle Fusion Middleware Infrastructure and Oracle Identity Manager, as needed. |
|
Console port |
|
Port for Oracle WebLogic Server and Oracle Identity Manager consoles. |
|
|
|
Location in which your domain data is stored. Note: This is the domain where the primary Administration server is configured. |
|
|
|
Location in which your application data is stored. |
|
Administrator user name for your WebLogic domain |
|
Name of the user with Oracle WebLogic Server administration privileges. The default administrator user is |
|
Administrator user password |
|
Password of the user with Oracle WebLogic Server administration privileges. |
|
RCU |
|
Path to the Repository Creation Utility (RCU). |
|
RCU schema prefix |
|
Prefix for names of database schemas used by Oracle Identity Manager. |
|
RCU schema password |
|
Password for the database schemas used by Oracle Identity Manager. |
|
Configuration utility |
|
Path to the Configuration Wizard for domain creation and configuration. |
How to Use This Guide
This guide covers various upgrade scenarios.
Depending on your existing deployment, refer to the respective topics for upgrading Oracle Identity Manager to 12c (12.2.1.4.0):
- In-Place Upgrade
- Single Node Environments: For upgrading a single node Oracle Identity Manager (OIM) setup, see Upgrading Oracle Identity Manager Single Node Environments.
- Multi-node or Highly Available Environments: For upgrading a multi-node Oracle Identity Manager setup, see Upgrading Oracle Identity Manager Highly Available Environments.
- Out-of-Place Upgrade: For instructions to upgrade out-of-place, see Performing an Out-of-Place Upgrade of Oracle Identity Manager
- Out-of-Place Cloned Upgrade: For instructions to perform an out-of-place cloned upgrade, see Performing an Out-of-Place Cloned Upgrade of Oracle Identity Manager.
- One-Hop-Upgrade:
- For upgrading a single node Oracle Identity Manager (OIM) setup, see Upgrading Oracle Identity Manager Single Node Environments.
- For upgrading Oracle Identity Manager highly available environments, see Upgrading Oracle Identity Manager Highly Available Environments.
Note:
Before you begin the upgrade, ensure that you review the Pre-Upgrade Requirements and perform the necessary pre-upgrade tasks.