How can I enable the extended transactional client in MQ v7.5?
How can I enable the extended transactional client in MQ v7.5?
In the MQ v7.5 edition of the WebSphere MQ classes for JMS, the Extended Transactional functionality is provided by the same JAR files that provide the rest of the JMS functionality.
To enable the extended transactional functionality, the only JAR file that you must add to the CLASSPATH is com.ibm.mqjms.jar. The META-INF/MANIFEST.MF file in this JAR file contains a Class-Path entry that pulls in all the other required JAR files. All required JAR files must be in the same location as the com.ibm.mqjms.jar file, as is the case for the supported configuration of a WebSphere MQ client/server installation.
Per the MQ V7.5 announcement letter, IBM now includes the MQ extended transactional client feature in the WebSphere MQ V7.1 and WebSphere MQ V7.0 clients as well. However, unlike WebSphere MQ V7.5 and later, the extended transactional client feature is split out into a separate installable component (e.g. the mqm.txclient.rte LPP on AIX, the MQSeriesTXClient RPM on Linux, and so on).
This means that applying a fix pack to an existing WebSphere MQ V7.1 or V7.0 client will not automatically enable the extended transactional client feature. You must install the extended transactional client component from the latest MQ Client SupportPac (MQC7 or MQC71) or from MQ server installation files:
MQC71 - WebSphere MQ V7.1 Client
MQC7 - WebSphere MQ V7.0 Client
If you upgrade to the WebSphere MQ V7.5 or IBM MQ V8.0 client, the extended transaction client is automatically included, with no need to install any components other than the MQ client itself: