4 Upgrading Oracle Access Manager Highly Available Environments

Describes the process of upgrading Oracle Access Manager highly available environments from 12c (12.2.1.4.0) to 14c (14.1.2.1.0).

About the Oracle Access Manager Multinode Upgrade Process

Review the topology and the roadmap for an overview of the upgrade process for Oracle Access Manager highly available environments.

The steps you take to upgrade your existing domain will vary depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.

Upgrade Topology

The following topology shows the Oracle Access Manager cluster set up that can be upgraded to 14c (14.1.2.1.0) by following the procedure described in this chapter.

Figure 4-1 Oracle Access Manager High Availability Upgrade Topology

Description of Figure 4-1 follows
Description of "Figure 4-1 Oracle Access Manager High Availability Upgrade Topology"
On OAMHOST1, the following installations have been performed:
  • An Oracle Access Server has been installed in the WLS_OAM1 Managed Server.

  • A WebLogic Server Administration Server has been installed. Under normal operations, this is the active Administration Server.

On OAMHOST2, the following installations have been performed:

  • An Oracle Access Server has been installed in the WLS_OAM2 Managed Server.

  • A WebLogic Server Administration Server has been installed. Under normal operations, this is the passive Administration Server. You make this Administration Server active if the Administration Server on OAMHOST1 becomes unavailable.

The instances in the WLS_OAM1 and WLS_OAM2 Managed Servers on OAMHOST1 and OAMHOST2 are configured in a cluster named OAM_CLUSTER.

Note:

This topology diagram is only for illustration purposes. Typical customer topologies may have more than two OAM server nodes in their cluster. They may also have a separate cluster of OAM Policy Manager server nodes.

Table 4-1 Tasks for Upgrading Oracle Access Manager Highly Available Environments

Task Description

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

See:

Required

Create backup of the existing 12c (12.2.1.4.0) Middleware home folders on OAMHOSTs

See Backing up the 12c (12.2.1.4.0) Middleware Home Folder on OAMHOSTs.

Required on OAMHOST1

Shut down the 12c environment (stop all Administration and Managed Servers) on OAMHOST1.

Ensure that the Database is up during the upgrade.

WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required on OAMHOST1

On OAMHOST1, uninstall Oracle Fusion Middleware Infrastructure and Oracle Access Manager 12c (12.2.1.4.0) in the existing Oracle home.

See unresolvable-reference.html#GUID-F120C0FD-016C-4F5A-A989-7AAA3917B13A.

Required on OAMHOST1

On OAMHOST1, install Infrastructure (JRF) 14c (14.1.2.1.0) and Oracle Access Manager 14c (14.1.2.1.0) in the existing Oracle home.

See Installing Product Distributions on OAMHOSTs.

Required on OAMHOST1

Start the servers on OAMHOST1.

See Starting the Servers.

Required on OAMHOST2

Shut down the 12c environment (stop all Managed Servers) on OAMHOST2.

Ensure that the Database is up during the upgrade.

WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required on OAMHOST2

On OAMHOST2, uninstall Oracle Fusion Middleware Infrastructure and Oracle Access Manager 12c (12.2.1.4.0) in the existing Oracle home.

See unresolvable-reference.html#GUID-F120C0FD-016C-4F5A-A989-7AAA3917B13A.

Required on OAMHOST2

On OAMHOST2, install Infrastructure (JRF) 14c (14.1.2.1.0) and Oracle Access Manager 14c (14.1.2.1.0) in the existing Oracle home.

See Installing Product Distributions on OAMHOSTs.

Required on OAMHOST2

Start the node manager and managed servers on OAMHOST2.

See Starting the Servers.

Backing up the 12c (12.2.1.4.0) Middleware Home Folder on OAMHOSTs

Backup the 12c (12.2.1.4.0) Middleware Home on both OAMHOST1 and OAMHOST2.

As a backup, copy and rename the 12.2.1.4.0 Middleware home folder on OAMHOST1 and OAMHOST2.

For example:

From /u01/app/fmw/ORACLE_HOME to /u01/app/fmw/ORACLE_HOME_old

Stopping Servers and Processes

Before you upgrade the configurations, you must shut down all of the pre-upgrade processes and servers, including the Weblogic Admin, Managed, and Node Manager servers that are running on the intended OAMHOST.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below:

Note:

It is important that you stop the following servers in the correct order.

Step 1: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop Any Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 3: Stop the Administration Server

To stop the Administration Server, use the stopWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 4: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in WLST Command Reference for Oracle WebLogic Server.

Uninstalling the Software

Follow the instructions in this section to start the Uninstall Wizard and remove the software.

If you want to uninstall the product in a silent (command-line) mode, see Running the Oracle Universal Installer for Silent Uninstallation in Installing Software with the Oracle Universal Installer.

Starting the Uninstall Wizard

Start the Uninstall Wizard:

  1. Change to the following directory:
    (UNIX) ORACLE_HOME/oui/bin
    (Windows) ORACLE_HOME\oui\bin
  2. Enter the following command:
    (UNIX) ./deinstall.sh
    (Windows) deinstall.cmd

Selecting the Product to Uninstall

Because multiple products exist in the Oracle home, ensure that you are uninstalling the correct product.

After you run the Uninstall Wizard, the Distribution to Uninstall screen opens.

From the drop-down menu, select the Oracle Fusion Middleware 14c (14.1.2.1.0) Oracle Access Manager product and click Uninstall.

Note:

The Uninstall Wizard displays the Distribution to Uninstall screen only if it detects more than one product distribution in the Oracle home from where you initate the wizard. If only Oracle Fusion Middleware 14c (14.1.2.1.0) Oracle Access Manager product distribution is available, the Uninstall Wizard will display the Deinstallation Summary screen.

Note:

Do not select Weblogic Server for FMW.

Note:

You can uninstall Oracle Fusion Middleware Infrastructure after you uninstall OIM or OAM software by running the Uninstall Wizard again. Before doing so, ensure that there are no other products using the Infrastructure, as those products will no longer function once the Infrastructure is removed. You will not encounter the Distribution to Uninstall screen if no other software depends on Oracle Fusion Middleware Infrastructure. See, Uninstalling Oracle Fusion Middleware Infrastructure in Installing and Configuring the Oracle Fusion Middleware Infrastructure

Navigating the Uninstall Wizard Screens

The Uninstall Wizard shows a series of screens to confirm the removal of the software.

If you need help on screen listed in the following table, click Help on the screen.

Table 4-2 Uninstall Wizard Screens and Descriptions

Screen Description

Welcome

Introduces you to the product Uninstall Wizard.

Uninstall Summary

Shows the Oracle home directory and its contents that are uninstalled. Verify that this is the correct directory.

If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use the response file later to uninstall the product in silent (command-line) mode. See Running the Oracle Universal Installer for Silent Deinstallation in Installing Software with the Oracle Universal Installer.

Click Deinstall to begin removing the software.

Uninstall Progress

Shows the uninstallation progress.

Uninstall Complete

Appears when the uninstallation is complete. Review the information on this screen, then click Finish to close the Uninstall Wizard.

Note:

  • Repeat these steps for uninstalling Weblogic Server for FMW.

    You will be reinstalling the Oracle binaries into the same ORACLE_HOME location.

  • After the product is uninstalled, ensure that the ORACLE_HOME folder exists. During the initial 12c (12.2.1.4.0) install, if the default location was ORACLE_HOME, that is /user_projects, then the domain-registry.xml file will reside in ORACLE_HOME.
Complete the following steps to clean this directory:
  1. After both OAM and WLS are uninstalled, run the following command:
    $ ls -al
    Following is an example of the output:
    total 28
    drwxr-x---. 6 <USER> <GROUP> 4096 Apr  2 20:27 .
    drwxr-x---. 6 <USER> <GROUP> 4096 Jul  9  2019 ..
    drwxr-x---. 5 <USER> <GROUP> 4096 Mar 23 17:48 cfgtoollogs
    -rw-r-----. 1 <USER> <GROUP>  225 Jul  9  2019 domain-registry.xml
    drwxr-x---. 7 <USER> <GROUP> 4096 Mar 26 17:12 .patch_storage
    drwxr-x---. 4 <USER> <GROUP> 4096 Jul  9  2019 user_projects
    drwxr-x---. 3 <USER> <GROUP> 4096 Apr  2 20:26 wlserver
    
  2. Go to the ORACLE_HOME location. If the user_projects directory and the domain-registry.xml file are present, take their backup. They need to be restored after the upgrade is complete. After taking the backup, delete all the files in ORACLE_HOME.

Installing Product Distributions on OAMHOSTs

Install the binaries on an OAMHOST.

Complete the following steps:
  1. Install the following products on the OAMHOST.
    • Oracle Fusion Middleware Infrastructure 14c (14.1.2.0.0)

    • Oracle Identity and Access Management 14c (14.1.2.1.0)

    • Any additional distributions for your pre-upgrade environment

Installing Product Distributions

Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Access Manager 14c (14.1.2.1.0) distributions on the target system and install them using Oracle Universal Installer.

Note:

If you are using Redundant binary locations, ensure that you install the software into each of those redundant locations.

To install the 14c (14.1.2.1.0) distributions:
  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    • Oracle Fusion Middleware Infrastructure (fmw_14.1.2.0.0_infrastructure.jar)
    • Oracle Access Manager (fmw_14.1.2.1.0_idm.jar)
    • Any additional distributions for your pre-upgrade environment

    Note:

    If you are upgrading an integrated environment that was set up using Life Cycle Management (LCM) tool, that includes Oracle Access Manager, Oracle Identity Manager, and WebGates, then you must install the respective binaries in the same Oracle Home.

  3. Change to the directory where you downloaded the product distribution
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_14.1.2.0.0_infrastructure.jar
    • (Windows) JDK_HOME\bin\java -jar fmw_14.1.2.0.0_infrastructure.jar
  5. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select the following:
    • For Infrastructure, select Fusion Middleware Infrastructure
    • For Oracle Access Manager, select Collocated Oracle Identity and Access Manager.
    Click Next.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  13. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
  14. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:

    (UNIX) JAVA_HOME/bin/java -jar fmw_14.1.2.1.0_idm.jar

    (Windows) JAVA_HOME\bin\java -jar fmw_14.1.2.1.0_idm.jar

Note:

  • If your 12c (12.2.1.4.0) setup was deployed using Life Cycle Management (LCM) tool, you must install Oracle HTTP Server 14c (14.1.2.1.0) in the 14c Middleware home. See Preparing to Install and Configure Oracle HTTP Server in Installing and Configuring Oracle HTTP Server.
  • By using the opatch tool, apply the latest recommended patchsets from Oracle Support. Complete only the binary installation of patchsets and follow any post-patch steps after the upgrade process is complete. This provides the latest known fixes for upgrade process, if any.

Running a Pre-Upgrade Readiness Check

To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.

About Running a Pre-Upgrade Readiness Check

You can run the Upgrade Assistant in -readiness mode to detect issues before you perform the actual upgrade. You can run the readiness check in GUI mode using the Upgrade Assistant or in silent mode using a response file.

The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your Fusion Middleware schemas and WebLogic domain configurations that are at a supported starting point. The review is a read-only operation.

The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.

You can run the readiness check while your existing Oracle Fusion Middleware domain is online (while other users are actively using it) or offline.

You can run the readiness check any number of times before performing any actual upgrade. However, do not run the readiness check after an upgrade has been performed, as the report results may differ from the result of pre-upgrade readiness checks.

Note:

To prevent performance from being affected, Oracle recommends that you run the readiness check during off-peak hours.

Starting the Upgrade Assistant in Readiness Mode

Use the -readiness parameter to start the Upgrade Assistant in readiness mode.

To perform a readiness check on your pre-upgrade environment with the Upgrade Assistant:
  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin

    Where, ORACLE_HOME is the 14c (14.1.2.1.0) Oracle Home.

  2. Start the Upgrade Assistant.
    • (UNIX) ./ua -readiness
    • (Windows) ua.bat -readiness

    Note:

    If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter the following error:
    Xlib: connection to ":1.0" refused by server
    Xlib: No protocol specified 

    To resolve this issue you need to set the DISPLAY variable to the host and desktop where a valid X environment is working.

    For example, if you are running an X environment inside a VNC on the local host in desktop 6, then you would set DISPLAY=:6. If you are running X on a remote host on desktop 1 then you would set this to DISPLAY=remoteHost:1.

    For information about other parameters that you can specify on the command line, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 4-3 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Performing a Readiness Check with the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.

Readiness checks are performed only on schemas or component configurations that are at a supported upgrade starting point.
To complete the readiness check:
  1. On the Welcome screen, review information about the readiness check. Click Next.
  2. On the Readiness Check Type screen, select Domain Based.

    The Domain Based option enables the Upgrade Assistant to discover and select all upgrade-eligible schemas or component configurations in the domain specified in the Domain Directory field.

    When you select this option, the screen name changes to Schemas and Configuration.

    Leave the default selection if you want the Upgrade Assistant to check all schemas and component configurations at the same time, or select a specific option:

    • Include checks for all schemas to discover and review all components that have a schema available to upgrade.

    • Include checks for all configurations to review component configurations for a managed WebLogic Server domain.

  3. In the Domain Directory field, select the 12c (12.2.1.4.0) domain folder that was copied to the 14c (14.1.2.1.0) setup machine. If the 14c (14.1.2.1.0) setup is on the same machine as the 12c Release, provide the 12c domain home location during the readiness check.

    Click Next.

  4. The Component List screen displays the list of components whose schema will be upgraded.

    Click Next.

  5. On the Schema Credentials screen, specify the database credentials to connect to the selected 12c (12.2.1.4.0) schema: Database Type, DBA User Name, and DBA Password. As part of the pre-upgrade requirements, you had created the required user, see Creating a Non-SYSDBA User to Run the Upgrade Assistant.

    Then click Connect.

    Note:

    Oracle database is the default database type. Make sure that you select the correct database type before you continue. If you discover that you selected the wrong database type, do not go back to this screen to change it to the correct type. Instead, close the Upgrade Assistant and restart the readiness check with the correct database type selected to ensure that the correct database type is applied to all schemas.

    Select the Schema User Name option and specify the Schema Password.

    Note:

    The Upgrade Assistant automatically enables the default credentials. If you are unable to connect, ensure that you manually enter the credentials for your schema before you continue.

    Click Next until all schema connections are validated (the screen name changes based on the schema selected).

    Note:

    If you encounter any connection failure, check the cause and fix it.
  6. On the Readiness Summary screen, review the summary of the readiness checks that will be performed based on your selections.
    If you want to save your selections to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    For a detailed report, click View Log.
    Click Next.
  7. On the Readiness Check screen, review the status of the readiness check. The process can take several minutes.
    If you are checking multiple components, the progress of each component displays in its own progress bar in parallel.
    When the readiness check is complete, click Continue.
    The following components are marked as ready for upgrade although they are not upgraded. Ignore the ready for upgrade message against these components:
    • Oracle JRF
    • Common Infrastructure Services
    • Oracle Web Services Manager
  8. On the End of Readiness screen, review the results of the readiness check (Readiness Success or Readiness Failure):
    • If the readiness check is successful, click View Readiness Report to review the complete report. Oracle recommends that you review the Readiness Report before you perform the actual upgrade even when the readiness check is successful. Use the Find option to search for a particular word or phrase within the report. The report also indicates where the completed Readiness Check Report file is located.

    • If the readiness check encounters an issue or error, click View Log to review the log file, identify and correct the issues, and then restart the readiness check. The log file is managed by the command-line options you set.

Understanding the Readiness Report

After performing a readiness check for your domain, review the report to determine whether you need to take any action for a successful upgrade.

The format of the readiness report file is:

readiness_timestamp.txt

where timestamp indicates the date and time of when the readiness check was run.

A readiness report contains the following information:

Table 4-4 Readiness Report Elements

Report Information Description Required Action
Overall Readiness Status: SUCCESS or FAILURE The top of the report indicates whether the readiness check passed or completed with one or more errors. If the report completed with one or more errors, search for FAIL and correct the failing issues before attempting to upgrade. You can re-run the readiness check as many times as necessary before an upgrade.

Timestamp

The date and time that the report was generated.

No action required.

Log file location

ORACLE_HOME/oracle_common/upgrade/logs

The directory location of the generated log file.

No action required.

Readiness report location

ORACLE_HOME/oracle_common/upgrade/logs

The directory location of the generated readiness report.

No action required.

Names of components that were checked

The names and versions of the components included in the check and status.

If your domain includes components that cannot be upgraded to this release, such as SOA Core Extension, do not attempt an upgrade.

Names of schemas that were checked

The names and current versions of the schemas included in the check and status.

Review the version numbers of your schemas. If your domain includes schemas that cannot be upgraded to this release, do not attempt an upgrade.

Individual Object Test Status: FAIL

The readiness check test detected an issue with a specific object.

Do not upgrade until all failed issues have been resolved.

Individual Object Test Status: PASS

The readiness check test detected no issues for the specific object.

If your readiness check report shows only the PASS status, you can upgrade your environment. Note, however, that the Readiness Check cannot detect issues with externals such as hardware or connectivity during an upgrade. You should always monitor the progress of your upgrade.

Completed Readiness Check of <Object> Status: FAILURE The readiness check detected one or more errors that must be resolved for a particular object such as a schema, an index, or datatype. Do not upgrade until all failed issues have been resolved.
Completed Readiness Check of <Object> Status: SUCCESS The readiness check test detected no issues. No action required.
Here is a sample Readiness Report file. Your report may not include all of these checks.
This readiness check report was created on Wed Dec 02 05:47:33 PST 2020 Log file is located at: 
/oracle/work/middleware_latest/oracle_common/upgrade/logs/ua2020-12-02-05-35-03AM.log
Readiness Check Report File: 
/oracle/work/middleware_latest/oracle_common/upgrade/logs/readiness2020-12-02-05-47-33AM.txt
Domain Directory: 
/oracle/work/middleware_1212/user_projects/domains/oim_domain

Starting readiness check of components.

Oracle Platform Security Services
    Starting readiness check of Oracle Platform Security Services.
      Schema User Name: DEV_OPSS
      Database Type: Oracle Database
      Database Connect String: example.oracle.com:1521:oimdb
      VERSION Schema DEV_OPSS is currently at version 11.1.1.9.0. 
Readiness checks will now be performed.
    Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
      INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
    Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
    Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
    Starting schema test:  Test that the schema does not contain any unexpected tables  TEST_UNEXPECTED_TABLES
    Completed schema test: Test that the schema does not contain any unexpected tables --> TEST_UNEXPECTED_TABLES +++ Test that the schema does not contain any unexpected tables
    Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
    Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
    Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
    Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
    Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
    Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
    Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
    Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
    Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
    Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
    Starting schema test:  TEST_UNEXPECTED_COLUMNS  Test that tables and views do not contain any unexpected columns
    Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
    Starting datatype test for table CT_29: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
    Completed datatype test for table CT_29: TEST_COLUMN_DATATYPES_V2 
--> Test that all table columns have the proper datatypes +++ PASS
    Starting index test for table JPS_ENTITY_LOCK: TEST_REQUIRED_INDEXES 
--> Test that the table contains all the required indexes
    Completed index test for table JPS_ENTITY_LOCK: 
TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
   Starting index test for table CT_9_3:  TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
    Completed index test for table CT_9_3: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
    Starting schema test:  UPGRADE_SCRIPT_TEST  Test that the middleware contains the required Oracle Platform Security Services upgrade script
    Completed schema test: UPGRADE_SCRIPT_TEST --> Test that the middleware contains the required Oracle Platform Security Services upgrade script +++ PASS
    Starting schema test:  PRIVILEGES_TEST  Test that the Oracle Platform Security Services schema has appropriate system privileges
    Completed schema test: PRIVILEGES_TEST --> Test that the Oracle Platform Security Services schema has appropriate system privileges +++ PASS
    Starting schema test:  SEQUENCE_TEST  Test that the Oracle Platform Security Services schema sequence and its properties are valid
    Completed schema test: SEQUENCE_TEST --> Test that the Oracle Platform Security Services schema sequence and its properties are valid 
+++ PASS
    Finished readiness check of Oracle Platform Security Services with
status: SUCCESS.

Oracle Metadata Services
    Starting readiness check of Oracle Metadata Services.
      Schema User Name: DEV_MDS
      Database Type: Oracle Database
      Database Connect String: example.oracle.com:1521:oimdb
      VERSION Schema DEV_MDS is currently at version 11.1.1.9.0. 
Readiness checks will now be performed.
    Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
    Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
    Starting schema test:  TEST_REQUIRED_PROCEDURES  Test that the schema contains all the required stored procedures
    Completed schema test: TEST_REQUIRED_PROCEDURES --> Test that the schema contains all the required stored procedures +++ PASS
    Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
    Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
    Starting index test for table MDS_ATTRIBUTES: TEST_REQUIRED_INDEXES 
--> Test that the table contains all the required indexes
    Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
    Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
    Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
    Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
    Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
      INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
    Finished readiness check of Oracle Metadata Services with status: 
SUCCESS.

User Messaging Service
    Starting readiness check of User Messaging Service.
      Schema User Name: DEV_ORASDPM
      Database Type: Oracle Database
      Database Connect String: example.oracle.com:1521:oimdb
      VERSION Schema DEV_ORASDPM is currently at version 11.1.1.9.0. Readiness checks will now be performed.
    Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
      INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
    Starting column test for table RULE_SET: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns
    Completed column test for table RULE_SET: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns +++ PASS
    Starting column test for table STATUS: TEST_UNEXPECTED_TABLE_COLUMNS 
--> Test that the table does not contain any unexpected columns
    Completed column test for table STATUS: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns +++ PASS
    Starting column test for table STATUS_ORPHAN: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns
    Completed column test for table STATUS_ORPHAN: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns +++ PASS
    Starting column test for table USER_DEVICE: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns
    Completed column test for table USER_DEVICE: 
TEST_UNEXPECTED_TABLE_COLUMNS --> Test that the table does not contain any unexpected columns +++ PASS
    Finished readiness check of User Messaging Service with status: SUCCESS.

Oracle SOA
    Starting readiness check of Oracle SOA.
      Schema User Name: DEV_SOAINFRA
      Database Type: Oracle Database
      Database Connect String: example.oracle.com:1521:oimdb
      VERSION Schema DEV_SOAINFRA is currently at version 11.1.1.9.0. Readiness checks will now be performed.
    Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
      INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
    Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
    Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
    Starting schema test:  TEST_REQUIRED_PROCEDURES  Test that the schema contains all the required stored procedures
    Completed schema test: TEST_REQUIRED_PROCEDURES --> Test that the schema contains all the required stored procedures +++ PASS
    Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
    Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
    Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
    Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
    Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
    Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
    Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
    Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
    Starting schema test:  SOA_TABLESPACE_VALIDATION  Test SOAINFRA schema for enough default table space and temp table space.
    Completed schema test: SOA_TABLESPACE_VALIDATION --> Test SOAINFRA schema for enough default table space and temp table space. +++ PASS
    Starting schema test:  SOA_INSTANCE_VALIDATION  Test SOAINFRA schema for inconsistencies of instance data.
    Completed schema test: SOA_INSTANCE_VALIDATION --> Test SOAINFRA schema for inconsistencies of instance data. +++ PASS
    Finished readiness check of Oracle SOA with status: SUCCESS.

Oracle Identity Manager
    Starting readiness check of Oracle Identity Manager.
      Schema User Name: DEV_OIM
      Database Type: Oracle Database
      Database Connect String: example.oracle.com:1521:oimdb
    Starting schema test:  examine  Calling examine method
      INFO Examine is successful
    Completed schema test: Examine --> Testing schema version +++ PASS
    Starting schema test:  TEST_MDS_BACKUP  Taking backup of MDS data related to OIM to handle any unseen situation during upgrade.
      INFO MDSBackup passes. Backup of MDS data related to OIM is here: 
/oracle/work/middleware_latest/oracle_common/upgrade/temp/mdsBackup/
    Completed schema test: TEST_MDS_BACKUP --> Taking backup of MDS data related to OIM to handle any unseen situration during upgrade. +++ PASS
    Finished readiness check of Oracle Identity Manager with status: 
SUCCESS.

User Messaging Service
    Starting readiness check of User Messaging Service.
    Starting config test:  TEST_USERMESSAGINGCONFIG  Test that configuration file usermessagingconfig.xml is accessible, in place and valid.
    Completed config test: TEST_USERMESSAGINGCONFIG --> Configuration file usermessagingconfig.xml is accessible, in place and valid. +++ PASS
    Starting config test:  TEST_ALREADY_UPGRADED  Test that configuration is not already upgraded.
    Completed config test: TEST_ALREADY_UPGRADED --> Configuration is not already upgraded. +++ PASS
    Finished readiness check of User Messaging Service with status: SUCCESS.

Oracle Identity Manager
    Starting readiness check of Oracle Identity Manager.
      INFO There are no configuration readiness tests for Oracle Identity Manager.
    Finished readiness check of Oracle Identity Manager with status: 
SUCCESS.

Oracle JRF
    Starting readiness check of Oracle JRF.
    Finished readiness check of Oracle JRF with status: SUCCESS.

System Components Infrastructure
    Starting readiness check of System Components Infrastructure.
    Starting config test:  TEST_SOURCE_CONFIG  Checking the source configuration.
      INFO
/oracle/work/middleware_1212/user_projects/oim_domain/opmn/topology.xml
was not found. No upgrade is needed.
    Completed config test: TEST_SOURCE_CONFIG --> Checking the source configuration. +++ PASS
    Finished readiness check of System Components Infrastructure with
status: ALREADY_UPGRADED.

Common Infrastructure Services
    Starting readiness check of Common Infrastructure Services.
    Starting config test:  CIEConfigPlugin.readiness.test  This tests the readiness of the domain from CIE side.
    Completed config test: CIEConfigPlugin.readiness.test --> This tests the readiness of the domain from CIE side. +++ PASS
    Finished readiness check of Common Infrastructure Services with
status: SUCCESS.

Oracle Web Services Manager
    Starting readiness check of Oracle Web Services Manager.
    Completed config test: BOOTSTRAP_PROPERTIES_CHECK --> Bootstrap properties check +++ PASS
    Completed config test: CONFIGURATION_PROPERTIES_CHECK --> Configuration properties check +++ PASS
    Completed config test: TOKEN_TRUST_PROPERTIES_CHECK --> Trust issuer properties check +++ PASS
    Completed config test: MDS_REPOSITORY_CONNECTIVITY_CHECK --> MDS repository connectivity check +++ PASS
    Finished readiness check of Oracle Web Services Manager with status: 
SUCCESS.

Finished readiness check of components.

Note:

You can ignore the missing index error in the readiness report. This is a known issue. The corresponding missing index is added during the schema upgrade operation. This error does not occur if the schema to be upgraded was created in 12c using the RCU.

Upgrading Schemas on OAMHOST1

Upgrade all of the necessary schemas for Oracle Access Management, on OAMHOST1 by using the Upgrade Assistant.

Run the Upgrade Assistant to upgrade the schemas.

Reconfiguring the Domain on OAMHOST1

Run the Reconfiguration Wizard on OAMHOST1 to reconfigure your domain component configurations to 14c (14.1.2.1.0).

To start the Reconfiguration Wizard in graphical mode from a Windows command prompt or on UNIX systems:

  1. Log in to the system on which the domain resides.
  2. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX).
  3. Go to the following directory, where ORACLE_HOME is your Oracle home directory:

    On Windows: ORACLE_HOME\oracle_common\common\bin

    On UNIX: ORACLE_HOME/oracle_common/common/bin

  4. Run the following commands:

    On Windows: reconfig.cmd

    On UNIX: sh reconfig.sh

The Reconfiguration Setup Progress screen appears.

Replicating the Domain Configurations on OAMHOST2

Replicate the domain configurations on OAMHOST2. This involves packing the upgraded domain on OAMHOST1 and unpacking it on OAMHOST2.

Complete the following steps:
  1. On OAMHOST1, run the following command from the location $MW_HOME/oracle_common/common/bin to pack the upgraded domain:
    • On UNIX:

      sh pack.sh -domain=<Location_of_OAM_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -template_name="OAM Domain" -managed=true

    • On Windows:

      pack.cmd -domain=<Location_of_OAM_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -template_name="OAM Domain" -managed=true

  2. Copy the domain configuration jar file created by the pack command on OAMHOST1 to any accessible location on OAMHOST2.
  3. On OAMHOST2, run the following command from the location $MW_HOME/oracle_common/common/bin to unpack the domain:
    • On UNIX:

      sh unpack.sh -domain=<Location_of_OAM_domain> -template=<absolute_path_to the_location_of_domain_configuration_jar_file> -overwrite_domain=true

    • On Windows:

      unpack.cmd -domain=<Location_of_OAM_domain> -template=<absolute_path_to the_location_of_domain_configuration_jar_file> -overwrite_domain=true

Upgrading Domain Component Configurations on OAMHOST1 and OAMHOST2

After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Upgrade the domain configurations on both OAMHOST1 and OAMHOST2.

Upgrading the Domain Configurations with the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

After running the Reconfiguration Wizard to reconfigure the WebLogic domain to 14c (14.1.2.1.0), you must run the Upgrade Assistant to upgrade the domain component configurations to match the updated domain configuration.

To upgrade domain component configurations with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the All Configurations screen, select All Configurations Used by a Domain and specify your domain location in the Domain Directory field by entering it directly or by clicking Browse to use a navigation tree to select a valid domain directory. Click Next.
  3. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5.  If there are remote managed servers hosting User Messaging Services (UMS) configuration files: On the UMS Configuration screen, provide the credentials to these servers so that the Upgrade Assistant can access the configuration files.

    Note:

    You may need to manually copy the UMS configuration files if the Upgrade Assistant is unable to locate them. See Error while Copying User Messaging Service (UMS) Configuration Files.
  6. On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  7. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  8. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  9. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.
    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Starting the Servers on OAMHOSTs

After you upgrade Oracle Access Manager on an OAMHOST, start the servers.

You must start the servers in the following order:
  1. Start the Node Manager on the required OAMHOST.

  2. Start the Administration Server on the required OAMHOST.

  3. Start the Oracle Access Manager Managed Servers on the required OAMHOST.

Starting Servers and Processes

After a successful upgrade, start all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

To start your Fusion Middleware environment, follow the steps below:

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console

.

Step 1: Start the Administration Server

To start the Administration Server, use the startWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startWebLogic.cmd

    Note:

    When using secured production mode, you must provide additional parameters to start the Administration Server. See Connecting to the Administration Server using WLST in Administering Security for Oracle WebLogic Server.

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startNodeManager.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start Any Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

  • (Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

    Note:

    When using secured production mode, you must provide additional parameters to start the Managed Servers. See Starting Managed Servers using a Start Script in Administering Security for Oracle WebLogic Server.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 4: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

  • (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Enabling WebGates to Work With Oracle Access Manager

After upgrading to Oracle Access Manager 14c (14.1.2.1.0), the earlier version of WebGates continues to work with Oracle Access Manager. However, to leverage the latest security features of Oracle Access Manager and WebGates 14c (14.1.2.0.0), you must upgrade the WebGates to 14c (14.1.2.0.0), and register the agent's profile with the Oracle Access Manager Server.

Note:

If you have any other components of Oracle Identity and Access Management deployed, then all of the components must to be upgraded to 14c (14.1.2.1.0) to leverage the new security features of 14c (14.1.2.1.0).

To upgrade the WebGates, you must upgrade the respective Web Servers to 14c (14.1.2.0.0).

To upgrade the Oracle HTTP Server WebGates, upgrade Oracle HTTP Server to 14c (14.1.2.0.0). See Upgrading a Standalone Oracle HTTP Server in the Upgrading Oracle HTTP Server.

After you upgrade the Web Servers, do the following:
  1. Register or edit the WebGate profile and copy the WebGate artifacts to the WebGate config folder. See Upgrading to OHS 14c (14.1.2.0.0) WebGate in the Installing WebGates for Oracle Access Manager.
  2. Start and stop the WebGates.