PROVIDERVERSION migration mode
For migration mode, the IBM MQ classes for JMS use the features and algorithms similar to those that are supplied with IBM WebSphere MQ Version 6.0, such as queued publish/subscribe, selection implemented on the client side, non-multiplex channels, and polling used to implement listeners.
To connect to WebSphere Message Broker Version 6.0 or 6.1 using IBM MQ Enterprise Transport Version 6.0, we must use migration mode.
We can connect to an IBM MQ Version 8.0 queue manager using migration mode, but none of the new features of an IBM MQ classes for JMS queue manager are used, for example, read ahead or streaming. If we have an IBM MQ Version 8.0 or later client connecting to an IBM MQ Version 8.0 or later queue manager on a distributed platform, or an IBM MQ Version 8.0 or later queue manager on z/OS, then the message selection is done by the queue manager rather than on the client system.
If IBM MQ messaging provider migration mode is specified and the IBM MQ classes for JMS attempt to use any of the JMS 2.0 API, the API method call fails with the exception JMSCC5007.
Parent topic: IBM MQ messaging provider modes of operationRelated information