Install and configuring a JMS provider

This topic describes the different ways that use JMS providers with WebSphere Application Server. A JMS provider enables use of the Java Message Service (JMS) and other message resources in WebSphere Application Server.

 

Overview

IBM WAS supports asynchronous messaging through the use of a JMS provider and its related messaging system. JMS providers must conform to the JMS specification version 1.1. To use message-driven beans the JMS provider must support the optional Application Server Facility (ASF) function defined within that specification, or support an inbound resource adapter as defined in the JCA specification version 1.5.

The service integration technologies of IBM WAS can act as a messaging system when you have configured a service integration bus that is accessed through the default messaging provider. This support is installed as part of WebSphere Application Server, administered through the administrative console, and is fully integrated with the WAS runtime.

WebSphere Application Server also includes support for the following JMS providers:

WebSphere MQ

Provided for use with supported versions of WebSphere MQ.

Generic

Provided for use with any 3rd party messaging system. If you want to use message-driven beans, the messaging system must support ASF.

For more information about the support for JMS providers, see JMS providers.

For more information about installing and using JMS providers, see the following topics:

 

Steps for this task (dependent on configuration)

 

See also


Installing the default messaging provider

 

See Also


JMS providers

 

Related Tasks


Installing WebSphere MQ as a JMS provider
Define a generic messaging provider