In order to get everything working correctly to use IBM MQ Transactional together with BizTalk, you need to purchase the IBM MQ Transactional Client. Please always download the latest version of the client.

After you install the IBM WebSphere MQ Extended Transactional Client on your BizTalk Server computer, the following additional configuration steps are necessary before you can implement transactional messaging with the BizTalk Adapter for WebSphere MQ.

  • In the WebSphere MQ Server environment, give your Network Service account appropriate permissions, as described in the IBM Technote article 1223479. For security reasons, it is strongly recommended that you use the “Security Exit” so that you do not have to add “Network Service” account into the MQM group.
  • On your BizTalk Server computer, add the MQSeries XA dll to the MSDTC registry. To the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL, add the string value amqmtsxatmc.dll in the Name column and add its path to the Data column. Provide the path in the form <WebSphere MQ Client installation folder>\bin\amqmtsxatmc.dll; for example, C:\Program Files\IBM\WebSphere MQ\bin\amqmtsxatmc.dll.
  • On your BizTalk Server computer, if you are using WebSphere MQ 5.3, give your Network Service account read/write access to the @SYSTEM folder, contained in <WebSphere MQ Client installation folder>\qmgrs\@SYSTEM. (You do not have to do this if you are using WebSphere MQ 6.0 /7.0.)
  • Make sure that MSDTC is enabled on the computer on which BizTalk Server is installed and that security is configured as described in the following procedure:
  1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.
  2. In the Console Root of the Component Services Console, expand Component Services.
  3. Expand Computers.
  4. Right-click My Computer, and then click Start MSDTC.
  5. Right-click My Computer, and then click Properties.
  6. Click the MSDTC tab.
  7. Under Transaction Configuration, click Security Configuration.
  8. Under Security Settings, select the Network DTC Access and Enable XA Transactions check boxes.
  9. Click OK.
If you are using Sysplex distributor with queue sharing groups, don’t forget to activate the GROUPUR attribute on your MQ Server. The GROUPUR attribute allows XA client applications to have any in-doubt transaction recovery that may be required, performed on any member of the QSG.If an XA client application connects to a queue-sharing group (QSG) through a Sysplex it cannot guarantee which specific queue manager it connects to. Use of the GROUPUR attribute by queue managers within the QSG can enable any in-doubt transaction recovery that may be necessary to occur on any member of the QSG. Even if the queue manager to which the application was initially connected is not available, transaction recovery can take place.This feature frees the XA client application from any dependency on specific members of the QSG and thus extends the availability of the queue manager. The QSG appears to the transactional application as a single entity providing all the WebSphere MQ features and without a single queue manager point of failure.