BizTalk Server: A Possible Evolution

A BizTalk Server “V6” release will probably adopt the .NET Framework workflow and messaging components. In general, BizTalk Server runs solutions that manage business processes that cut across multiple applications. Shown here is a possible evolution from BizTalk Server 2006 and the upcoming 2006 R2 version (top) to BizTalk Server V6 in 2009 or 2010 (bottom).

In the current BizTalk Server, developers code business processes using two engines: Orchestration, which supports long-running transactions (called orchestrations), and the Business Rules engine, which supports if-then conditional rules (e.g., rules for selecting shipping methods) that can apply to many different transaction types. The BizTalk Server messaging system interconnects applications involved in the solution, using adapter components that support the specific network protocols and data formats of the applications. The messaging system also supports a flexible many-to-many routing system (called the message box) for messages sent among applications and orchestrations.