tag:blogger.com,1999:blog-3078460769226170088.post1367196624310309360..comments2024-02-16T03:47:56.872-08:00Comments on Kent Weare's Integration Blog: Clustering MQ Series and BizTalk Send/ReceiveKent Wearehttp://www.blogger.com/profile/12128408181333089696noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3078460769226170088.post-82783225263778638902009-06-30T05:56:21.782-07:002009-06-30T05:56:21.782-07:00Hi Kiranmv,
The adapter is installed with BizTalk...Hi Kiranmv,<br /><br />The adapter is installed with BizTalk...it is part of the base install. Go into BizTalk Admin - Platform Settings - Adapters and see if it is there.<br /><br />The MQSAgent is an opt-in install. You will find a "Checkbox" in the additional software section of the install. This is where you enable the developer tools, SSO Admin etc. In order for you to actually be able to install this agent, the install application must detect MQ Series installed.Kent Wearehttps://www.blogger.com/profile/12128408181333089696noreply@blogger.comtag:blogger.com,1999:blog-3078460769226170088.post-73146129751161422852009-06-30T03:11:44.786-07:002009-06-30T03:11:44.786-07:00Hi
Could you please let me know how to go about d...Hi <br />Could you please let me know how to go about downloading and installing the MQseries adapter for biztalk 2006.I m searching for the same and unable to find iit anywhere.kiranmvhttps://www.blogger.com/profile/14823464643796034244noreply@blogger.comtag:blogger.com,1999:blog-3078460769226170088.post-38486869124829561942009-06-29T09:04:33.517-07:002009-06-29T09:04:33.517-07:00Thanks for the feedback Ben. The main concern for...Thanks for the feedback Ben. The main concern for me around failback is during Windows Patching cycles. I didn't want to take any chances with failover's occuring and having a critial app hung up due to this issue.Kent Wearehttps://www.blogger.com/profile/12128408181333089696noreply@blogger.comtag:blogger.com,1999:blog-3078460769226170088.post-441688833041798742009-06-29T05:17:39.302-07:002009-06-29T05:17:39.302-07:00Fantastic - my previous client was the client wher...Fantastic - my previous client was the client where this problem occured and went through support and we came up with this workaround! Its still an open issue and as far as I know, it hasn't been resolved yet, but in our testing we found this workaround caused no issues (failover is an uncommon event after all).<br /><br />For the record, the kill task comes with the resource kit (we put it on the server manually).<br /><br />Also its known that you can't run MQ on a different node to MSDTC, because you can't access MQ remotely (with the standard components for .net that are in the MQ adapter). This is why you can't run MQ QMs in an active/active config on a windows cluster (if you're using this tech to get/put). There is another MQ adapter that allows you to do this though (the client based biztalk adapter for MQ; MQSC) - see <a href="http://msdn.microsoft.com/en-us/library/aa772116.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/aa772116.aspx</a>Ben Copshttps://www.blogger.com/profile/08629352950689750016noreply@blogger.com