MSDN Magazine - August 2008 - (Page 65)

ror routing on the ports that transport EDI documents, these documents will be able to be routed to any BizTalk component. For example, if a trading partner were to deliver an invalid document to BizTalk rather than allowing the document to fail and remain hidden, it may be desirable to notify an administrator. This could be accomplished by enabling error routing on the port being used for EDI transport. You could then create an orchestration that subscribes to all documents containing errors. This orchestration could then include all of the logic necessary to determine the reason behind the document’s failing and notify an administrator. To route failed messages to a subscribing entity, the port where the messages are arriving or from where they’re being sent must have the Enable Routing for Failed Messages flag set. When this is set, any message that fails will be sent to the MessageBox contained in an envelope with information about why the document failed. One set of promoted properties, the ErrorReport group, will then be available to allow for routing to specific subscribers. To set up a subscriber to listen for these failed documents, simply set a filter to listen for any document on the MessageBox that had a value in the ErrorReport.ErrorType property. Say your company wants to subscribe to all failed messages that arrive from external trading partners. The initial receive shape on an orchestration could be set to listen for all documents with a value in ErrorReport.ErrorType. This would be done by dropping the receive shape at the top of the orchestration flow and setting it to subscribe to a port with a generic document type (such as System.Xml.XmlDocument). The filter on the receive shape could then be set by clicking on the Filter property of the shape and setting the Property value to ErrorReport.ErrorType and the Operator value to Exists. If the filter needed to be further refined to restrict the document BizTalk Server provides the infrastructure that enables EDI processes to be easily plugged into a service-oriented architecture. being picked up to those that specifically matched the Invoice 810 schema, for example, then the incoming port type could be swapped from the generic System.Xml.XmlDocument to the specific schema desired. I have outlined the core EDI functionality in BizTalk Server, but how does this functionality fit into a service-oriented architecture that ensures the maximum reuse of components? An EDI solution is really a series of processes that can be reused by numerous trading partners. BizTalk Server provides the infrastructure that enables these processes, and their accompanying data entities, to be easily plugged into an SOA and leveraged by a variety of other workflows and services across the enterprise. Additionally, in the context of EDI all documents can be transferred in a secure manner, are validated for content, and can be tracked. In the event of error, they can be fully recovered. If there is extensive processing that needs to take place, either through the core EDI engine or through orchestrations, state management is ensured. Because the solution is based on BizTalk Server, much of your work on orchestrations, error processing, reporting, and other elements can be leveraged across EDI trading partner relationships. For more information on this subject, see BizTalk Server 2006 R2 EDI Functionality (available at msdn.microsoft.com/library/bb226440.aspx) and BizTalk Server 2006 R2 EDI and AS2 Tutorials (at msdn.microsoft.com/ library/bb259975.aspx).  EDI and SOA Mark Beckner runs Inotek Consulting Group, LLC, specializing in technical consulting and enterprise integration infrastructures. He is the author of Pro EDI in BizTalk Server 2006 R2. msdnmagazine.com August 2008 65 http://msdn.microsoft.com/library/bb226440.aspx http://msdn.microsoft.com/library/bb259975.aspx http://msdn.microsoft.com/library/bb259975.aspx http://msdnmagazine.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - August 2008

MSDN Magazine - August 2008 Toolbox CLR Inside Out Basic Instincts Cutting Edge Patterns in Practice Data 2.0 - Expose And Consume Data In A Web Services World Biztalk EDI - Build A Robust EDI Solution With BizTalk Server Silverlight - Create Animations With XAML And Expression Blend Write On! - Create Web Apps You Can Draw On With Silverlight 2 Wicked Code - Craft Custom Controls For Silverlight 2 Team System Foundations Windows With C++ Concurrent Affairs Going Places { End Bracket }

MSDN Magazine - August 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.