Home > Articles > Software Development & Management

What Is the BizTalk Interoperability Framework?

The BizTalk interoperability framework defines an application model, the BizTalk Message format, and the BizTalk Document format. Microsoft and its BizTalk.org business partners manage this framework.
James Kobielus is a contributing editor for Network World and writes its popular column "Above the Cloud." He is the author of more than 150 columns, books, feature articles, and buyers' guides. This article is excerpted from his book BizTalk: Implementing Business-to-Business E-Commerce (Prentice Hall PTR, 2000, ISBN 0-13-089159-2).
Like this article? We recommend

The BizTalk interoperability framework consists of an application model. It also specifies BizTalk Document, Message, and Schema formats.

BizTalk Application Model

The BizTalk application model includes three logical "layers": the application layer, BizTalk server layer, and data communications services layer. (Note that the BizTalk specification uses the lowercase "s" to denote the BizTalk server logical layer to distinguish it from Microsoft's BizTalk Server product, which sports the uppercase "S".) These layers support transmission, processing, and receipt of BizTalk Messages.

In a BizTalk environment, line-of-business applications communicate among themselves by exchanging documents through one or more intermediate BizTalk servers. Applications and BizTalk servers may communicate over various data communications services or protocols, such as the HyperText Transfer Protocol (HTTP); File Transfer Protocol (FTP); or a message-brokering protocol, such as Microsoft Message Queue Server (MSMQ).

Under the BizTalk application model, an application is any system that fits all three of the following criteria. First, it stores and executes line-of-business data or processing logic. Second, it can generate and/or consume XML-formatted Business Documents. Third, it can communicate with a BizTalk server via a data communications service or protocol. The application may use an adapter "glue" layer to process XML and communicate with BizTalk servers. The application may support XML as one of its native file formats, or it may interface with adapter software that converts between XML and one or more of the application's native file formats.

The line-of-business application, or its BizTalk adapter, generates XML-formatted Business Documents—according to the appropriate, application-specific XML schema defined outside the BizTalk Framework. The application-adapter then wraps Business Documents and any associated binary file "attachments" with the XML "BizTags," both header and trailer, which define a "BizTalk Document" (per BizTalk schema defined in the BizTalk Framework). Then, the application submits the BizTalk Document to an originating BizTalk server.

BizTags provide BizTalk servers with document handling and routing information, acting as an "envelope" for the business information to be transmitted. They are the set of XML tags (both mandatory and optional) that are used to specify the handling of a Business Document—which is contained in a BizTalk Document, and which is in turn contained in a BizTalk Message. All BizTags are defined within standard BizTag namespaces with Uniform Resource Identifiers (URIs) derived by extension from the prefix http://schemas.biztalk.org/btf-2-0/. The BizTags are added as an XML envelope or wrapper around a Business Document by an application or BizTalk application-adapter. BizTags are processed by the BizTalk server or by other applications that facilitate the document interchange.

BizTalk servers provide various processing services to applications: validating, mapping, translating, encoding, encrypting, signing, routing, storing, forwarding, and delivering BizTalk Messages and BizTalk Documents. Any compliant BizTalk server can process any BizTag defined under BizTalk Framework 2.0. By contrast, the tags used to mark up business information within the BizTalk Message body are determined by application-specific XML document schemas. Application-specific document tags within a Business Document are not BizTags, and are generally not processed directly by the BizTalk server.

A BizTalk server receives a BizTalk Document sent by an application and then wraps this document within an electronic envelope that defines a "BizTalk Message." The envelope of a BizTalk Message—in other words, the specific non-BizTag headers and trailers used to enclose a BizTalk Document—is specific to each network transport protocol, such as HTTP, FTP, or MSMQ. Microsoft has not yet published its promised implementation guidelines for transport-specific envelopes for BizTalk Messages.

The typical end-to-end flow of a BizTalk Message consists of five principal processing steps:

  1. A commerce-relevant event occurs within an application, thereby triggering business rules that spur creation of one or more Business Documents and (optional) binary file attachments.

  2. The application, or its BizTalk adapter, transforms these Business Documents into a BizTalk Document by wrapping them with BizTags defined in the BizTalk schema (per specifications at http://www.biztalk.org/) and XML tags defined in application-specific schemas (per specifications defined at other industry schema-repository sites, such as http://www.xml.org).

  3. The originating application transmits the BizTalk Document to the originating BizTalk server.

  4. The originating BizTalk server creates a BizTalk Message by wrapping transport-specific envelope information around one or more Business Documents. The originating server uses addressing information contained in BizTags to determine the correct transport-specific destination address or addresses. The originating server then transmits the BizTalk Message to the destination BizTalk server over the appropriate transport protocol.

  5. The destination BizTalk server validates the BizTalk Message, extracts the BizTalk Document contained within, validates it, and routes it to destination applications. Destination applications extract the Business Documents and optional binary file attachments contained in BizTalk Documents. Applications then process these documents and attachments according to application-specific business rules.

BizTalk applications differ from each other in several critical respects. First, applications may differ in the set of business rules implemented at end-point applications as well as intermediate BizTalk servers. Second, they may differ in the contents, schemas, and formats of Business Documents and binary file attachments they exchange. Third, they may differ in the end-to-end workflow process parameters encoded in BizTags in their BizTalk Documents. Fourth, they may differ in the platform-specific processing context in which each application or server processes a particular BizTalk Message or Document.

Indeed, there is a broad range of implementation-specific issues that come into play when you're developing an end-to-end BizTalk application. The principal implementation-specific issues are described in the following sections.

BizTalk Server Functionality

The BizTalk Framework does not specify the precise set of services to be provided by a generic BizTalk server. The scope of server functionality depends on the particular BizTalk server vendor's implementation. However, the BizTalk Framework strongly implies that these services will be provided to end-to-end applications from a homogeneous set of BizTalk servers, such as Microsoft's BizTalk Server product.

Physical Hosting

The BizTalk Framework does not specify the physical deployment of applications and BizTalk servers. Applications and BizTalk servers usually reside on separate machines, connected over local- and wide-area networks. However, they may also run on the same machine and communicate via various protocols over its internal bus.

Transport Protocols

The BizTalk Framework does not specify the communications protocols that bind applications and BizTalk servers to each other. Applications and servers may use any data communications network or protocol to communicate among themselves.

Software Interfaces

The BizTalk Framework does not specify the software interfaces between the application, BizTalk server, and data communications layers. These interfaces depend on the application programming interfaces (APIs), programming languages, and object models supported on the platforms on which these components are deployed.

Security Mechanisms

The BizTalk Framework does not specify mechanisms for authentication, access control, encryption, tamper-proofing, or nonrepudiation on BizTalk Messages and their contents. Security on end-to-end BizTalk transactions depends on implementation-specific agreements on these issues.

Application State Information

The BizTalk Framework does not specify the way applications and BizTalk servers are supposed to define and communicate state information on in-process interchanges. State information defines the context of a particular Business Document within an end-to-end e-commerce transaction. However, BizTalk Framework 2.0 provides several BizTalk Message header fields for input of implementation-specific state information. These header fields consist of messageID, sent, state, referenceID, handle, process, and description.

Operating Environments

As noted previously, the BizTalk Framework does not specify the operating environments on which line-of-business applications, BizTalk application-adapters, and BizTalk servers run. Operating environments constrain the physical-hosting, transport-protocol, software-interface, and state-information options available to BizTalk-enabled, line-of-business applications. However, the framework strongly implies that BizTalk implementers will develop or optimize their applications to run on Windows 2000 and associated Microsoft server software, especially Internet Information Server (IIS), Commerce Server, SQL Server, Microsoft Transaction Server (MTS), and MSMQ.

Business Document Schemas

The BizTalk Framework does not specify the schema—or information model—implemented in the contents of Business Documents. Microsoft has deliberately and wisely chosen not to dictate the logical structure of application-specific or vertical-market documents. Instead, the BizTalk Framework defers to other industry initiatives to define the XML schemas of business documents. BizTalk Documents can contain documents defined in vertical-market initiatives, such as the RosettaNet program that has defined XML schemas for business documents and online catalogs supporting the information-technology industry's supply chain. Similarly, the XML/EDI group is mapping existing American National Standards Institute (ANSI) X12 transaction sets to XML schemas. Microsoft has established an industry clearinghouse at http://www.biztalk.org for others to post application-specific or vertical-market XML document schemas that can be encapsulated in BizTalk Documents and Messages.

Workflow Process Definition and Execution

The BizTalk Framework does not contain specifications for defining end-to-end workflows involving BizTalk Messages. As a result, the framework does not live up to its promise of being able to encapsulate "self-describing" workflows within any given message transmitted between trading partners. The BizTalk Framework simply defines the header syntax of individual messages and the documents contained within them. These headers contain state information that hints at a BizTalk Message's role in a larger "interchange," a term that is largely synonymous with workflow or business process.

However, the headers by themselves do not specify the end-to-end sequence of processing steps through which one or more linked BizTalk Messages is to pass. If companies wish to implement interorganizational applications involving messages passed between two or more vendors' BizTalk servers, they will have to cobble together a very implementation-specific approach to defining, executing, and tracking these workflows.

NOTE

Microsoft provides a tool and framework—the Commerce Interchange Pipeline—for defining e-commerce workflows involving a complex sequence of messages processed within a particular BizTalk server (Microsoft's own BizTalk Server product).

Event Model and Error Messages

The BizTalk Framework does not specify the event model to be shared and the error messages exchanged between BizTalk servers, BizTalk application-adapters, line-of-business applications, and data-communications interfaces. The event model should include standard alerts for a server, adapter, or application's inability to validate or process a BizTalk Message, BizTalk Document, or Business Document. The error messages should be standard XML documents that can be processed by BizTalk servers and application-adapters. Until Microsoft defines the BizTalk event model and error messages, these important features will remain implement-specific (in other words, proprietary features of Microsoft's BizTalk products and services).

Clearly, BizTalk's application model, as laid out in the BizTalk Framework 2.0 Independent Document Specification, provides only a general development framework. It is not a specification to which independent developers can write code without first addressing a broad range of implementation-specific issues. Consequently, a BizTalk application will not be easily portable to application environments other than the one to which they were written. As we've seen, Microsoft provides just such an application environment, the centerpiece of which is its BizTalk Server product.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020