http://www.stsc.hill.af.mil/CrossTalk/2008/01/0801DewarSchonberg.html

Advertisements

BIZTALK HOTROD

January 3, 2008

If you are at the edge of learning BizTalk Server, check out the issues that come out of this elegant resource – they call it BIZTALK HOTROD. Their 3rd issue is out recently and they had their 1st and 2nd issues released in the past.

Cool stuff – find it here.

When I was implementing the Failed Message Routing feature in BizTalk Server 2006, I got caught up into the notion that Failed Orchestration Routing may execute the same way as Failed Message Routing. Turned out that they don’t – Failed Message Routing and Failed Orchestration Routing are two different notions. BTS 2006 can only handle Failed Message Routing by enabling the flag “Enable routing for failed messages” on either a Send or a Receive port. If you ever need to handle Failed Orchestration routing, then you will need to implement the exception logic in the orchestraiton and fill in the ErrorReport promoted properties for the Error Report Orchestration to subscribe the Failed Message from an Orchestration.

Here is a good blog by Matt Meleski around this notion: http://objectsharp.com/cs/blogs/matt/archive/2006/11/01/4110.aspx