Prepare and running Microsoft Transaction Server applications

preparing and running, client applications, preparing and running client applications, Microsoft Transaction Server (MTS), preparing client applications, running client applications" /> Prepare and running Microsoft Transaction Server applications

Home

Preparing and running Microsoft Transaction Server applications

For general information about how to develop Microsoft Transaction Server (MTS) applications that access WebSphere MQ resources, see the section on MTS in the WebSphere MQ Help Center.
To prepare an MTS application to run as a WebSphere MQ client application, do one of the following for each component of the application:

If the component uses the C language bindings for the MQI, follow the instructions in the WebSphere MQ Application Programming Guide but link the component with the library mqic32xa.lib instead of mqic32.lib.
If the component uses the WebSphere MQ C++ classes, follow the instructions in WebSphere MQ Using C++ but link the component with the library imqx23vn.lib instead of imqc23vn.lib.
If the component uses the Visual Basic language bindings for the MQI, follow the instructions in the WebSphere MQ Application Programming Guide but, when you define the Visual Basic project, type
MqType=3 in the Conditional Compilation Arguments field.
If the component uses the WebSphere MQ Automation Classes for ActiveX (MQAX), define an environment variable, GMQ_MQ_LIB, with the value
mqic32xa.dll .
We can define the environment variable from within your application, or we can define it so that its scope is system wide. However, defining it as system wide can cause any existing MQAX application, that does not define the environment variable from within the application, to behave incorrectly.

Home