1 Introduction to Upgrading Oracle Access Manager 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 Access Manager 12c (12.2.1.3.0).

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:

• Planning an Upgrade to Oracle Fusion Middleware 12c (12.2.1.3.0)

• Understanding In-Place versus Out-of-Place Upgrades

• Understanding the Basic Upgrade Tasks

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 12c (12.2.1.3.0) from a supported 11g release.
• About the Oracle Access Manager Upgrade Scenarios
  The steps to upgrade Oracle Access Manager to 12c (12.2.1.3.0) depend on the existing 11g Release 2 (11.1.2.3.0) production topology.
• About the New Features for Oracle Access Manager 12c
  Several changes have been made to Oracle Access Manager between 11g and 12c.
• 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 12c (12.2.1.3.0) from a supported 11g release.

Supported starting point for is upgrading Oracle Access Manager to 12c (12.2.1.3.0) is Oracle Access Manager 11g Release 2 (11.1.2.3.0).

If you are not using the 11.1.2.3.0 version of Oracle Access Manager, you must upgrade to 11.1.2.3.0 before you move to 12c (12.2.1.3.0).

For information about upgrading Oracle Access Manager to 11g Release 2 (11.1.2.3.0), see Introduction to Oracle Identity and Access Management Upgrade in the Upgrade Guide for Oracle Identity and Access Management for 11g Release 2 (11.1.2.3.0).

The upgrade procedures in this guide explain how to upgrade an existing Oracle Access Manager 11g domain to Oracle Access Manager 12c (12.2.1.3.0). If your domain contains other components, you will have to upgrade those components as well. Links to supporting documentation are provided wherever necessary.

For information about upgrade planning recommendations, see Doc ID 2539939.2.

About the Oracle Access Manager Upgrade Scenarios

The steps to upgrade Oracle Access Manager to 12c (12.2.1.3.0) depend on the existing 11g Release 2 (11.1.2.3.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, it can however be used as a guide for the less common deployment topologies.

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.

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.

You can upgrade the following topologies or deployments using the procedure described in this guide:

• Single node environments

• Highly available (multinode) environments

• Oracle Access Manager Multi-data center setup

• Oracle Identity Manager and Oracle Access Manager integrated environments that are set up manually in 11.1.2.3.0

• Oracle Identity Manager and Oracle Access Manager integrated environments that are set up using Life Cycle Management (LCM) tool in 11.1.2.3.0

Note:

If you are using Oracle Access Manager Mobile and Social, read about the features not supported in this release of OAM before considering an upgrade to 12c (12.2.1.3.0). See Features Not Supported in Access Manager 12.2.1.3.0.

About the New Features for Oracle Access Manager 12c

Several changes have been made to Oracle Access Manager between 11g and 12c.

To understand what's new in general in Oracle Fusion Middleware 12c, 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.

For information about Oracle Access Manager 12c (12.2.1.3.0), and it’s features, refer to the following topics in the Administrator's Guide for Oracle Access Manager:

• Features of Access Manager 12.2.1.3.0
• Features Not Supported in Access Manager 12.2.1.3.0
• Understanding Oracle Access Manager Services
• Understanding Oracle Access Management Access Manager

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.0) components are generally interoperable with other 12c (12.2.1.0) components.

To facilitate a graceful upgrade of the components to 12c, during the upgrade, Oracle Access Manager 12c is compatible with OAM WebGate 11g (11.1.2.3), RREG11g Client 11g (11.1.2.3 with latest bundle patch), and ASDK 11g.

After you upgrade Oracle HTTP Server (OHS) from 12.2.1.2.0 (WebGate based on 11.1.2.3.0 OAM architecture) to the OHS 12.2.1.3.0 (WebGate based on 12.2.1.3.0 OAM architecture), you will need to add the User Defined Parameter of UniqueCookieNames=Legacy to the WebGate agent configuration through the OAM console. Adding the parameter ensures that the WebGate cookie name format is recognized by the OHS WebGate after the upgrade to 12c (12.2.1.3). For instructions, see Doc ID 2673236.1. For a list of the supported WebGate parameters, see User-Defined WebGate Parameters in Administering Oracle Access Management.

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 12.2.1.3.0, see Products and Features Available in Oracle Fusion Middleware 12c (12.2.1.3.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
JAVA_HOME	/home/Oracle/Java/jdk1.8.0_131	Environment variable that points to the Java JDK home directory.
Database host	examplehost.exampledomain	Name and domain of the host where the database is running.
Database port	1521	Port number that the database listens on. The default Oracle database listen port is 1521.
Database service name	orcl.exampledomain	Oracle databases require a unique service name. The default service name is orcl.
DBA username	FMW	Name of user with database administration privileges. The default DBA user on Oracle databases is SYS.
DBA password	<dba_password>	Password of the user with database administration privileges.
ORACLE_HOME	/home/Oracle/product/ORACLE_HOME	12c directory in which you will install your software. This directory will include Oracle Fusion Middleware Infrastructure and Oracle Access Manager, as needed.
Console port	7001	Port for Oracle WebLogic Server and Oracle Access Manager consoles.
DOMAIN_HOME	/home/Oracle/config/domains/idm_domain	Location in which your domain data is stored. Note: This is the domain where the primary Administration server is configured.
APPLICATION_HOME	/home/Oracle/config/applications/idm_domain	Location in which your application data is stored.
Administrator user name for your WebLogic domain	weblogic	Name of the user with Oracle WebLogic Server administration privileges. The default administrator user is weblogic.
Administrator user password	<admin_password>	Password of the user with Oracle WebLogic Server administration privileges.
RCU	ORACLE_HOME/oracle_common/bin	Path to the Repository Creation Utility (RCU).
RCU schema prefix	oam	Prefix for names of database schemas used by Oracle Access Manager.
RCU schema password	<rcu_password>	Password for the database schemas used by Oracle Access Manager.
Configuration utility	ORACLE_HOME/oracle_common/common/bin	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 11.1.2.3.0 deployment, refer to the respective topics for upgrading Oracle Access Manager to 12c (12.2.1.3.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.

• OIM-OAM Integrated Highly Available Environments:

  • For upgrading OIM-OAM integrated highly available deployment, that was set up manually in 11g, see Upgrading OIM-OAM Integrated Environments set up Manually.

  • For upgrading OIM-OAM integrated highly available deployment, that was set up using Life Cycle Management (LCM) tool in 11g, see Upgrading OIM-OAM Integrated Environments set up Using Life Cycle Management Tool.

Note:

Before you begin the upgrade, ensure that you review the Pre-Upgrade Requirements and perform necessary pre-upgrade tasks.