Recommendations for Fusion Middleware Components 2-39
Artifacts in the Database The IPM schema is part of the Oracle Imaging and Process Management database.
Oracle Imaging and Process Management also requires OCS schema, to use Oracle Universal Content Management as the Oracle Imaging and Process Management
repository.
Synchronization Recommendations The application tier and data tier must be manually synchronized with the standby
site after making configuration changes and applying patches.
The IPMJMSServerStore which is the JMS store must be synchronized with a file-based persistent store. For more information, see
Section 2.1.1, Recommendations for Oracle WebLogic Server JMS and T-Logs
.
Recovery Recommendations Oracle Imaging and Process Management must be recovered with the IPM schema to
the most recent point in time, along with the Managed Server running the Oracle Imaging and Process Management application, and the associated instances.
2.8.4 Recommendations for Oracle Information Rights Management
Oracle Information Rights Management distributes rights management between centralized servers and desktop agents.
Oracle Information Rights Management enables documents or emails to be automatically or manually sealed at any stage in their lifecycle, using sealing tools
integrated into the Microsoft Windows desktop, authoring applications, email clients, and content management and collaborative repositories. Sealing wraps documents
and emails within a layer of strong encryption and digital signatures, together with indelible links back to network-hosted servers operated by the organization to which
the information belongs that store the decryption keys and associated access rights.
Sealed documents and emails can be distributed by any existing means, including email, the Web, and file sharing.
This section describes various Oracle Information Rights Management artifacts and provides recommendations for disaster recovery.
Artifacts in the Database The ORAIRM schema is part of the Oracle Information Rights Management database.
In addition to the database, when you install Oracle Information Rights Management a key store is created that is used by the Oracle IRM J2EE application. It is recommended
that the key store is located in a directory under the domain home, so when the domain is restored the key store is automatically available. If the key store is not
stored under the domain, then you must manually copy the key store to the replicated system.
Special Considerations Load balancer virtual hosts for Oracle Identity Federation should be configured on
both the production and standby sites.
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making configuration changes and applying patches.
2-40 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 The databases containing the Oracle Information Rights Management schemas and the
data stores must be recovered to the most recent point in time, along with the Managed Server running the Oracle Information Rights Management application.
2.8.5 Recommendations for Oracle Universal Records Management
