JMS provider support
Overview
WAS supports asynchronous messaging through the use of a JMS provider and its related messaging system. JMS providers must conform to the JMS specification V1.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 V1.5.
WAS supports JMS messaging using the following:
- Service integration default messaging provider
- WebSphere MQ JMS provider
- V5 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 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 WAS, administered through the console, and is fully integrated with the WAS runtime.
WebSphere MQ JMS provider
WAS also includes support for the WebSphere MQ JMS provider. This is provided for use with supported versions of WebSphere MQ.
V5 default provider
For backwards compatibility with earlier releases, WAS also includes support for the V5 default messaging provider which enables you to configure resources for use with the WAS V5 Embedded Messaging system. The V5 default messaging provider can also be used with a service integration bus.
The V5 default messaging provider is the V5 embedded WebSphere MQ provider. It is designed for use with applications that still use Version 5 resources to communicate with V5 nodes in mixed version cells that use embedded messaging.
Generic JMS provider
WAS also includes support for the generic JMS provider. This is provided for use with any third party messaging system. To use message-driven beans, the messaging system must support ASF. For additional information about connecting to WebSphere MQ, see the following topics:
Related tasks
Installing and configuring a JMS provider
Learning about messaging with WAS