Geeks With Blogs
Evan Koch Musings on BizTalk Server and SQL Server April 2008 Entries
Failed Message Routing
One of the things Microsoft introduced with BizTalk 2006 is failed message routing. Prior to this, developers had to come up with custom solutions to remove failed messages from the messagebox to prevent them from accumulating. Now all one has to do is enable routing for failed messages on the receive ports and create an orchestration to consume these failed messages. When a message comes into the messagebox, BizTalk tries to find a matching subscription based on the context properties of the message. ......

Posted On Friday, April 4, 2008 9:13 PM

Inbound Maps
In one of the previous examples that talked about convoys within BizTalk, I had the following orchestration:In one of the previous examples that talked about convoys within BizTalk, I had the following orchestration: The purpose of this map within the orchestration was to receive a message that followed the Claim schema, transform it into the ClaimValidation schema and set the Status to CONTRACT VALIDATION COMPLETED. It’ll see a bit contrived, but we can move the map so that it’s called on the receive ......

Posted On Friday, April 4, 2008 8:58 PM

Parallel Convoys
Taking decoupled orchestrations one step further, we’ll use it to do multiple concurrent tasks and then associate the output from those tasks. We’ll borrow our scenario for this example from the health care industry. When a claim is submitted, there are multiple types of validation that happens (and by no means is this a comprehensive list): is this a valid contract? Is the hospital part of the network? Is the procedure performed covered? We’ll take two of those for our scenario. With decoupled orchestrations ......

Posted On Friday, April 4, 2008 8:36 PM

Copyright © Evan Koch | Powered by: GeeksWithBlogs.net