B2B Integration : A Practical Guide to Collaborative E-commerce

XML Standards for E-business 211
Continued from page 210
2 — biztalk_l is the root element of this XML document. There is
also a namespace associated with the document, which is essentially
a Universal Resource Name (URN). It indicates the location of the
schema that describes this document.
3 — 38 — The header node of the document contains delivery and
manifest as child nodes. The delivery element is required to provide
the routing/delivery information. The manifest element describes what
is being sent in this document and can include attachments.
4 — 26 Delivery element which contains message, to and from as
child nodes.
6 — Unique message ID associated with this document.
7 — TimeStamp indicating the time when the message was
sent.
8 — The subject specifying the title of the message.
10 — 17 — element which contains address and state as its sub
elements. This provides information to the sender's BizTalk server to
route the above document.
11 — Address of the receiver's BizTalk server. In our
example, we are sending the document to www.gsds.com. The address
also contains information about the action to be taken on the receiver's
server. In this example, we are causing it to execute purchase_order.jsp
on that server.
12 — An element that contains ,
and as the sub-elements. They describe how the BizTalk
server has to process this document.
18 — Same as element, but provides information about
the senders BizTalk server and the processes that will handle the
response.
19 — The response BizTalk document will be routed to
the ConfirmProcess through the mail server.
27 — 37 — An element that contains and
as sub-elements.
28 — has and as its sub-elements.
32 — 36 — An element that has , and
as the child nodes. Together they describe the attachment
Continue on page 212