Because the JMS specification does not define a wire protocol for communication between brokers and clients, each JMS provider (including Message Queue) has defined and uses its own propriety protocol. This situation has led to non-interoperability across JMS providers.
The JMS bridge service in Message Queue 4.4 closes this gap by enabling a Message Queue broker to map its destinations to destinations in external JMS providers. This mapping effectively allows the Message Queue broker to communicate with clients of the external JMS provider.
The JMS bridge service supports mapping destinations in external JMS providers that:
Are JMS 1.1 compliant
Support JNDI administrative objects
Use connection factories of type javax.jms.ConnectionFactory or javax.jms.XAConnectionFactory
For transacted mapping, support the XA interfaces as a resource manager
Many open source and commercial JMS providers meet these requirements, which makes the JMS bridge service an effective way to integrate Message Queue into an existing messaging environment that employs other JMS providers.
For more information about the JMS bridge service see:
For information about the architecture, subcomponents, and capabilities of the JMS bridge service, see JMS Bridge Service in Sun GlassFish Message Queue 4.4 Technical Overview.
For information about configuring and managing JMS bridges in a broker, see Configuring and Managing JMS Bridge Services in Sun GlassFish Message Queue 4.4 Administration Guide.