Table of Contents
- Title and Copyright Information
- Preface
- 1 Introduction to Upgrading Oracle Access Manager to 14c (14.1.2.1.0)
-
2
Pre-Upgrade Requirements
- Oracle Fusion Middleware Pre-Upgrade Checklist
- Creating a Complete Backup
- Verifying Certification and System Requirements
- Creating a Non-SYSDBA User to Run the Upgrade Assistant
- Identifying Existing Schemas Available for Upgrade
- Verify the Database User for the WLSSchemaDataSource Data Source
- Remove the JAX-RS Deployment
- Ensuring that the Keystore Passwords are Same
- Shutting Down the Node Managers
-
Part I In-Place Upgrade of Oracle Access
Manager
-
3
Upgrading Oracle Access Manager Single Node Environments
- About the Oracle Access Manager Single Node Upgrade Process
- Completing the Pre-Upgrade Tasks for Oracle Access Manager
- Stopping Servers and Processes
- Uninstalling the Software
- Installing Product Distributions
- Running a Pre-Upgrade Readiness Check
- Upgrading Product Schemas
- Reconfiguring a WebLogic Domain
- Upgrading Domain Component Configurations
- Starting the Servers on an OAMHOST
- Enabling WebGates to Work With Oracle Access Manager
-
4
Upgrading Oracle Access Manager Highly Available Environments
- About the Oracle Access Manager Multinode Upgrade Process
- Backing up the 12c (12.2.1.4.0) Middleware Home Folder on OAMHOSTs
- Stopping Servers and Processes
- Uninstalling the Software
- Installing Product Distributions on OAMHOSTs
- Running a Pre-Upgrade Readiness Check
- Upgrading Schemas on OAMHOST1
- Reconfiguring the Domain on OAMHOST1
- Replicating the Domain Configurations on OAMHOST2
- Upgrading Domain Component Configurations on OAMHOST1 and OAMHOST2
- Starting the Servers on OAMHOSTs
- Enabling WebGates to Work With Oracle Access Manager
-
5
Upgrading Oracle Access Manager Multi-Data Center Environments
- About the Oracle Access Manager Multi-Data Center Topology
- Roadmap for Upgrading Oracle Access Manager MDC Setup
- Backing Up the Existing MDC Environment
- Enabling Write Permission to Primary and Clones (If Necessary)
- Disabling and Deleting All Replication Agreements Between Primary and Clone
- Redirecting Traffic to Primary Data Center
- Upgrading Oracle Access Manager on Clone Data Center
- Redirecting Traffic to Clone Data Center
- Upgrading Oracle Access Manager on Primary Data Center
- Freezing all Changes to Clones (if Necessary)
- Syncing Access Metadata
- Creating Replication Agreement
- Bringing up the Primary and Clone Data Centers Online
-
3
Upgrading Oracle Access Manager Single Node Environments
-
Part II Out-of-Place Upgrade of Oracle
Access Manager
-
6
Performing an Out-of-Place Upgrade of
Oracle Access Manager
- Pre-Upgrade Assessment
- Executing the pack command on the server where the Admin Server and one of the Managed Servers is installed.
- Install the 12c Binaries on the Target Before Unpack
- Executing the unpack Command from the 12c Oracle Home on HOST2.
- Running a Pre-Upgrade Readiness Check
- Upgrading Product Schemas
- Reconfiguring a WebLogic Domain
- Upgrading Domain Component Configurations
- Starting Servers and Processes
-
6
Performing an Out-of-Place Upgrade of
Oracle Access Manager
-
A
Troubleshooting the Oracle Access Manager
Upgrade
- Troubleshooting OAM During the Upgrade
- Activation State is set as FAILED when Restarting the Admin Server
- AMInitServlet Fails to Preload when Restarting OAM Managed Server
- File Not Found Exception when Starting the OAM Managed Server
- Error When Starting SSL Enabled OAM Managed Server After Upgrade
- OAM Upgrade Fails With InvalidKeyException
- OWSM Error Messages in the Reconfiguration Logs
- B Upgrade Scenarios for OAM