Install a JMS provider
Overview
WAS supports asynchronous messaging
WAS itself can act as a default messaging provider if a service integration bus is configured.
WAS includes the following JMS providers...
WebSphere default messaging provider Based on WebSphere MQ messaging. WebSphere v5 default messaging provider Identical to the v5 default provider. Only the name has changed. Provides backwards compatibility. WAS v6 supports a WAS v5 emulation mode for applications running in a mixed cell in WAS v5.
WebSphere MQ messaging provider Supports the JMS 1.1 unified connection factory. For publish/subscribe messaging, IBM recommends using WebSphere MQ Event Broker.
Security is administered through WebSphere MQ.
Generic messaging provider. Supports the JMS 1.1 unified connection factory. Allows you to use other, arbitrary JMS providers. You can use the console to administer JMS connection factories and destinations, but cannot administer the JMS provider or its resources outside of WAS.
To use message-driven beans, JMS providers must include either...
- Application Server Facility (ASF)
- Inbound resource adapter JCA 1.5
Procedure
- Install the default messaging provider
- Install WebSphere MQ as a JMS provider
- Define a generic messaging provider
- JMS providers collection
- Select JMS resource provider
- Activation specification collection
- Connection factory collection
- Queue connection factory collection
- Queue collection
- Topic connection factory collection
- Topic collection
Related concepts
WebSphere MQ library Web page
JMS provider support
Install the default messaging provider
Install WebSphere MQ as a JMS provider
Install WebSphere MQ as a JMS provider
Define a generic messaging provider
Install the default messaging provider
JMS providers collection
Select JMS resource provider
Activation specification collection
Connection factory collection
Queue connection factory collection
Queue collection
Topic connection factory collection
Topic collection