1 Introduction to Upgrading Oracle Access Manager to 14c (14.1.2.1.0)
Before you begin, review all introductory information to understand the standard upgrade topologies and upgrade paths for Oracle Access Manager 14c (14.1.2.1.0).
Note:
The product Oracle Identity Manager is referred to as Oracle Identity Manager (OIM) and Oracle Identity Governance (OIG) interchangeably in the guide.
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 Access Manager:
- About the Starting Points for a Oracle Access Manager Upgrade
You can upgrade to Oracle Access Manager 14c (14.1.2.1.0) from a supported 12c release. - About the Oracle Access Manager Upgrade Scenarios
The steps to upgrade Oracle Access Manager to 14c (14.1.2.1.0) depend on the existing 12c (12.2.1.4.0) production topology. - About the New Features for Oracle Access Manager 14c (14.1.2.1.0)
Several changes have been made to Oracle Access Manager between 12c (12.2.1.4.0) and 14c (14.1.2.1.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 Access Manager Upgrade
You can upgrade to Oracle Access Manager 14c (14.1.2.1.0) from a supported 12c release.
The supported starting point for upgrading Oracle Access Manager to 14c (14.1.2.1.0) is Oracle Access Manager 12c (12.2.1.4.0).
If you are not using the 12c (12.2.1.4.0) version of Oracle Access Manager, you must upgrade to 12c (12.2.1.4.0) before you move to 14c (14.1.2.1.0). For instructions, see the upgrade documentation for your release: Oracle Fusion Middleware Documentation Library.
The upgrade procedures in this guide explain how to upgrade an existing Oracle Access Manager 12c (12.2.1.4.0) domain to Oracle Access Manager 14c (14.1.2.1.0). If your domain contains other components, you will have to upgrade those components as well.
About the Oracle Access Manager Upgrade Scenarios
The steps to upgrade Oracle Access Manager to 14c (14.1.2.1.0) depend on the existing 12c (12.2.1.4.0) production topology.
Oracle Access 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.
Your actual topology may vary, but the topologies described here provide an example that can be used as a guide to upgrade other similar Oracle Access Manager topologies.
You can upgrade the following topologies or deployments using the procedure described in this guide:
About the New Features for Oracle Access Manager 14c (14.1.2.1.0)
Several changes have been made to Oracle Access Manager between 12c (12.2.1.4.0) and 14c (14.1.2.1.0).
To understand what's new in general in 14c (14.1.2.1.0), see New and Changed Features in Understanding Oracle Fusion Middleware.
For information about Oracle Access Manager 14c (14.1.2.1.0), and its features, see the following topics in Administering Oracle Access Management:
- Understanding Oracle Access Management Services
- Understanding Oracle Access Management Access Manager
For more information about new features in Oracle Access Manager 14c (14.1.2.1.0),see What's New in Oracle Access Management in the Release Notes for Oracle Identity Management.
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 14c (14.1.2.1.0) components are generally interoperable with other 14c (14.1.2.1.0) components. See Interoperability with Oracle Identity Management Products.
Note:
Exporting and importing OAM policies from other releases by using tools such as exportPolicy, importPolicy, and so on, is not certified. An upgrade is the only supported path to move policies from one release to another.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 14.1.2.1.0, see Products and Features Available in Oracle Fusion Middleware 14c (14.1.2.1.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. |
|
|
|
Directory in which you will install your software. This directory will include Oracle Fusion Middleware Infrastructure and Oracle Access Manager, as needed. |
|
Console port |
|
Port for Oracle Access Manager console. |
|
|
|
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 Access Manager. |
|
RCU schema password |
|
Password for the database schemas used by Oracle Access 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 12c (12.2.1.4.0) deployment, refer to the respective topics for upgrading Oracle Identity and Access Management to 14c (14.1.2.1.0):
-
Single Node Environments
For upgrading single node Oracle Access Manager (OAM) setup, see Upgrading Oracle Access Manager Single Node Environments.
-
Multi-node or Highly Available Environments
-
For upgrading multi-node Oracle Access Manager setup, see Upgrading Oracle Access Manager Highly Available Environments.
-
For upgrading Oracle Access Manager multi-data center setup, see Upgrading Oracle Access Manager Multi-Data Center Environments.
-
Note:
Before you begin the upgrade, ensure that you review the Pre-Upgrade Requirements and perform necessary pre-upgrade tasks.