Sun Java System Application Server Enterprise Edition 8.2 Administration Guide

About JMS Resources

The JMS Provider in the Application Server

The Application Server implements the Java Message Service (JMS) API by integrating the Sun Java System Message Queue (formerly Sun ONE Message Queue) software into the Application Server. For basic JMS API administration tasks, use the Application Server Administration Console. For advanced tasks, including administering a Message Queue cluster, use the tools provided in the MQ-install-dir/imq/bin directory.

For details about administering Message Queue, see the Message Queue Administration Guide.

JMS Resources

The Java Message Service (JMS) API uses two kinds of administered objects:

These objects are created administratively, and how they are created is specific to each implementation of JMS. In the Application Server, perform the following tasks:

JMS applications use the JNDI API to access the connection factory and destination resources. A JMS application normally uses at least one connection factory and at least one destination. To learn what resources to create, study the application or consult with the application developer.

There are three types of connection factories:

There are two kinds of destinations:

The chapters on JMS in the J2EE 1.4 Tutorial provide details on these two types of communication and other aspects of JMS (see

The order in which the resources are created does not matter.

For a J2EE application, specify connection factory and destination resources in the Application Server deployment descriptors as follows:

The Relationship Between JMS Resources and Connector Resources

The Application Server implements JMS by using a system resource adapter named jmsra. When a user creates JMS resources, the Application Server automatically creates connector resources that appear under the Connectors node in the Administration Console’s tree view.

For each JMS connection factory that a user creates, the Application Server creates a connector connection pool and connector resource. For each JMS destination a user creates, the Application Server creates an admin object resource. When the user deletes the JMS resources, the Application Server automatically deletes the connector resources.

It is possible to create connector resources for the JMS system resource adapter by using the Connectors node of the Administration Console instead of the JMS Resources node. See Chapter 7, Connector Resources for details.