Java Messaging Service (JMS)

WAS supports asynchronous messaging as a method of communication based on the Java Message Service (JMS) programming interface. The base JMS support enables WebSphere enterprise applications to exchange messages asynchronously with other JMS clients by using JMS destinations (queues or topics). An enterprise application can explicitly poll for messages on a destination.

Use the base support for JMS, you can build enterprise beans that use the JMS API directly to provide messaging services along with methods that implement business logic.

For more information about implementing WebSphere enterprise applications that use JMS, see the following topics:

Install WebSphere MQ for iSeries
If you want to use the embedded JMS provider, install WebSphere MQ and WebSphere MQ classes for Java and JMS. This topic describes how to install these products if you did not install them with WAS.

Overview of JMS
This topic provides an overview of asynchronous messaging using JMS support provided by WAS.

Administer JMS resources (in the Administration topic)
Use the WebSphere administrative console to administer the JMS support of WAS. For example, you can configure JMS providers and resources, and control the activity of the JMS server.

Design an application to use JMS
This topic describes things to consider when designing an enterprise application to use the JMS API directly for asynchronous messaging.

Develop an application to use JMS
This topic gives an overview of the steps needed to develop a J2EE application (servlet or enterprise bean) to use the JMS API directly for asynchronous messaging.

Develop a JMS client
This topic gives an overview of the steps needed to develop a JMS client application, based on a sample client provided with WebSphere Application Server.

Deploy an application to use JMS
This topic describes how to deploy a J2EE application to use JMS.

Message-driven beans in applications
This topic describes message-driven beans (a type of enterprise bean defined in the EJB 2.0 specification), which extend the base JMS support and the Enterprise JavaBean component model to provide automatic asynchronous messaging.