Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 936125 - Last Review: February 2, 2011 - Revision: 3.0
How to provide high availability for the MQSAgent COM+ application or for the MQSAgent2 COM+ application in a clustered environment
Consider the following scenario. In Microsoft BizTalk Server, you use the BizTalk Adapter for MQSeries adapter to connect to a clustered IBM WebSphere MQ Server-based server. The clustered IBM WebSphere MQ Server-based server hosts the MQSAgent Microsoft COM+ application or the MQSAgent2 COM+ application. In this scenario, you should not provide high availability by clustering the MQSAgent COM+ application or the MQSAgent2 COM+ application.
Note In BizTalk Server 2006 and later versions, the MQSAgent COM+ application is named the MQSAgent2 COM+ application.
To provide high availability for the MQSAgent COM+ application or for the MQSAgent2 COM+ application in a clustered environment, you must install the COM+ application locally on each cluster node. Do not cluster this component. If the COM+ application stops for any reason, the next call to the COM+ application from BizTalk Server automatically restarts the COM+ application. This behavior makes sure that you provide high availability without clustering this component.
For more information about a known issue that occurs when you use the MQSeries adapter in a clustered environment , click the following article number to view the article in the Microsoft Knowledge Base:
893059Â
(http://kbalertz.com/Feedback.aspx?kbNumber=893059/
)
The BizTalk Server Adapter for MQSeries version 2.0 no longer retrieves messages from a clustered MQSeries queue manager when the queue manager fails over to a different cluster node
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
APPLIES TO
- Microsoft BizTalk Server Branch 2010
- Microsoft BizTalk Server Developer 2010
- Microsoft BizTalk Server Enterprise 2010
- Microsoft BizTalk Server Standard 2010
- Microsoft BizTalk Server 2009 Branch
- Microsoft BizTalk Server 2009 Developer
- Microsoft BizTalk Server 2009 Enterprise
- Microsoft BizTalk Server 2009 Standard
- Microsoft BizTalk Server 2006 R2 Branch Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate