5. BizTalk Document Structure

[Previous] [Next]

The following is an example of a simple BizTalk Document.

 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"> <SOAP-ENV:Header> <dlv:delivery SOAP-ENV:mustUnderstand="1" xmlns:dlv="http://schemas.biztalk.org/btf-2-0/delivery" xmlns:agr="http://www.trading-agreements.org/types/"> <dlv:to> <dlv:address xsi:type="agr:department"> Book Order Department</dlv:address> </dlv:to> <dlv:from> <dlv:address xsi:type="agr:organization"> Booklovers Anonymous</dlv:address> </dlv:from> </dlv:delivery> <prop:properties SOAP-ENV:mustUnderstand="1" xmlns:prop="http://schemas.biztalk.org/btf-2-0/properties"> <prop:identity> uuid:74b9f5d0-33fb-4a81-b02b-5b760641c1d6</prop:identity> <prop:sentAt>2000-05-14T03:00:00+08:00</prop:sentAt> <prop:expiresAt>2000-05-15T04:00:00+08:00</prop:expiresAt> <prop:topic>http://electrocommerce.org/purchase_order/</prop:topic> </prop:properties> </SOAP-ENV:Header> <SOAP-ENV:Body> <po:PurchaseOrder xmlns:po="http://electrocommerce.org/purchase_order/"> <po:Title>Essential BizTalk</po:Title> </po:PurchaseOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> 

This BizTalk Document consists of a standard SOAP 1.1 message that contains the following:

  • An application-specific Business Document (in this case a book purchase order), with its own application-defined XML namespace, carried in the body of the SOAP message.
  • BizTalk-specific <delivery> and <properties> SOAP header entries, constructed using BizTags defined in standard BizTag namespaces, with schema and semantics defined in this specification.

In general, the body of the SOAP message constituting a BizTalk Document contains several related Business Documents, and the header of the SOAP message contains several BizTalk-specific (and potentially other) header entries. The use of the SOAP-ENV:mustUnderstand attribute with a value of "1" implies (in accordance with the SOAP 1.1 specification) that the destination business entity receiving this Document must understand and correctly process the header entries so attributed, or if the header entry is not understood, the processing of the Document must be terminated with failure.

All BizTags are defined within standard BizTag namespaces with URIs derived by extension from the prefix http://schemas.biztalk.org/btf-2-0/. The scope of semantic significance for the BizTag namespaces is always confined to the header of the outermost BizTalk Document. If a BizTalk Document is carried whole in the body of another BizTalk Document, the BizTags in the inner document are "dormant" and ineffective—they are treated as business data for the purposes of processing the outer Document.

It is worth noting that the <to> and <from> routing tags, described in more detail below, often use business-entity names for source and destination addressing, rather than transport addresses such as HTTP URLs. The form and interpretation of the address content is indicated by the xsi:type attribute. The BizTalk Document structure and function are independent of the transports over which the Documents are carried.



XML and SOAP Programming for BizTalk Servers
XML and SOAP Programming for BizTalk(TM) Servers (DV-MPS Programming)
ISBN: 0735611262
EAN: 2147483647
Year: 2000
Pages: 150

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net