Peter Winther is an IT architect at Volvo IT and works with information technology since 1998. He has worked with BizTalk from 2004 inside Volvo IT with BizTalk Operation and he also works with SOA technology, and integration both inside Volvo Group and for external customers.
Extract Messages from suspended instances
BizTalk 2010 and SQL 2008 R2 is the environment we have used fore this scenario.
You have problem with some integrations, 1500 suspended instances inside BizTalk and you need to send the actual messages to a customer, and then you properly do not want to manually save out this from BizTalk Administrator.
There are a lot of blogs and Internet resources pointing out vbs, powershell scripts how to do this, but I have used BizTalk Terminator to solve this kind of scenarios.
Below statement is off course not suitable for all companies and how they work, but in my company we separate developing and operation and this is the background why I wrote this article.
To gain more quality in delivery to customers, I think the BizTalk operation team should have a Software Development Kit (SDK) so the developers that create code and deliver application package and bindings to BizTalk operation must understand the infrastructure part of the delivery, often i see that developers focus is to handle functions but forget that it should run in a complex infrastructure.
When you work with BizTalk Operation you have to take care of what code and configurations you get from developers, then it is a god idea to have some kind of checklist, I searched google and I found this checklist http://seroter.wordpress.com/2007/09/04/my-biztalk-code-review-checklist/ by Richard Seroters, if you take this and then adjust it to your environment then you have a good start for a good checklist. I am going to make a more broader general checklist for BizTalk in the future and make it public.