IBM MQ messaging provider

The IBM® MQ messaging provider has three modes of operation: normal mode, normal mode with restrictions, and migration mode.

The IBM MQ messaging provider has three modes of operation:
  • IBM MQ messaging provider normal mode
  • IBM MQ messaging provider normal mode with restrictions
  • IBM MQ messaging provider migration mode
The IBM MQ messaging provider normal mode uses all the features of an IBM MQ queue manager to implement JMS. This mode is optimized to use the JMS 2.0[MQ 9.3.0 Jun 2022][MQ 9.3.0 Jun 2022][Jakarta Messaging 3.0] or Jakarta Messaging 3.0 API and functionality.
If:
  • The client specifies a provider version of 6 on a ConnectionFactory, the client behaves in a way compatible with the client provided with IBM WebSphere® MQ 6.0. Only JMS 1.1 and JMS 2 interfaces are supported but some JMS 2 functionality, such as shared subscriptions, delivery delay and asynchronous send, is disabled. There is no connection sharing.
  • The client specifies a provider version of 7 on a ConnectionFactory, both JMS 1.1 and JMS 2 interfaces are fully supported.
  • No provider version is specified, an attempt is made to connect with provider version 7. If this fails, a further attempt is made with provider version 6.

If you want to connect to IBM Integration Bus by using IBM MQ Enterprise Transport, use the migration mode. If you use IBM MQ Real-Time Transport, the migration mode is automatically selected because you have explicitly selected properties in the connection factory object. Connection to IBM Integration Bus using the IBM MQ Enterprise Transport follows the general rules for mode selection that is described in Configuring the JMS PROVIDERVERSION property.