Tasks Vendor-specific client libraries | Messaging topologies: How can I use messaging? Choosing a messaging provider
WAS supports several JMS messaging providers:
- default messaging provider
This fully featured messaging provider comes free with WAS. Can handle point-to-point queues, topics in a publish-subscribe environment, and Web service endpoints.
- WebSphere MQ messaging provider
Use WebSphere MQ when we require advanced messaging facilities and options. WebSphere MQ is available on many platforms, supporting many programming languages. It is fully JMS compliant and has a large client base.
- Generic JMS provider
This is the catch-all for any external messaging providers other than WebSphere MQ. Although WAS works with any JMS-compliant messaging provider (after it is defined to WebSphere), there can only be limited admin support in WebSphere.
This approach is only recommended if we have an existing investment in a third-party messaging provider, because much greater support is available in the default messaging provider and WebSphere MQ messaging provider.
- WAS V5 default messaging provider
The WAS V5 default messaging provider is supported for migration purposes only.