Integrating to the max...BizTalk Style

The migration from BizTalk 2006 R2 to BizTalk 2009 was a fairly smooth one, untill we faced an issue that the MQSC Adapter was not working on the 64bit environment. We tried to define a 64-bit host and run the adapter inside this host, this however did not proved to be the solution; After browsing through the MSDN pages we found that it just wasn’t going to be a 9till5 workday; “Only x86 (32-bit) Windows operating systems that are supported by BizTalk Server 2006 are supported by the MQSC Adapter. WebSphere MQ on Windows is not supported on 64-bit Windows operating systems. This means that the MQSC Adapter is not supported on either X64 (64-bit) Windows or a 32-bit BizTalk Host Instance on x64.” ( http://msdn.microsoft.com/en-us/library/aa705007(BTS.10).aspx ) The setup we had previously used was; - BizTalk 2006 R2 32-bit / MQ Client 6.2.5 + SSL / MQSC Adapter “IBM WebSphere MQ Client 5.3 with CSD10, or IBM Websphere MQ Client 6.0 with Fix Pack 6.0.1.1.” ( http://msdn.microsoft.com/e...

This article will go into detail about one of the possible approaches to connect from BizTalk to IBM MQ. Note: This is not the only or best approach and this article serves as an example for the few out there facing the problem in setting up MQSC Adapter for IBM MQ + Certificates. For starters i would like to quote a fellow BizTalker that spoke at the BTUG last week and said that in order to do SAP with BizTalk you would have to fulfill requirement #1: ‘Search for a SAP buddy’. Well although i think this will apply to other adapters as well (e.g. Dynamics AX 2009!) it is a good general rule to have someone at the other side for support. It can get tough! Overview When communicating with IBM MQ there are a number of scenarios, although i might forget some, i believe the following are possible: 1) MQ Server hosted within your BizTalk environment This would require the use of the MQSeries Adapter. 2) MQ Server hosted outside your BizTalk environment This woul...