Recommendations for Fusion Middleware Components 2-15
Artifacts in the Database Oracle B2B message and message state persistence are stored in the Oracle SOA Suite
database along with the partners, documents, and channels definitions. The metadata repository is used for storing Oracle B2B metadata.
Special Considerations The external FTP servers and email servers should be available on the standby site if
these adapters are used.
Synchronization Recommendations For information about Oracle B2B JMS queue synchronization and recovery, refer to
Section 2.1.1, Recommendations for Oracle WebLogic Server JMS and T-Logs. 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. 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 soa-infra application. Oracle B2B stores state information within JMS queues and the SOA run-time database, so recovering the database and the
Managed Server will ensure that the application runs normally.
2.4.6 Recommendations for Oracle Web Services Manager
Oracle Web Services Manager Oracle WSM provides a policy framework to manage and secure Web services consistently across your organization. It provides capabilities
to build, enforce, execute and monitor Web Service policies including security, WSRM, MTOM and addressing policies. Oracle Web Services Manager is made up of the
Policy Manager and the Agent.
The Policy Manager reads and writes security and management policies, including predefined and custom policies from the MDS repository. Policy Manager is a stateless
Java EE application. It exposes its capabilities through stateless session beans. Although the Policy Manager does not cache any data, the underlying MDS
infrastructure does.
Table 2–1 JMS Queues and Topics Used by Oracle B2B
JMS Artifact Name Type
JNDI Name
dist_B2BEventQueue_auto Distributed queue
jmsb2bB2BEventQueue dist_B2B_IN_QUEUE_auto
Distributed queue jmsb2bB2B_IN_QUEUE
dist_B2B_OUT_QUEUE_auto Distributed queue
jmsb2bB2B_OUT_QUEUE dist_B2BBroadcastTopic_auto
Distributed topic jmsb2bB2BBroadcastTopic
2-16 Oracle Fusion Middleware Disaster Recovery Guide
The Agent is responsible for policy enforcement, execution and gathering of run-time statistics. The agent is available on all Oracle Fusion Middleware Managed Servers
and is configured on the same server as the application which it protects. The agent consists of two pieces: the Policy Access Point PAP and the Policy Interceptor
This section describes various Oracle Web Services Manager artifacts and provides recommendations for disaster recovery.
Artifacts in the Database The MDS repository is used for storing the policies.
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 Oracle database metadata repositories. 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 soa-infra application. All policies are stored in the MDS repository, so recovering the database and the Managed Server will ensure that the
application runs normally.
2.4.7 Recommendations for Oracle User Messaging Service
