AX 2012, BizTalk 2010 and Windows Message Queue

(0) Share

Report

Posted on by Eamonn J. Casey

425

Hei,

I have a question regarding a recommendation that we use MSMQ between AX 2012 and BizTalk 2010.

I have read the documentation about how to set it up and it is relatively straight forward.

My question is: Why would you want to do this? Considering that we are going to have a highly available environment (BizTalk Group, SQL Server clusters, multiple AX insances), I don't see how putting MSMQ in there will affect either stability or performance. Is there some limitations on the AX side that it can't send/receive as fast as BizTalk?

Any links to whitepapers and recommendations would be helpful.

Thanks in advance,

Eamonn J.

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

Community Member on at

Like (0)

Report

Re: AX 2012, BizTalk 2010 and Windows Message Queue

Hi Eamonn,

It would appear that the BizTalk AIF adapter has been depreciated for the AX 2012 release. To quote from various MS articles:

"In Dynamics AX 2012, we have removed the BizTalk adapter. Instead, we have chosen to favor standards-based communications, wherever possible. Because BizTalk and AIF both are built on Windows Communication Foundation (WCF), you can simply use the standard WCF adapters to manage communications across various transports and using various protocols. Typically, synchronous communications happen through standard Web services by using the HTTP or NetTCP adapters, while asynchronous communications simply use the file system or Message Queuing (MSMQ)."

Although there is no harm in using the WCF HTTP or NetTCP approaches, I'm a big fan of queues, especially when used in a clustered environment due to the redundancy that is provided 'out of the box' and that they remove the 'point-to-point' nature of HTTP/TCP endpoints (even when behind a load-balancer).

With MSMQ, multiple BizTalk Host Instances can read and write from the same set of (clustered) MSMQ queues with no additional hardware or software requirements. Effectively decoupling your message processing / message generation processes - a sound architectural practice.

Please see msdn.microsoft.com/.../hh352300.aspx and http://blogs.msdn.com/b/aif/archive/2011/08/17/new-white-paper-for-biztalk-integration-with-aif.aspx for further information.

Rgds, Nick.

Was this reply helpful? Yes No