Configuring and Managing the WebLogic Messaging Bridge
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:
Unless the Exactly-once QOS (quality of service) is required for handling two-phase transactions sent across the messaging bridge, there are no special security configuration requirements for the bridge to interoperate between two release 6.1 or later domains.
However, you must follow these steps when a bridge running on release 7.0 domain must handle transactional messages (using the Exactly-once QOS) between two release 6.1 or later domains
Security Interoperability Mode
flag according to Setting Security Interoperability Mode in Programming WebLogic JTA before rebooting. Note: When Security Interoperability Mode
is set to performance, you are not required to set domain trust between the domains.
system
user to the same value in all participating domains on the SecurityUse these guidelines when configuring a messaging bridge on a release 9.0 domain to provide "Exactly-once" transactional message communication between two release 6.1 or later domains.
Note: The Exactly-once quality of service for two-phase transactions is only supported for release 6.1 or later.
jms-xa-adp.rar
, on the 9.0 domain where the messaging bridge is running, as described in Deploy resource adaptors in Administration Console Online Help.eis.jms.WLSConnectionFactoryJNDIXA
.Note: The jms51-interop.jar
file and jms-notran-adp51.rar
file are deprecated, see "WebLogic Server 5.1 End-of-Life Announcement" in Supported Configurations.
When configuring a messaging bridge involves interoperability between WebLogic Server 9.0 and release 5.1, you must configure the following on the WebLogic Server 9.0 implementation that the bridge is running on:
jms51-interop.jar
file in the WL_HOME\server\lib
directory must be in the CLASSPATH
of the WebLogic Server 9.0 implementation.jms-notran-adp51.rar
) and the non-transaction adapter (jms-notran-adp.rar
) must be deployed on the 9.0 bridge domain, as described in Deploy resource adapters in Administration Console Online Help.eis.jms.WLSConnectionFactoryJNDINoTX
.eis.jms.WLS51ConnectionFactoryJNDINoTX
.jms51-interop.jar
file for the 9.0 release.For example, if you have WebLogic Server 5.1 GA installed in a directory named WL51_HOME and your WebLogic Server 9.0 release is installed in WL81_HOME, then set the Adapter Classpath as follows for the 5.1 destination:
WL51_HOME\classes;
WL51_HOME\lib\
weblogicaux.jar;
WL81_HOME\server\lib\jms51-interop.jar
When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:
CLASSPATH
in the WebLogic Server CLASSPATH
.PATH
of any native code required by the provider's client-side libraries in the WebLogic Server system PATH
. (This variable may vary depending on your operating system.)JMSBridgeDestination
instance 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, see Create JMS Bridge destinations in Administration Console Online Help.