This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
JMS Modules are basically like containers that hold the JMS System Resources which include queues, topics, connection factories, templates, destination keys, quota, distributed queues, distributed topics.
A WebLogic messaging bridge is a forwarding mechanism between any two messaging products. It facilitates the message flow between two separate implementations of WebLogic JMS, or between WebLogic JMS and a another messaging product like IBM MQ Series.
You can use the Foreign JMS Feature of WebLogic Server to establish a connection between weblogic and WebSphere MQ.
Below is a very good read about the configuration.
The major difference between the two approaches primarily is the way they behave.
With Foreign JMS Server, your applications act as direct clients of the remote JMS Server by looking upto the Connection Factories and JMS Destinations from a local domain to remote domain / third party JMS Provider.
One the other hand Message Bridge behaves like a Store and Forward Agent. A message bridge creates a pipe between a destination on the local JMS server, and another on the remote JMS server, so that any messages that are sent to the source destination are automatically forwarded to the target destination. In other words, your applications can indirectly interact with the remote JMS server through the configured message bridge.
Foreign JMS Server provides some additional benefits:
Since the Foreign Destinations are mapped to WebLogic JNDI tree, any message-driven bean (MDB) that you deploy to the server can simply reference the remote destination using its local JNDI name.
1.It suppots interoperability and can be used between any two JMS implementaions.One with JMS weblogic and second can be any third party JMS Provider.supports the connectitivyt between any two versions of weblogic.
2.It uses two adapters whichy we need to configure while creating the source and target destinations.
One is XA based adapter which ensures exact-once delivery and eliminates duplicates.
second is JNDInoTX which will be used for at-least once delivery.
SAF on the other hand will be used in cases where there is possibility of network related issues and unavailability problems.SAF ensures guaranteed delivery as it stores the message on the local queue.
one area where i am confused is ,does JMS Bridge not store messages when the destination is not available?IF it stores,what is introduced as part of SAF feature?