As we upgrade MQ servers in the landscape, how will this effect PI’s JMS adapters? What should we do if we have multiple MQ server versions in our landscape?
In this blog, we will take a look at some of the compatibility issues between the different releases of MQ when integrating with PI.
When using the PI technical adapters to integrate with 3rd party data sources, e.g. database and messaging systems, we must include the drivers, or libraries, of those systems in either aii_af_jmsproviderlib.sda for PI 7.0/XI 3.0 or com.sap.aii.adapter.lib.sda for PI 7.1+.
Most of the drivers for these systems are backward compatible. This means that when using the lastest driver version, we should also be able to access all previous versions of the same database or messaging system.
Unfortunately, this is not the case for IBM MQ.
Here, we have examined 3 different driver versions of MQ: 5.3, 6.0 and 7.0. Using the drivers of these different versions to access MQ server 5.3 and 7.0.
For the different releases of the MQ, different sets of drivers (client libraries or jar files) are required:
(It is possible a few of the above jar files may not be needed. We did verify which ones.)
Below are our finding when testing the different sets of drivers on a PI 7.1 system, accessing MQ 5.3 and MQ 7.0 servers. I do not believe the PI version will make any different for this test.
|MQ Driver Version||Comments|
|5.3||1||1Problem with JMS
receiver comm chan
|7.0||2||2Problem with JMS
sender comm chan
MQ6 drivers or client libraries are most suitable when multiple versions of MQ servers are used in the landscape.
If only a single version of MQ server is used, then that version’s driver or client libraries should be used.