Choose a messaging provider
For messaging between appservers, with some interaction with a WebSphere MQ system, use the default messaging provider.
To integrate WAS messaging into a predominantly WebSphere MQ network, use the WebSphere MQ messaging provider.
We can also use a third-party messaging provider.
Enterprise applications in WAS can use asynchronous messaging through services based on JMS messaging providers and their related messaging systems. These messaging providers conform to the JMS V1.1 specification.
Configure any of the following messaging providers:
- Default messaging provider (service integration)
- WebSphere MQ messaging provider
- Third-party messaging provider
The types of messaging providers that can be configured in WAS are not mutually exclusive:
- All types of provider can be configured within one cell.
- Different applications can use the same, or different, providers.
- One application can access multiple providers.
No one of these providers is necessarily better than another. The choice of provider depends on what the JMS application needs to do, and on other factors relating to the business environment and planned changes to that environment.
For backwards compatibility with earlier releases, WAS also includes support for the "V5 default messaging provider".
- Determine the environment and application requirements.
If we have to use a third-party messaging provider, or interoperate with WAS V5 resources, use the associated provider.
If the existing or planned messaging environment involves both WebSphere MQ and WAS systems, and it is not clear to you whether you should use the default messaging provider, the WebSphere MQ provider, or a mixture of the two, complete the task Choose messaging providers for a mixed environment.
- Choose the messaging provider:
- Choose the default messaging provider.
If we mainly want to use messaging between applications in WAS, perhaps with some interaction with a WebSphere MQ system, the default messaging provider is the natural choice because this provider is fully integrated with the WAS runtime environment.
See...
- Choose the WebSphere MQ messaging provider.
If the business also uses WebSphere MQ, and you want to integrate WAS messaging applications into a predominantly WebSphere MQ network, the WebSphere MQ messaging provider allows you to define resources for connecting directly to the queues in a WebSphere MQ system.
See...
- WebSphere MQ messaging provider.
- Manage messaging with the WebSphere MQ messaging provider.
- Choose a third-party messaging provider.
Use any third-party messaging provider that supports the JMS V1.1 unified connection factory. We might want to do this, for example, because of existing investments.
- To administer a third-party messaging provider, use the resource adaptor or client supplied by the third party.
We can still use the WAS admin console to administer the JMS connection factories and destinations that are within WAS, but we cannot use the admin console to administer the JMS provider itself, or any of its resources that are outside of WAS.
- To use message-driven beans (MDBs), third-party messaging providers must include Application Server Facility (ASF), an optional feature that is part of the JMS V1.1 specification, or use an inbound resource adapter that conforms to the JCA V1.5 specification.
Choose messaging providers for a mixed environment
Related concepts
Introduction: Messaging resources
Related tasks
Manage messaging with the WebSphere MQ messaging provider
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Administer activation specifications and listener ports for message-driven beans
Secure messaging
Tuning messaging
Troubleshooting messaging
Programming to use asynchronous messaging
Manage messaging with the default messaging provider
Set JMS resources for the synchronous SOAP over JMS endpoint listener