Technical data

18 Using the WebLogic Messaging Bridge
18-18 Administration Guide
Using the Messaging Bridge to Interoperate
with Different WebLogic Server Versions
and Domains
The following interoperability guidelines apply when using the messaging bridge to
access JMS destinations in different releases of WebLogic Server and in other
WebLogic Server domains.
n “Naming Guidelines for WebLogic Servers and Domains” on page 18-18
n “Enabling Security Interoperability for WebLogic Domains” on page 18-19
n “Using the Messaging Bridge To Access Destinations In a Release 6.1 or Later
Domain” on page 18-20
n “Using the Messaging Bridging To Access Destinations In a Release 6.0
Domain” on page 18-21
n “Using the Messaging Bridging To Access Destinations In a Release 5.1
Domain” on page 18-22
Note: When the messaging bridge is used to communicate between two domains
running different releases of Weblogic Server, a best-practice
recommendation is for the messaging bridge to 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:
n WebLogic Server instances and domain names are unique.
n WebLogic JMS server names are unique name across domains.
n All JMS connection factories targeted to servers in a cluster are uniquely named.