Robust Error Handling in BizTalk Server Solutions

Third day of Microsoft SOA and BP Conference stared off for me with a session about robust error handling for BizTalk Server solutions by Matt Meleski. He did a general discussion first before he started some demos around error handling relying on Message Box and BizTalk framework or failed message routing to file share or SharePoint. These first demos involved error handling in BizTalk server solutions were errors could occur in places like receive location, receive pipeline, messaging failures, maps, send pipeline, send adapter. Errors were handled by using MOM or failed message routing.

Last demo he did were around errors occurring inside an orchestration and handled through compensation or scopes. Why should there be error handling inside a BizTalk Server solution, because it is something that cannot be ignored and should be planned up front. There are some resources out there in the world to achieve robust error handling like tools, books, sites and blogs.

Technorati: BizTalk Server 2006

Author: Steef-Jan Wiggers

Steef-Jan Wiggers is all in on Microsoft Azure, Integration, and Data Science. He has over 15 years’ experience in a wide variety of scenarios such as custom .NET solution development, overseeing large enterprise integrations, building web services, managing projects, designing web services, experimenting with data, SQL Server database administration, and consulting. Steef-Jan loves challenges in the Microsoft playing field combining it with his domain knowledge in energy, utility, banking, insurance, healthcare, agriculture, (local) government, bio-sciences, retail, travel, and logistics. He is very active in the community as a blogger, TechNet Wiki author, book author, and global public speaker. For these efforts, Microsoft has recognized him a Microsoft MVP for the past 8 years. View all posts by Steef-Jan Wiggers