Oracle Access Manager (OAM) Steps For Converting Clone To Primary And Vice Versa For Automated Policy Synchronization (APS) Functionality
(Doc ID 2108116.1)
Last updated on MARCH 31, 2022
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
OAM 184.108.40.206.x (PS3)
Multi Data Center
Several Node clustered OAM servers (in each data center) without external load balancing
Coexistence with 10g
Automated Policy Synchronization
What are the steps required to convert Clone to Primary and vice versa in a Multi Data Center setup for APS functionality to work?
This is the requirement. In the event of Primary DC (say DC1) is down for a considerably large amount of time, then it should be possible to convert Clone DC (say DC2) to Primary and vice versa.
Then apply some configuration changes in the DC2. When the the DC1 is brought up, then the configuration changes are synchronized into DC1 from DC2 through APS utility.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document