Java Message Service providers for clients
Client applications can use messaging resources from three main types of Java Message Service (JMS) providers in WebSphere® Application Server: The WebSphere Application Server default messaging provider (which uses service integration as the provider), the IBM MQ messaging provider (which uses your IBM MQ system as the provider) and third-party messaging providers (which use another company's product as the provider).
- Default messaging provider
- If you mainly want to use messaging between applications in WebSphere Application Server, perhaps with some interaction with a IBM MQ system, the default messaging provider is the natural choice. This provider is based on service integration technologies and is fully integrated with the WebSphere Application Server runtime environment.
- IBM MQ messaging provider
- If your business also uses IBM MQ, and you want to integrate WebSphere Application Server messaging applications into a predominately IBM MQ network, choose the IBM MQ messaging provider, which allows you to define resources for connecting to any queue manager on the IBM MQ network.
- Third-party messaging provider
- You can configure any third-party messaging provider that supports the JMS Version 1.1 unified connection factory. You might want to do this, for example, because of existing investments.
WebSphere applications can use messaging resources provided by any of these JMS providers. However the choice of provider is most often dictated by requirements to use or integrate with an existing messaging system. For example, you may already have a messaging infrastructure based on IBM MQ. In this case you may either connect directly using the included support for IBM MQ as a JMS provider, or configure a service integration bus with links to a IBM MQ network and then access the bus through the default messaging provider.