The following sections provide interoperability guidelines for using the WebLogic Messaging Bridge to access JMS destinations on different releases of WebLogic Server or when accessing foreign providers:
The following interoperability guidelines apply when using the messaging bridge to access JMS destinations on different releases of WebLogic Server and in other WebLogic Server domains.
|Note:||When the messaging bridge is used to communicate between two domains running different releases of WebLogic Server, BEA recommends that the messaging bridge be configured to run on the domain using the latest release of WebLogic Server.|
Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. Therefore, make sure that:
Configuring interoperability between domains depends on the QOS:
Use the following guidelines to configure interoperability when a bridge running on a release 7.0 or higher domain must handle transactional messages (using the Exactly-once QOS) between two release 7.0 or later domains
Keep all the domains used by your process symmetric with respect to Cross Domain Security configuration and Security Interop Mode. Because both settings are set at the domain level, it is possible for a domain to be in a mixed mode, meaning the domain has both Cross Domain Security and Security Interop Mode set. For more information, see:
jms-xa-adp.rar, on the domain where the messaging bridge is running, as described in in Administration Console Online Help.
There are no special security configuration requirements for the bridge to interoperate between two releases of 7.0 or later domains. However, if you wish to provide more secure communication between domains, you can configure Cross Domain Security.
|Note:||Keep all the domains used by your process symmetric with respect to Cross Domain Security configuration—all domains use Cross Domain Security (or are on the appropriate exception lists) or none of the domains have Cross Domain Security configured. For more information, see:|
When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:
JMSBridgeDestinationinstance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:
|Note:||The messaging bridge cannot provide the “Exactly-once” quality of service when the source and target bridge destinations are located on the same resource manager (that is, when the bridge is forwarding a global transaction that is using the XA resource of the resource manager). For example, when using MQ Series, it is not possible to use the same Queue Manager for the source and target bridge destinations.|
For more information on configuring the remaining attributes for a JMS Bridge Destination, seein Administration Console Online Help.