BizTalk BizTalk FrameWork FrameWork 2.02.0Building on SOAP for Open Interoperable Building on SOAP for Open Interoperable Business ProtocolsBusiness Protocols

Marius RochonMarius RochonTechnical EvangelistTechnical EvangelistMicrosoft Corp.Microsoft Corp.

Web Service Web Service EnvironmentEnvironment

Internet

Legacy

UNIX

Windows

Linux

Mainframe

Web Service EnvironmentWeb Service EnvironmentNo common (programming) languageNo common (programming) languageNo common (development) cultureNo common (development) cultureNo common (component) technologyNo common (component) technologyNo assumption of mutual trustNo assumption of mutual trustEither create a universal translatorEither create a universal translator

Everyone in the universe speaks Everyone in the universe speaks EnglishEnglish

Or create a common languageOr create a common languageMust be standards basedMust be standards based

Requirements for a web Requirements for a web service Messaging service Messaging FrameworkFramework

XMLXML--based open framework for based open framework for message exchangemessage exchangeCompletely based on standardsCompletely based on standardsAgnostic to platform and implementation Agnostic to platform and implementation technologytechnologySupports multiple internet transportsSupports multiple internet transportsAddresses reliable delivery, routing, Addresses reliable delivery, routing, packaging and messagepackaging and message--level securitylevel security

BTF2 Foundation: Simple Object BTF2 Foundation: Simple Object Access Protocol (SOAP) Version 1.1Access Protocol (SOAP) Version 1.1

SOAP 1.1 is an emerging standard SOAP 1.1 is an emerging standard submitted to the W3C by submitted to the W3C by Microsoft, IBM, Microsoft, IBM, HP, Iona, Ariba, Commerce One, SAP, HP, Iona, Ariba, Commerce One, SAP, Compaq, Lotus, Compaq, Lotus, DevelopmentorDevelopmentor, , UserlandUserlandSOAP provides many features includingSOAP provides many features including

Extensible messaging protocol frameworkExtensible messaging protocol frameworkStandard data encoding styleStandard data encoding styleAn RPC usage patternAn RPC usage patternAn HTTP binding for messaging An HTTP binding for messaging andand RPCRPC

The features are independently usableThe features are independently usable

SOAP Protocols VisionSOAP Protocols Vision

Base XML technologies XML, XSD, XMLDSIG, XLINK, ..

SOAP 1.1 extensible protocol framework

SOAP 1.1Encoding

SOAP/RPC

MIMES/MIME

SOAP AsyncMessaging

BizTalk Framework 2.0

HTTPTCP SMTP FTP

SOAP/MIMEEncrypt

SignAttach

BizTalk Framework GoalsBizTalk Framework Goals

XMLXML--based open framework for based open framework for message exchangemessage exchangeCompletely based on standardsCompletely based on standardsAgnostic to platform and implementation Agnostic to platform and implementation technologytechnologySupports multiple internet transportsSupports multiple internet transportsAddresses reliable delivery, routing, Addresses reliable delivery, routing, packaging, context communication packaging, context communication messagemessage--level securitylevel security

BTF TimelineBTF Timeline3/4/99 Announced BizTalk Framework3/4/99 Announced BizTalk Framework5/29/99 Launched BizTalk.org, BTF 0.85/29/99 Launched BizTalk.org, BTF 0.811/1999 Published BTF 1.011/1999 Published BTF 1.06/12/2000: BTF2 draft sent to BTF 6/12/2000: BTF2 draft sent to BTF steering committeesteering committee6/27/2000: BTF2 draft incorporating 6/27/2000: BTF2 draft incorporating steering committee feedback publishedsteering committee feedback published8/2000: Expect publication of finalized 8/2000: Expect publication of finalized version of BTF2 with some updatesversion of BTF2 with some updates

Current Support for BTFCurrent Support for BTFCustomers Customers using BTF in their app or marketplaceusing BTF in their app or marketplace

businessenginebusinessengine.net portal.net portalcapitalstreamcapitalstream.com portal.com portalford.com siteford.com siteohioohio savings banksavings bankwulf gaertnerwulf gaertner

Partners Partners providing servers supporting BTFproviding servers supporting BTFSAP, Sequoia software, SAP, Sequoia software, Sainsbury'sSainsbury's, , DatastreamDatastream, , ViewlocityViewlocity, Neon, Neon

Competitors Competitors that are supporting or will support BTF that are supporting or will support BTF WebmethodsWebmethods, , OndisplayOndisplay, Vitria, Vitria

Support and Interop ModelSupport and Interop Model

Application

BTF CompliantMessage Server

Transport

Application

TransportNetwork

Doc AckDocAck

Doc Doc

BTF CompliantMessage Server

Source Server Destination Server

BTF2 Document BTF2 Document StructureStructure

SOAP Envelope

SOAP Header

SOAP Body

Business Documents

BTF2 Header Entries

Other Header Entries

BizTalk Framework 2.0 BizTalk Framework 2.0 Guaranteed (Exactly Once) DeliveryGuaranteed (Exactly Once) Delivery

Business processes require higher Business processes require higher reliability of message delivery than basic reliability of message delivery than basic internet transports can provide internet transports can provide Need certified delivery with fault Need certified delivery with fault tolerance and delivery receipt tolerance and delivery receipt Need to ensure the business action is Need to ensure the business action is performed exactly onceperformed exactly onceBTF2 provides a simple receipt BTF2 provides a simple receipt mechanism for reliable deliverymechanism for reliable delivery

<delivery SOAP-ENV:mustUnderstand="1“ ..xmlns:agr="http://www. agreements.org/types">

<!-- to and from left out for brevity --><deliveryReceiptRequest>

<sendTo><address xsi:type="agr:email_uri">

mailto:sender@myhost.com</address>

</sendTo><sendBy>

2000-05-14T08:00:00+08:00</sendBy>

</deliveryReceiptRequest></delivery>

BizTalk Framework 2.0 BizTalk Framework 2.0 MIME Packaging for SOAP MessagesMIME Packaging for SOAP Messages

MIME is an established IETF standardMIME is an established IETF standardMIME solves multiple problems for SOAPMIME solves multiple problems for SOAP

Packaging of attachments in native formatPackaging of attachments in native formatImages, Word/PDF documents, ..Images, Word/PDF documents, ..

Digital signaturesDigital signaturesXMLDSIG will do that in future for XML XMLDSIG will do that in future for XML fragments within a SOAP messagefragments within a SOAP message

Message level encryptionMessage level encryptionArbitrary nesting of these featuresArbitrary nesting of these features

BizTalk Framework 2.0 BizTalk Framework 2.0 SOAP Messages with AttachmentsSOAP Messages with Attachments

MIME multipart/related packages for MIME multipart/related packages for carrying attachments in native formcarrying attachments in native formAn XML insurance claim submission may An XML insurance claim submission may have attachments forhave attachments for

Facsimile of a hand signed claim formFacsimile of a hand signed claim formPicture of damaged object (e.g., car crash)Picture of damaged object (e.g., car crash)

MIME header labels for attached partsMIME header labels for attached partsAttachments can be referenced using Attachments can be referenced using URI references in SOAP messageURI references in SOAP message

Multipart/related MIME container

BTF2 messageXML Claim DocRefers to attachments

TIFF Attachment(facsimile form)

GIF Attachment(photo of crash)

Content-Location: TIFF

Content-Location: GIF

<form href=“TIFF”>

<pict href=“GIF”>

……

Actual Binary TIFF

Actual Binary GIF

BizTalk Framework 2.0 BizTalk Framework 2.0 S/MIME Based Message Level SecurityS/MIME Based Message Level Security

IETF standard (IETF standard (RFCsRFCs 2311, 2633)2311, 2633)Supports signatures and encryption for Supports signatures and encryption for messagesmessagesApplies to XML and other documentsApplies to XML and other documents

Whole documents onlyWhole documents onlyXMLDSIG almost ready for XML fragmentsXMLDSIG almost ready for XML fragments

Supported on practically all platforms in Supported on practically all platforms in standard MIME librariesstandard MIME libraries

Content-Type: multipart/signed;protocol="application/pkcs7-signature";micalg=sha1; boundary=boundary42

--boundary42 Content-Type: text/xml

This is the clear signed BTF2 message

--boundary42 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=smime.p7s

ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4…

--boundary42--

BizTalk Framework 2.0BizTalk Framework 2.0Open Routing ArchitectureOpen Routing Architecture

Business document routing often Business document routing often requires naming business entitiesrequires naming business entitiesMessaging protocols usually require Messaging protocols usually require network protocol based addressingnetwork protocol based addressingBTF2 allows routing using an extensible BTF2 allows routing using an extensible naming conventionnaming convention

Allows using, e.g., D&B’s DUNS numberAllows using, e.g., D&B’s DUNS numberAllows agreement based name resolutionAllows agreement based name resolution

<delivery SOAP-ENV:mustUnderstand="1"xmlns="http://schemas.biztalk.org/btf-2-0/delivery"xmlns:agr="http://www. agreements.org/types"><to>

<address xsi:type="agr:duns_num">99-999-9999

</address></to><from>

<address xsi:type="agr:email_uri">mailto:sender@myhost.com

</address></from>

</delivery>

BTS2000 Support for BTF2BTS2000 Support for BTF2BTS2000 BetaBTS2000 Beta

Supports 7/27 draft of BTF2Supports 7/27 draft of BTF2BTS2000 RTM BTS2000 RTM

Will supported updated final version of BTF2 Will supported updated final version of BTF2 which is due to be published by 8/2000which is due to be published by 8/2000

Key TakeawaysKey TakeawaysThe BizTalk Framework is:The BizTalk Framework is:

A framework for secure, reliable message A framework for secure, reliable message exchange. exchange. Based on public standards like XML and Based on public standards like XML and SOAP.SOAP.Is platform and transport agnostic.Is platform and transport agnostic.

Questions?Questions?