Well, thanks to Chris for letting me know that ESB Guidance for BizTalk Server was added to Codeplex.
I’m actually deploying an application this week based on the Exception Management code. I changed it around a bit, but having these bits accelerated my development significantly. Now I need to find a way to upgrade to these current components!
Hello, Richard,I am very interest in your working for esb exception management.
Actually I use the esb exception component in my last EAI project.
But I just apply it very simply.
1, I collect the fault message by the esb exception component when my orchestration
occur some exceptions, and send the fault message to biztalk messagebox by direct send
port.
2, And I built a new reusable orchestration that receive the fault message which the Esb
exception component collect, then store the message in the database by sql adapter.
3, Finally, I create a web application to show the exception informations.
As my previous consider, I will throttle the exceptional instance in the web app by invoke the
TerminateInstance method in Micrsoft.BizTalk.Operations dll. But unfortunately, the instance is
inactivity the esb exception management collect.
Hope your next contribution for esb.
Thanks
Richard Seroter's Architecture Musings 
Leave a comment