Message Queue 4.4 is a minor release that includes a number of feature enhancements and bug fixes. This section describes the new features included in this release:
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.
As mentioned earlier, the JMS specification does not define a wire protocol for communication between brokers and clients. The STOMP (Streaming Text Oriented Messaging Protocol) open source project at http://stomp.codehaus.org defines a simple wire protocol that clients written in any language can use to communicate with any messaging provider that supports the STOMP protocol.
Message Queue 4.4 provides support for the STOMP protocol through the STOMP bridge service. This service enables a Message Queue broker communicate with STOMP clients.
For more information about the STOMP bridge service see:
For information about the architecture and capabilities of the STOMP bridge service, see STOMP Bridge Service in Sun GlassFish Message Queue 4.4 Technical Overview.
For information about configuring and managing a STOMP bridge in a broker, see Configuring and Managing STOMP Bridge Services in Sun GlassFish Message Queue 4.4 Administration Guide.
The following additional enhancements are also provided in Message Queue 4.4:
The UMS now provides functions that use HTTP GET to offer several services:
getBrokerInfo: retrieves information about the broker.
getConfiguration: retrieves information about the UMS configuration.
debug: turns debug logging in the UMS server on and off.
ping: communicates with the broker to confirm that it is running.
For information about these new features, see Query and utility functions using HTTP GET in https://mq.dev.java.net/4.4-content/imqums/protocol.html.
For an overview of UMS, see Universal Message Service (UMS). For documentation of the UMS API, see https://mq.dev.java.net/4.4-content/imqums/protocol.html. For programming examples in several languages, see https://mq.dev.java.net/4.4-content/imqums/examples/README.html.
Message Queue is now packaged for distribution using the open source Image Packaging System (IPS), also known as the pkg(5) system. This packaging method has been added in order for Message Queue to integrate with Sun GlassFish Enterprise Server 2.1.1.
Message Queue 3.7 provided an audit logging feature that was removed in Message Queue 4.0. This feature has been reinstated in Message Queue 4.4. For information about this feature, see Audit Logging in Sun GlassFish Message Queue 4.4 Administration Guide.