Debug maps in BizTalk 2006/2006 R2 and in BizTalk 2009

This is a great feature, that in most cases overlooked, because maps can become very large, to the point that is difficult to read, very difficult to maintain and detect some problems.

For many, the ability to debug maps is a new feature in BizTalk Server 2009, because finally, it has a particular emphasis on the Menu, but that is not true, because BizTalk Server 2006 R2 or even BizTalk Server 2016 they will also have the same capability.

Debugging maps in BizTalk Server 2009

• Right-click on the map file, and now you have a new Item “Debug Map”, next to “Test Map” and “Validate Map” items

You will get the possibility to debug the actual XSLT that BizTalk generates and also the possibility to debug scripts, functoids and other custom code.

Debugging maps in BizTalk Server 2006 or 2006 R2

Visual Studio 2005 has a great feature that enables you to debug BizTalk Map:

• Right-click the BizTalk map and select “Validate Map“
• In the output window you’ll see a link to the .xsl, click on the link to bring it up in VS
• Right-click the .xsl and select “View Source“
• At that point, you can set breakpoints in your .xsl
• Then select “XML –> Debug XSLT” – at which point you’ll be able to step thru the XSLT

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community. View all posts by Sandro Pereira