EDI and Orchestrations

Abstract

Orchestrations enable complex handling of documents, either for processes that require multiple steps, or for processes that require extended exception handling capabilities or validation routines. This chapter outlines a number of scenarios in which orchestrations could be used in an EDI implementation, and it introduces a number of concepts that enable developers of BizTalk EDI solutions to support complex logic and flow, including the following:

• • Routing incoming EDI documents (and filtering): In most EDI environments, all EDI documents are received (and delivered) on the same location, often via FTP or VAN (value-added network). It is important to understand how to route different EDI document types to different objects within BizTalk (e.g., an 864 should be routed to one orchestration, whereas a document of a different type should be routed elsewhere).

• • Delivering EDI documents via orchestrations: One of the top reasons to include document delivery within an orchestration (rather than to simply use send ports) is to ensure that a document passes EDI validation in the pipeline and, if it does not, to catch the exception and notify an administrator.

• • Exception handling: One of the most important topics for any EDI solution (and integration projects in general) is exception handling. BizTalk Server 2006 provides for many ways to build robust exception handling, ensuring that the proper steps are taken when documents fail (such as notification of an administrator). This chapter outlines a generic exception handler that can be used for a variety of purposes.