Configuring and Managing the WebLogic Messaging Bridge
Interoperating with Different WebLogic Server Releases or Foreign Providers
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:
Interoperating with Different WebLogic Server Releases
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.
Naming Guidelines for WebLogic Servers and Domains
Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. Therefore, make sure that:
- WebLogic Server instances and domain names are unique.
- WebLogic JMS server names are unique name across domains.
- If a JMS file store is being used for persistent messages, the JMS file store name must be unique across domains.
Configuring Interoperability for WebLogic Domains
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
- For each server participating in the transaction, set the
Security Interoperability Mode flag according to Setting Security Interoperability Mode in Programming WebLogic JTA before rebooting.
Security Interoperability Mode is set to performance, you are not required to set domain trust between the domains.
- Configure domain trust for the all participating bridge domains.
- In all participating WebLogic Server 6.x domains, change the password for the
system user to the same value in all participating domains on the Security—>Users tab in the Administration Console. See Changing the System Password.
- Establish domain trust by setting a security credential for all domains to the same value in all participating domains. If you have participating 6.x domains, set the security credential for all domains to the same value as the
system password in all participating WebLogic Server 6.x domains.
Access Destinations In a Release 6.1 or Later Domain
Use 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.
- If a JMS file store is being used for persistent messages, the JMS file store name must be unique across WebLogic domains, as described in Naming Guidelines for WebLogic Servers and Domains.
- Make sure that security interoperability between the domains is correctly configured, as described in Configuring Interoperability for WebLogic Domains.
- Make sure that the XA connection factory is enabled for the domains by selecting the XAConnection Factory Enabled check box. See Configure connection factory transaction parameters in Administration Console Online Help.
- Deploy the transaction resource adapter,
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.
- When configuring the JMS bridge destinations, as described in Create JMS bridge destinations in Administration Console Online Help, do the following for both the source and target destinations:
- In the Adapter JNDI Name field, identify the transaction adapter's JNDI name,
- Do not enter anything in the Adapter Classpath field.
- Select a Quality Of Service of Exactly-once, as described in Configure messaging bridge instances in Administration Console Online Help.
Access Destinations In a Release 5.1 Domain
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:
- The Exactly-once QOS for transactions is not supported for WebLogic Server 5.1. For more information on the bridge QOS options, see the Attribute table in "Messaging Bridge: Configuration: General".
jms51-interop.jar file in the WL_HOME
\server\lib directory must be in the
CLASSPATH of the WebLogic Server 9.0 implementation.
- The release 5.1 resource adapter (
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.
- When configuring the JMS source and target destinations, as described in Create JMS bridge destinations in Administration Console Online Help, do the following:
In the Adapter JNDI Name field:
- For the 9.0 destination, specify the non-transaction adapter's JNDI name as
- For the 5.1 destination, specify the 5.1 adapter's JNDI name as
In the Adapter Classpath field:
- For the 9.0 destination, leave the field blank.
- For the 5.1 destination, indicate the location of the classes for the WebLogic Server 5.1 release, as well as the location of the
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:
Note: If your implementation is using a 5.1 Service Pack, the corresponding sp.jar files must also be added to the Adapter Classpath field.
- Select a Quality Of Service of Atmost-once or Duplicate-okay, as described in Configure messaging bridge instances in Administration Console Online Help.
Interoperating with Foreign Providers
When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:
- Before starting WebLogic Server:
- Supply the provider's
CLASSPATH in the WebLogic Server
- Include the
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.)
- In the
JMSBridgeDestination instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:
- Connection URL
- Initial Context Factory
- Connection Factory JNDI Name
- Destination JNDI Name
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.