2-26 Oracle Fusion Middleware Disaster Recovery Guide
Oracle Data Guard should be configured for Oracle database metadata repositories and the data stores.
It is recommended that the standby database be synchronized when the application tier synchronization is initiated on the storage. This synchronization occurs
automatically because Oracle Data Guard is configured in Managed Recovery mode the recommended configuration for the database. If the standby database is not in
Managed Recovery mode, then you should manually synchronize the standby database.
Recovery Recommendations Recover the managed server running the Oracle Adaptive Access Manager
application, and the associated Oracle Internet Directory instances. The OAAM, OAAM_PARTN, MDS, IAUand the ODS schemas must be recovered to the most
recent point in time.
2.5.8 Recommendations for
Oracle Identity Manager
Oracle Identity Manager is a user provisioning and administration solution that automates the process of adding, updating, and deleting user accounts from
applications and directories; and improves regulatory compliance by providing granular reports that identify which users have access to which applications. Oracle
Identity Manager is available as a stand-alone product or as part of Oracles Identity and Access Management Suite.
Oracle Identity Manager uses Oracle SOA for workflow, you must also follow the Oracle SOA disaster recovery recommendations. For more information, see
Recommendations for Oracle SOA Suite .
This section describes various Oracle Identity Manager artifacts and provides recommendations for disaster recovery.
Artifacts on the File System JMS Store: The volume containing the file-based JMS persistent store.
Artifacts in the Database Oracle Identity Manager uses OIM, SOAINFRA, ORASPDM, and MDS schemas,
which are part of the Oracle Identity Management database.
LDAP Store Oracle Identity Manager does not have any dependency on an external LDAP store
when used in the standalone mode. Oracle Identity Manager synchronizes users with and external LDAP store when LDAP Sync is enabled or when integrated with Oracle
Access Manager or Oracle Identity Federation.
Special Considerations Load balancer virtual hosts for Oracle Identity Manager should be configured on both
the production and standby sites.
The Oracle Identity Management and SOA Managed Servers are configured to listen on a floating IP addresses, this is required for Server Migration. Ensure that the
floating IP addresses are configured with the same Virtual Names on both the production and the standby sites.
Recommendations for Fusion Middleware Components 2-27
The connectors in Oracle Identity Manager are file-based. They are used to provision or reconcile records from different enterprise applications. Ensure that the connectors
are available for Oracle Identity Manager and the applications.
Oracle Identity Management
is also dependent on the JMS persistence store. For more information, see
Recommendations for Oracle WebLogic Server JMS and T-Logs .
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making configuration changes and applying patches.
Oracle Data Guard should be configured for Oracle database metadata repositories and the data stores.
It is recommended that the standby database be synchronized when the application tier synchronization is initiated on the storage. This synchronization occurs
automatically because Oracle Data Guard is configured in Managed Recovery mode the recommended configuration for the database. If the standby database is not in
Managed Recovery mode, then you should manually synchronize the standby database.
For JMS persistence store, see Recommendations for Oracle WebLogic Server JMS and
T-Logs .
Recovery Recommendations Recover the managed server running the Oracle Identity Manager application, and the
associated Oracle Internet Directory instances. The OIM, SOAINFRA, ORASPDM, and MDS schemas must be recovered to the most recent point in time. Oracle Identity
Management is dependent on the ODS schema when LDAP sync is enabled, in such cases make sure to recover the ODS to the most recent point in time as well
2.5.9 Recommendations for Oracle Authorization Policy Manager
