WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

JMS provider support

This topic provides an overview of the support for JMS providers by WebSphere Application Server.

Overview

WebSphere Application Server 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.

WebSphere Application Server supports JMS messaging using the following:
  • Service integration default messaging provider
  • WebSphere MQ JMS provider
  • Version 5 default provider
  • Generic JMS provider

WebSphere applications can use messaging resources provided by any of these JMS providers. However the choice of provider is most often dictated by requirements to use or integrate with an existing messaging system. For example, you may already have a messaging infrastructure based on WebSphere MQ. In this case you may either connect directly using the included support for WebSphere MQ as a JMS provider, or configure a service integration bus with links to a WebSphere MQ network and then access the bus through the default messaging provider.

Service integration default provider

The service integration technologies of WebSphere Application Server 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 WebSphere Application Server runtime.

WebSphere MQ JMS provider

WebSphere Application Server also includes support for the WebSphere MQ JMS provider. This is provided for use with supported versions of WebSphere MQ.

Version 5 default provider

For backwards compatibility with earlier releases, WebSphere Application Server also includes support for the Version 5 default messaging provider which enables you to configure resources for use with the WebSphere Application Server Version 5 Embedded Messaging system. The Version 5 default messaging provider can also be used with a service integration bus.

The Version 5 default messaging provider is the Version 5 embedded WebSphere MQ provider. It is designed for use with applications that still use Version 5 resources to communicate with Version 5 nodes in mixed version cells that use embedded messaging.

Generic JMS provider

WebSphere Application Server also includes support for the generic JMS provider. This is provided for use with any third party messaging system. If you want to use message-driven beans, the messaging system must support ASF.




Related tasks
Installing and configuring a JMS provider
Learning about messaging with WebSphere Application Server
Reference topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cmj_jmsp.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)