2-38 Oracle Fusion Middleware Disaster Recovery Guide
Recovery Recommendations Oracle Universal Content Management must be recovered with the OCS and MDS
schemas to the most recent point in time.
2.8.2 Recommendations for Oracle Inbound Refinery
Oracle Inbound Refinery is a conversion server that manages file conversions for electronic assets such as documents, digital images, and motion video. In addition to
conversion, Oracle Inbound Refinery provides thumbnail functionality for documents and images, storyboarding for video, and the ability to extract and use EXIF data from
digital images and XMP data from electronic files generated from programs such as Adobe Photoshop and Adobe Illustrator. You can use Oracle Inbound Refinery to
convert content items stored in Oracle Content Server.
This section describes various Oracle Inbound Refinery artifacts and provides recommendations for disaster recovery.
Artifacts in the Database Oracle Inbound Refinery does not have any database dependencies.
Special Considerations The load balancer virtual hosts required for Oracle Inbound Refinery should be
configured on both the production and standby sites.
Synchronization Recommendations The directory tier must be manually synchronized with the standby site after making
configuration changes and applying patches.
Recovery Recommendations Recover the Oracle Inbound Refinery instance.
2.8.3 Recommendations for Oracle Imaging and Process Management
Oracle Imaging and Process Management provides organizations with a scalable solution upon which to develop process-oriented imaging applications and
image-enablement solutions for enterprise applications. Oracle Imaging and Process Management enables image capture via Oracle Document Capture and Oracle
Distributed Document Capture, annotation and markup of images, workflow support for routing and approval automation, and support for high-volume applications for
millions of items. With Oracle Imaging and Process Management, organizations can quickly integrate their content and processes directly with Oracle enterprise
applications, such as Oracle E-Business Suite, PeopleSoft Enterprise, and JD Edwards EnterpriseOne. Users benefit by having a single source for all transaction-based
content, eliminating the need for double entry.
This section describes various Oracle Imaging and Process Management artifacts and provides recommendations for disaster recovery.
Artifacts on the File System The IPM Input Agent pulls files from a common file share. This IPM file share must be
synchronized with the standby site.
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
