WAS v8.5 > End-to-end paths > Messaging resourcesChoose a messaging provider
For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, we can use the default messaging provider. To integrate WAS messaging into a predominantly WebSphere MQ network, we can use the WebSphere MQ messaging provider. We can also use a third-party messaging provider.
Different applications can use the same, or different, providers. One application can access multiple providers.
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.
- Determine the environment and application requirements.
- Choose the messaging provider:
- Default messaging provider
- WebSphere MQ messaging provider
This allows you to define resources for connecting directly to the queues in a WebSphere MQ system. See:
- Third-party messaging provider that supports the JMS v1.1 unified connection factory.
Use the resource adaptor or client supplied by the third party. We can still use the dmgr console to administer the JMS connection factories and destinations that are within WAS, but we cannot use the dmgr console to administer the JMS provider itself, or any of its resources that are outside of WAS.
To use 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 or 1.6 specification.
See:
Related concepts:
Choose messaging providers for a mixed environment
Introduction: Messaging resources
Manage messaging with the WebSphere MQ messaging provider
Manage messaging with a third-party messaging provider
Manage message-driven beans
Secure messaging
Tune messaging
Troubleshooting messaging
Programming to use asynchronous messaging
Manage messaging with the default messaging provider
Configure JMS resources for the synchronous SOAP over JMS endpoint listener