BizTalk automates b-to-b

Today's conventional wisdom holds that XML is the key to helping businesses work together, at least from the standpoint of merging information from disparate systems. But by itself, XML can't do anything to help. Someone has to define the extensions to the XML schema, the structure that the two partners are going to use when exchanging data. Needless to say, a lot of money rides on how well you make this work, and where there's money, there's Microsoft Corp.

BizTalk Server 2000 is in some ways Microsoft's most ambitious product yet in terms of its effect on back-end operations. Most businesses that have streamlined their processes over time have done so internally with great success, but things often break down at the front door. Even the most successful EAI (enterprise application integration) or EDI (electronic data interchange) projects will have some sort of disconnect. BizTalk Server 2000 is constructed to remedy that situation by using SOAP (Simple Object Access Protocol) and XML to glue systems together electronically. It is a unique product that any business using EAI/EDI should consider.

BizTalk Server is aimed at processing business documents, such as bills of lading, invoices, and purchase orders, as secured e-mail-like messages. These functions require sophisticated features such as document tracking and once-only delivery to provide the reliability needed for business-to-business transactions.

This is where the BizTalk Framework 2.0 architecture comes to the fore, enabling the movement of BizTalk documents and messages between trading partners based on BizTags, the XML tags that define document handling. As an extension of SOAP 1.1, the BizTalk Framework 2.0 provides the mechanisms for data exchange without defining the contents -- that's what the schemas are for.

The BizTalk Framework, although agnostic regarding message transport protocols, allows BizTags to carry transport-specific information. After it receives application-generated business documents, the BizTalk Server creates BizTalk messages that contain one or more BizTalk documents, which are generated either by the BizTalk Server or by the application used to create the original business document. The BizTalk Message is then sent to the partner's BizTalk Framework-compliant server which unwraps the message and passes it on to the partner's application.

Unlike most Microsoft products, BizTalk Server 2000 is licensed per CPU, not according to the number of users. The two flavors of BizTalk Server 2000 differ only in scalability. The Enterprise Edition, which we tested, offers support for unlimited internal applications and trading partners, whereas the Standard Edition handles as many as five applications and partners.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine