IBM MQ messaging provider modes

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 API and functionality.

The IBM MQ messaging provider normal mode with restrictions uses the JMS 2.0 API, but not the new IBM MQ 8.0 features such as shared subscriptions, delayed delivery, or asynchronous send.

The IBM MQ messaging provider migration mode is based on IBM WebSphere® MQ 6.0 function and uses only features that were available in the IBM WebSphere MQ 6.0 queue manager to implement JMS. You can connect to IBM WebSphere MQ 7.0, or later, queue managers that use IBM MQ messaging provider migration mode but you cannot use any of the Version 7.0 optimizations. This mode allows connections to either of the following queue manager versions:
  1. IBM WebSphere MQ 7.0 or later, queue manager in bindings or client mode, but this mode uses only those features that were available to a IBM WebSphere MQ 6.0 queue manager.
  2. IBM WebSphere MQ 6.0 or earlier queue manager in client mode.

If you want to connect to IBM Integration Bus by using IBM MQ Enterprise Transport, use the IBM MQ messaging provider migration mode. If you use IBM MQ Real-Time Transport, the IBM MQ messaging provider 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 Rules for selecting the IBM MQ messaging provider mode.