Choosing a messaging provider
For messaging between application servers, perhaps with some interaction with a WebSphere® MQ system, you can use the default messaging provider. To integrate WebSphere Application Server messaging into a predominantly WebSphere MQ network, you can use the WebSphere MQ messaging provider. You can also use a third-party messaging provider. To choose the provider that is best suited to your needs, consider what the application needs to do, and the business need for the provider to integrate well with your enterprise infrastructure.
About this task
Enterprise applications in WebSphere Application Server can use asynchronous messaging through services based on Java™ Message Service (JMS) messaging providers and their related messaging systems. These messaging providers conform to the JMS Version 1.1 specification.
You can configure any of the following messaging providers:
- The default messaging provider (which uses service integration as the provider)
- The WebSphere MQ messaging provider (which uses your WebSphere MQ system as the provider)
- A third-party messaging provider (which uses another company's product as the provider)
The types of messaging providers that can be configured in WebSphere Application Server 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 your JMS application needs to do, and on other factors relating to your business environment and planned changes to that environment.