Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide

Overview of Java Message Service

The Java Message Service (JMS) API is a messaging standard that allows Java EE applications and components to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous. The Sun Java System Message Queue (MQ), which implements JMS, is tightly integrated with Enterprise Server, enabling you to create components such as message-driven beans (MDBs).

MQ is integrated with Enterprise Server using a connector module, also known as a resource adapter, defined by the Java EE Connector Architecture Specification 1.5. Java EE components deployed to the Enterprise Server exchange JMS messages using the JMS provider integrated via the connector module. Creating a JMS resource in Enterprise Server creates a connector resource in the background. So, each JMS operation invokes the connector runtime and uses the MQ resource adapter in the background.

You can manage the Java Message Service through the Admin Console or the asadmin command-line utility.

Further Information

For more information on configuring JMS resources, see Chapter 4, Configuring Java Message Service Resources, in Sun GlassFish Enterprise Server 2.1 Administration Guide. For more information on JMS, see Chapter 18, Using the Java Message Service, in Sun GlassFish Enterprise Server 2.1 Developer’s Guide. For more information on connectors (resource adapters), see Chapter 12, Developing Connectors, in Sun GlassFish Enterprise Server 2.1 Developer’s Guide.

For more information about the Sun GlassFish Message Queue, see the Message Queue documentation. For general information about the JMS API, see the JMS web page