JMS providers for clients
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 WAS, administered through the console, and is fully integrated with the WAS runtime.
WAS 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 which supports ASF.
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 version 5 Embedded Messaging system. The V5 default messaging provider can also be used with a service integration bus.
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.
The service integration bus also provides access to a default messaging provider. This is a J2EE 1.4 compliant JMS messaging provider which is fully integrated with WAS. You can use it in multiple server configurations for messaging interactions with a WebSphere MQ network.
Related tasks
Use application clients