2-18 Oracle Fusion Middleware Disaster Recovery Guide
■
Packaged-Application Adapters
■
Oracle Adapter for Oracle Applications See Oracle Fusion Middleware Users Guide for Technology Adapters for additional
information about the types of Oracle JCA Adapters. This section describes various Oracle JCA Adapter artifacts and provides
recommendations for disaster recovery.
Artifacts on the File System Certain adapters by their nature use local or shared-storage files, for example:
■
JMS adapters utilizing WebLogic JMS with file-based persistence store: The persistence store must be synchronized with the standby site to resume processing
after failover.
■
Inbound and outbound files from either File or FTP adapters: The relevant files must be synchronized with the standby site to resume processing after failover.
Adapter configuration is maintained in the weblogic-ra.xml deployment descriptor for the ear JCA resource RAR. The file location of each weblogic-ra.xml is determined by
the administrator when the file is created, and must be replicated to the standby site.
Artifacts in the Database Adapter artifacts are generated at design time as part of the composite project. These
artifacts are stored along with the rest of the composite definition in the metadata repository.
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making domain-related configuration changes that is, adapter configuration changes and applying patches.
Oracle Data Guard should be configured for the Oracle SOA Suite database and metadata repository.
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 database must be recovered to the most recent point in time, along with the
Managed Server running the JCA adapters and the Administration Server.
2.4.9 Recommendations for Oracle Business Activity Monitoring
Oracle Business Activity Monitoring BAM provides the tools for monitoring business services and processes in the enterprise. It allows correlating of market indicators to
the actual business process and to changing business processes quickly or taking corrective actions if the business environment changes. Oracle BAM provides the
necessary tools and run-time services for creating dashboards that display real-time data inflow and define rules to send alerts under specified conditions.
Recommendations for Fusion Middleware Components 2-19
This section describes various Oracle BAM artifacts and provides recommendations for disaster recovery.
Artifacts in the Database Oracle BAM data and report metadata is stored in the Oracle BAM database that
contains Oracle BAM schemas.
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making domain-related configuration changes and applying patches.
Oracle Data Guard should be configured for the Oracle SOA Suite database containing the BAM schema and the metadata repository.
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 database must be recovered to the most recent point in time, along with the
Managed Server running Oracle BAM.
2.4.10 Recommendations for Oracle Business Process Management
The Oracle Business Process Management BPM Suite provides an integrated environment for developing, administering, and using business applications centered
around business processes. It provides a seamless integration of all stages of the application development life cycle from design-time and implementation to runtime
and application management.
The Oracle BPM Suite is layered on the Oracle SOA Suite and shares many of the same product components, including:
■
Oracle Business Rules
■
Human workflow
■
Oracle adapter framework for integration
■
SOA Composite Architecture This section describes various Oracle BPM artifacts and provides recommendations for
disaster recovery.
Artifacts on the File System BPM JMS Persistent Store BPMJMSFileStore_auto: The file-based JMS persistent
store. The persistence store must be synchronized with the standby site to resume processing after failover.
Artifacts in the Database Process definition, deployed applications, and configuration files are stored in the
Metadata Service MDS repository. Oracle BPM also uses a separate MDS partition to share projects and project templates between process analysts and process developers.
2-20 Oracle Fusion Middleware Disaster Recovery Guide
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making domain-related configuration changes and applying patches.
Oracle Data Guard should be configured for the Oracle SOA Suite database and metadata repository.
When the application tier synchronization is initiated on the storage, the standby database is also updated to be up to the same point in time. This is recommended if a
snapshot Standby database is used.
Recovery Recommendations The database must be recovered to the most recent point in time, along with the
Managed Server running the soa-infra application.
2.5 Recommendations for Oracle Identity Management
