1. Upgrading Oracle Access Manager
  2. Pre-Upgrade Requirements

2 Pre-Upgrade Requirements

Before you begin to upgrade Oracle Access Manager 12c (12.2.1.4.0), you must perform pre-upgrade tasks such as backing up, creating a replica of your current environment, and verifying that your system meets certified requirements.

Oracle Fusion Middleware Pre-Upgrade Checklist

Perform the tasks in this checklist before you begin any upgrade to ensure you have a successful upgrade and limited downtime.

Upgrades are performed while the servers are down. This checklist identifies important and often time-consuming pre-upgrade tasks that you can perform before the upgrade to limit your downtime. The more preparation you do before you begin the upgrade process, the less time you will spend offline.

Note:

The pre-upgrade procedures you perform will depend on the configuration of your existing system, the components you are upgrading, and the environment you want to create at the end of the upgrade and configuration process. Complete only those tasks that apply to your configurations or use cases.

Ensure that Oracle Identity Manager and Oracle Access Manager are in different domains. If they are in the same domain, then you need to separate them into multiple domains. For more information, see Separating Oracle Identity Management Applications Into Multiple Domains.

Table 2-1 Tasks to Perform Before You Upgrade to Oracle Fusion Middleware 12c (12.2.1.4.0)

Task Description

Required

Create a complete backup of your existing environment.

Back up all system-critical files and database(s) that contain any schemas that are to be upgraded. If the upgrade fails, you must restore your pre-upgrade environment and begin the upgrade again.

See Creating a Complete Backup.

If you modified any of the startup scripts in your existing domain, you will need to copy them to temporary directory location (outside of the existing domain) during the upgrade and redeploy them after the upgrade. See Maintaining Customized Domain and Environment Settings.

Required

Ensure that the keystore files are valid.

See Validating the Keystore Files.

Optional

Shut down all the local and remote Node Managers before starting the upgrade process.

See Shutting Down the Node Managers.

Parent topic: Pre-Upgrade Requirements

Creating a Complete Backup

Before you start an upgrade, back up all system-critical files, including the Oracle home, Domain home, and databases that host your Oracle Fusion Middleware schemas.

The backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table so that you can restore the contents back to its pre-upgrade state if the upgrade fails.

See:
  • Maintaining Customized Domain and Environment Settings
    If you have modified any domain-generated, server startup scripts, or configuration files in your pre-upgrade environment, it is important to note that these changes are overwritten during the installation, and reconfiguration operations. Oracle recommends you to take a backup of the the customized files to a shared library location. In case of any failure or issues during the upgrade process, you can restore these files, if required.

Parent topic: Pre-Upgrade Requirements

Maintaining Customized Domain and Environment Settings

If you have modified any domain-generated, server startup scripts, or configuration files in your pre-upgrade environment, it is important to note that these changes are overwritten during the installation, and reconfiguration operations. Oracle recommends you to take a backup of the the customized files to a shared library location. In case of any failure or issues during the upgrade process, you can restore these files, if required.

Every domain installation includes dynamically-generated domain and server startup scripts, such as setDomainEnv. These files are replaced by newer versions during the installation and upgrade process.

For example, if you want to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.cmd (Windows) or setUserOverrides.sh (UNIX) and configure it to add custom libraries to the WebLogic Server classpath, specify additional command-line options for running the servers, or specify additional environment variables. When using the pack and unpack commands, any custom settings that you add to this file are preserved during the domain upgrade operation and are carried over to the remote servers.

The following example illustrates startup customizations in a setUserOverrides file:
# add custom libraries to the WebLogic Server system claspath
  if [ "${POST_CLASSPATH}" != "" ] ; then
    POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${HOME}/foo/fooBar.jar"
    export POST_CLASSPATH
  else
    POST_CLASSPATH="${HOME}/foo/fooBar.jar"
    export POST_CLASSPATH
  fi
 
# specify additional java command-line options for servers
JAVA_OPTIONS="${JAVA_OPTIONS}  -Dcustom.property.key=custom.value"

If the setUserOverrides file exists during a server startup, the file is included in the startup sequence and any overrides contained within this file take effect. You must store the setUserOverrides file in the DOMAIN_HOME/bin directory.

Note:

If you are unable to create the setUserOverrides script before an upgrade, you need to reapply your settings as described in Re-apply Customizations to Startup Scripts in Upgrading Oracle WebLogic Server.

Parent topic: Creating a Complete Backup

Validating the Keystore Files

Before performing the upgrade, ensure that the following keystore files are valid and are not in a corrupted state:
  • oamkeystore.jks
    Use this command to validate the file:
    keytool -list -keystore $DOMAIN_HOME/config/fmwconfig/.oamkeystore -storepass
xxx -storetype jceks
  • Default-keystore.jks
    Use this command to validate the file:
    keytool -list -keystore $DOMAIN_HOME/config/fmwconfig/default-keystore.jks
-storepass xxx -storetype jceks

Note:

Do not start the upgrade if there is an issue in any of these keystore files.

Parent topic: Pre-Upgrade Requirements

Shutting Down the Node Managers

Ensure that you have shut down all the local and remote Node Managers before starting the upgrade process.

The Node Managers should remain shut down until you start the WebLogic Administration Server after completing the upgrade. When the WebLogic Administration Server is up and running, start the Node Managers, followed by the Managed Servers.

Parent topic: Pre-Upgrade Requirements