IBM MQ messaging provider

Through the IBM® MQ messaging provider in Liberty, Java™ Message Service (JMS) messaging applications can use your IBM MQ system as an external provider of the JMS messaging resources. IBM MQ is both JMS 1.1 and JMS 2.0 specifications compliant.

You can configure IBM MQ resources for applications (for example queue connection factories) and manage messages and subscriptions that are associated with JMS destinations in Liberty. You can administer security through IBM MQ. Additional configuration might be required in IBM MQ, depending on the resources that are used by your application.

IBM MQ is characterized as follows:
  • Messaging is handled by a network of queue managers, each running in its own set of processes and having its own administration.
  • Features such as shared queues (on IBM MQ for z/OS®) and IBM MQ clustering simplify the administration and provide dynamic discovery.
  • Many IBM products and IBM partner products support IBM MQ with monitoring and control, high availability, and clustering.
  • IBM MQ clients can run within WebSphere® Application Server (JMS), or almost any other messaging environment by using various APIs.
  • IBM MQ clients can run within a wide range of environments, platforms, and operating systems that are using various APIs. Integration through the IBM MQ resource adapter provides connectivity to other Java EE systems.
Notes: The IBM MQ feature that is deployed within Liberty has the following restrictions:
  • The IBM MQ classes for Java are not supported in Liberty. They must not be used with either the IBM MQ Liberty messaging feature or with the generic JCA support. For more information, see Using WebSphere MQ Java Interfaces in J2EE/JEE Environments.
  • The IBM MQ resource adapter has a transport type of BINDINGS_THEN_CLIENT. This transport type is not supported within the IBM MQ Liberty messaging feature.
  • The Advanced Messaging Security (AMS) feature is not included in the IBM MQ Liberty messaging feature.