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)

• Installing the default messaging provider

• Using WebSphere MQ as a JMS provider. Installing WebSphere MQ as a JMS provider.

  Note:

  • We can install WebSphere MQ in addition to the default messaging provider. The preferred solution for publish/subscribe messaging with WebSphere MQ as a JMS provider is a full message broker such as WebSphere MQ Event Broker.

  • If you install WebSphere MQ as a JMS provider, use the WebSphere administrative console to administer the JMS resources provided by WebSphere MQ, such as queue connection factories. However, one cannot administer MQ security, which is administered through WebSphere MQ.

  For more information about scenarios and considerations for using WebSphere MQ with IBM WebSphere Application Server, see the White Papers and Red books provided by WebSphere MQ; for example, through the WebSphere MQ library Web page at http://www-3.ibm.com/software/ts/mqseries/library/

• Installing another JMS provider, which must conform to the JMS specification and, to use message-driven beans, support the ASF function. If you want to use a JMS provider other than the default messaging provider or WebSphere MQ, you should complete the following steps:

  1. Installing and configuring the JMS provider and its resources by using the tools and information provided with the product.

  2. Define the JMS provider to WebSphere Application Server as a generic messaging provider.

  Note: Use the WebSphere administrative console to administer JMS connection factories and destinations (within WebSphere Application Server) for a generic provider, but cannot administer the JMS provider or its resources outside of WebSphere Application Server.

 

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

 

---