This topic describes the different ways that you can implement a JMS provider for use with WebSphere Application Server.
Why and when to perform this task
For IBM WebSphere Application Server to support bean-managed messaging, you need to install and configure one or more JMS providers that conform to the JMS specification version 1.0.2. To use message-driven beans the JMS provider must support the Application Server Facility (ASF) function defined within that specification.
You can install and use the Embedded Messaging Server option of WebSphere Application Server, install WebSphere MQ as the JMS provider, or install another "generic" JMS provider. If you install both embedded messaging and WebSphere MQ as JMS providers, for example, WebSphere applications can use JMS resources provided by both the embedded WebSphere JMS provider and the WebSphere MQ JMS provider.
WebSphere Application Server provides default JMS support with its Embedded Messaging Server component. This function is installed with WebSphere Application Server, administered through the administrative console and managed as part of the WebSphere Application Server runtime. This function is only accessible from WebSphere Application Server Web, EJB and client containers, and is not interoperable with WebSphere MQ. If access is required to heterogeneous non-JMS applications, WebSphere MQ clustering, or other WebSphere MQ functions, you should install WebSphere Application Server without the Embedded Messaging Server component, and should install WebSphere MQ instead as the JMS provider.
The WebSphere Application Server Embedded Messaging Client is the same Java Client feature that ships with WebSphere MQ 5.3.1.
To provide the supported levels of messaging, you should apply the latest service for WebSphere Application Server and WebSphere MQ while a production application is in Quality-Assurance or Product-Validation Test.
For more information about WebSphere Application Server messaging scenarios, and the relationship between embedded messaging and WebSphere MQ, see the following articles:
You can install and configure a JMS provider in one or more of the following ways:
Note:
Note:
The preferred solution for publish/subscribe messaging with WebSphere MQ as the JMS provider is a full broker such as WebSphere MQ Event Broker. Failing this, you can install the MA0C SupportPac with 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/
Note: You cannot use the WebSphere administrative console to administer the JMS provider or its resources.
Example
This scenario starts with adding embedded messaging as the JMS provider, then optionally adding WebSphere MQ as an alternative JMS provider. Each stage summarizes the messaging functions that can be added.
You want to be able to run WebSphere applications that use the WebSphere JMS resources for both point-to-point and publish/subscribe messaging.
Besides the point-to-point and publish/subscribe messaging that uses the embedded WebSphere JMS resources (from the preceding step), you want to use WebSphere MQ Queue resources for point-to-point messaging.
For publish/subscribe messaging, you want to be able to run WebSphere applications that use the WebSphere MQ Topic resources or the embedded WebSphere Topic resources (such as those configured in preceding steps).
You can run WebSphere applications that use both the WebSphere JMS resources and WebSphere MQ JMS resources for messaging.
You can run WebSphere applications that use the WebSphere MQ JMS resources for point-to-point or (with a supported broker installed) publish/subscribe messaging.