BizTalk 2009 migration to 64-bit and the MQSC Adapter

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;


image001


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/en-us/library/aa705007(BTS.10).aspx)


The new setup was;


- BizTalk 2009 64-bit / MQ Client 6.2.5 + SSL / MQSC Adapter


We looked for information on a bunch of pages likes forums/MSDN/technet/articles and came to the following conclusion;


BizTalk 2006 MQSC adapter does not support 64-bit and can only be used in conjunction with the MQ Client version 6.0.2.5.


BizTalk 2009 MQSC Adapter has the same limitation when used with version 6.0.2.5 but does support the new version of the MQ Client (7.x).


We installed the latest version 7.1.1.2 and ran into another problem; error code AMQ9716. This was related to the usage of SSL and the new feature: certificate validation (OCSP Authentication) that was already in place in earlier versions, but was only actively refusing certificates in V7 of the MQ Client (http://www-01.ibm.com/support/docview.wss?uid=swg21399255).


A collegae of mine noticed the sentence “This was ignored before V7.0.1.0” which led hem to believe that a V7 release existed without this validation. He searched and managed to get version 7.0.0.2…


I am glad to report that this is a winning team when you want to use 64-bit in BizTalk 2009;


BizTalk 2009 64-bit / MQ Client 7.0.0.2 + SSL / MQSC Adapter


Solution: install the MQ Client version 7.0.0.2

Comments

Mukesh said…
This comment has been removed by the author.
2:56 PM
Mukesh said…
Hi Sander,

I am running into the same issue.I am now using Windows Server 2008 R2 64bit, installed MQ client 7.0.0.2, enabled Application role with all the features. When I start with Biztalk 2009 64bit installation,MQSeries Agent is grayed out. I check the component services, MQSAgent2 is created but is not running. To install MQSAgent using the wizard, I had to move bin32 files and create a bins64 folder to get MQSAgent installed. I am not sure if MQSAgent is installed correctly. Do you have any suggestions please?

Thanks
Mukesh
2:59 PM
Post a Comment

Popular posts from this blog

Azure implementation guidelines

In My post ‘ Service Bus Management ’ I pointed out a way of implementing a DTAP strategy for managing the Service Bus environment. There’s now a great post available from Microsoft which goes into more detail about other aspects of managing the Azure subscriptions and other artefacts which is quite useful when setting up your Azure environments. Follow this link to the ‘Azure Implementation Guidelines’ HTH, Sander
Read more

Focus and innovation - recap of the last 2 years

It's been a long time since my last post. Hereby a partial explanation for that, with the note that this blog will remain active for the purpose of being a resource for historical references. My IT career started with programming, and adventures within holland, as well as overseas. When I realised programming is something you can specify, I figured that providing added value is crucial for a long term career and decided to focus on process centric roles. I started with webservice integration and eventually from that to process integration using BizTalk. The great feeling when discussing high level processes and implementing solutions within days, even highly scalable and interfacing with LOB systems is great. After several years of implementing solutions like these, I started questioning if all of this work was justified by the business case, if the solution was actually contributing, if the choices had been valid. In other words, I needed to understand the choices made. When...
Read more

BizTalk Pub/sub vs Topics based routing–discussion

My colleagues and I had a brief discussion about the subject ‘Topics’ and what it brings… Do you all agree/disagree with the following statement: topic-based pub-sub messaging doesn’t really exist in BizTalk “In my opinion; I disagree, as BizTalk offers the following 'out-of-the-box' • Message Routing (f.e build in context properties like message type, trading partner, operation etc) • Content Routing (f.e. promoted properties, message inspection in orchestrations/pipelines icw orchestration logic)” My colleague Rene Brauwers Here my 2 cents…. I agree that it exists...however the current offerings in BizTalk are tightly coupled, making the usage far from perfect. When doing content based routing on custom fields (promoted properties), you will be making the solution message-coupled; Your custom message property schema is deployed, and the message filter on these fields have a direct relationship with this property schema. Making any change to this schema will g...
Read more