Integration Server 11.1 | Integration Server Administrator's Guide | Configuring Integration Server for JMS Messaging | Supported JMS Providers
 
Supported JMS Providers
 
Using IBM webMethods Universal Messaging as the JMS Provider
Adding Third Party JMS Provider Client Libraries to Integration Server Classpath
Considerations and Example Configuration Information for Third-Party JMS Providers
Integration Server is certified for use with the JMS providers available from IBM, Universal Messaging and IBM webMethods Broker, and third party JMS providers.
The following table identifies the versions of Universal Messaging and IBM webMethods Broker that interoperate with Integration Server version 11.1.
JMS Provider
Versions
IBM webMethods Universal Messaging
10.3 with Universal Messaging 10.3 fix 26 applied.
10.5 with Universal Messaging 10.5 fix 12 applied.
10.7 and higher
IBM webMethods Broker
6.5 and higher
IBM webMethods Broker is deprecated.
Integration Server has been tested with the following JMS 1.1 providers:
JMS Provider
RabbitMQ and Azure Service Bus over AMQP
Apache ActiveMQ Classic
Hornet MQ (formerly JBoss Messaging)
IBM MQ
Oracle Streams Advanced Queuing (AQ)
Solace PubSub+
SonicMQ
WebLogic
WebSphere Application Server
IBM has tested Integration Server with at least one version of the above JMS 1.1 providers. IBM will support additional versions of these JMS providers when the following criteria are met:
*The JMS provider and client libraries are supported by their vendor. That is, they are not considered End-of-Support (EOS).
*The JMS provider and client libraries are certified to run with the same JVM used by the Integration Server.
*The JMS client libraries do not include or depend on any classes that conflict with the classes in the Integration Server or in the IBM shared directory (e.g., common/lib).
*IBM supports features listed in the JMS 1.1 specification only. Proprietary features offered by 3rd party providers are not supported. JMS 2.0 features are not supported.
*Additional requirements, restrictions, and considerations are listed on a per provider basis in Adding Third Party JMS Provider Client Libraries to Integration Server Classpath.
For information about adding JMS provider libraries to the Integration Server classpath, see Adding Third Party JMS Provider Client Libraries to Integration Server Classpath.