Choose a messaging provider


 

+

Search Tips   |   Advanced Search

 

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:

The types of messaging providers that can be configured in WAS are not mutually exclusive:

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".

  1. 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.

  2. Choose the messaging provider:


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