Technical data

18 Using the WebLogic Messaging Bridge
18-6 Administration Guide
Note: When configuring a messaging bridge to interoperate between WebLogic
Server release 6.1 and release 5.1, then the release 5.1
resource adapter
(
jms-notran-adp51.rar) and the non-transaction adapter
(
jms-notran-adp.rar) must be deployed on the 6.1 domain running the
messaging bridge
.
For step-by-step instructions on deployment tasks using the Administration Console,
or for more information on using the auto-deployment feature, see “Deploying
Applications” on page 7-1.
Configuring the Source and Target Bridge Destinations
A messaging bridge connects two actual destinations that are mapped to bridge
destinations: a source destination from which messages are received, and a target
destination to which messages are sent. Depending on the messaging products that
need to be bridged, there are two types of bridge destinations:
n JMS Bridge Destination – For JMS messaging products, whether it is a
WebLogic JMS implementation or a third-party JMS provider, you need to
configure a
JMSBridgeDestination instance for each actual source and target
JMS destination being mapped to a messaging bridge.
n General Bridge Destination – For non-JMS messaging products, you need to
configure a generic
BridgeDestination instance for each actual source and
target destination being mapped to a messaging bridge.
Before starting the procedure in this section, refer to the “Using the Messaging Bridge
to Interoperate with Different WebLogic Server Versions and Domains” on page
18-18 for specific configuration requirements and guidelines.
Configuring JMS Bridge Destinations
A JMSBridgeDestination instance defines a unique name for the actual JMS queue
or topic destination within a WebLogic domain, the name of the resource adapter used
to communicate with the specified destination, property information to pass to the
adapter (Connection URL, Connection Factory JNDI Name, etc.), and, optionally, a
user name and password.