How to Configure the Messaging Bridge Between Two Uniform Distributed Destinations
(Doc ID 1235233.1)
Last updated on SEPTEMBER 03, 2020
Applies to:Oracle WebLogic Server - Version 8.1 and later
Information in this document applies to any platform.
***Checked for relevance on 7-Feb-2013***
There is a small and often overlooked entry in the documentation that highlights that configuring a messaging bridge between two domains is not as straightforward as you would think. In the current WebLogic Server documentation it is given here, but it applies to WLS 8.1 and later.
A. Yes, the messaging bridge can send to and receive from distributed destinations. Oracle recommends the following configurations:
- If the source is distributed destination, the bridge is pinned to one of the members when it connects to the destination. It stays connected only to that member until it reconnects. The bridge does not receive messages from the other members of the distributed destination. Therefore, the best practice is to configure one bridge for each member of a distributed destinations using the member's JNDIName.
- If the target is a distributed destination, the best practice is to send to the distributed destination using the distributed destination's JNDIName and disable server affinity. This allows the distributed destination to load balance incoming messages.
This small entry fixes many messaging bridge issues, but it does mean that the messaging bridge configuration is extremely complex in systems which have many distributed destinations over many servers, as the number of messaging bridges required can grow exponentially. This is why SAF is easier to configure, as you simply need to introduce a SAF agent for each server, although it has it own issues as it's relatively untested.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document