Technical data

18 Using the WebLogic Messaging Bridge
18-2 Administration Guide
n WebLogic JMS with a third-party JMS product (for example, MQSeries).
n WebLogic JMS with non-JMS messaging products (only by using specialized
adapters that are not provided with WebLogic Server).
A messaging bridge consists of two destinations that are being bridged: a source
destination from which messages are received, and a target destination to which
messages are forwarded. For WebLogic JMS and third-party JMS products, a
messaging bridge communicates with source and target destinations using the resource
adapters provided with WebLogic Server. For non-JMS messaging products, a custom
adapter must be obtained from a third-party OEM vendor or by contacting BEA
Professional Services in order to access non-JMS source or target destinations.
Source and target bridge destinations can be either queues or topics. For example,
messages that are sent to a source topic or queue are automatically forwarded by the
messaging bridge to a designated target topic or queue. You can also specify a quality
of service (QOS), as well as message filters, transaction semantics, and connection
retry policies.
Once a messaging bridge is configured, it is easily managed from the Administration
Console, including temporarily suspending bridge traffic whenever necessary, tuning
the execute thread pool size to suit your application, and monitoring the status of all
your configured bridges.
Messaging Bridge Configuration Tasks
Before you can deploy a messaging bridge, you need to configure its required
components:
n “About the Bridge’s Resource Adapters” on page 18-3
n “Deploying the Bridge’s Resource Adapters” on page 18-5
n “Configuring the Source and Target Bridge Destinations” on page 18-6
n “Configuring a Messaging Bridge Instance” on page 18-12