1 / 25

IFX and ebMS

IFX and ebMS. Avoiding “Islands of Interoperability” Specify the Document AND its Envelope. XML Documents: Minimize Assumptions about Partner. Hardware run on Operating System run under API / Language written in (OO?) Middleware Architecture deployed Physical Connection .

dexter
Download Presentation

IFX and ebMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IFX and ebMS Avoiding “Islands of Interoperability” Specify the Document AND its Envelope

  2. XML Documents:Minimize Assumptions about Partner • Hardware run on • Operating System run under • API / Language written in (OO?) • Middleware Architecture deployed • Physical Connection

  3. Heterogeneous Interoperability Sender Java On Solaris DOM Parser XML Docs Receiver C++ On Windows SAX Parser

  4. XML Interoperability:More than the Document Data Application Partner XML Document Document Infrastructure CORBA Objects have IIOP EDI Documents have a VAN IFX Documents have … ??

  5. What is XML Document Infrastructure? • No Document can be received unless its envelope is transported. • No Document can be read unless its envelope is opened. • No Document can be understood unless its “context” is known.

  6. XML Message Layers:Interoperability  All Levels XML Document Context Envelope <- Infrastructure -> Transport

  7. 1. XML Document • Industry Specific • Data Structure “pass by value” • Schema defined by Committee • Common Data Elements (Ex: Currency, Name) • Document Specific Elements (Ex: Guest, Traveler, Patient, Student, Account)

  8. 2. XML Context Layer • Message Type Determines “Context” • Session Setup / Shutdown • Request / Response (*) • Create(*):Update(*):Delete / Response • Publish / Subscribe • Asynchronous Event Notification (*) (*) Messages including Document data

  9. 3. XML Envelope Layer(s) Layered set of choices of increasing Functionality  Make not Buy

  10. Packaging: MIME Usage • XML not effective packaging candidate • XML Documents only • Requires special encoding • MIME a Winner • HTTP, SMTP are MIME-aware • FTP and other transports carry MIME • Package ANY data format • Package multiple data formats

  11. ebMS and SOAP ebMS SOAP with Attachments

  12. What is ebMS? Message Envelope (MIME) – Ex: Travel Doc ebMS Controlled Payload(s) Msg Header Operation (CRUD) Traveler Certificates Msg Security “Reservation” Document Traveler Profile Manifest Location Map JPG (Binary) Other Related Data

  13. Where is ebMS? MHS Node MHS Node Application Application ebMS

  14. XML Envelope: Outer Layer • SOAP + Attachments • Multi-hop Message Routing • Request / ACK Matching • Transport Layer Independence • Data Encoding • Multiple Payloads

  15. XML Envelope: Inner Layer • ebMS Value Adds • Multi-hop Message Tracing • Request / Response Matching • Payload Versioning • Standardized Error Reporting • Security (Authenticate, Authorize, Non-refutability) • Session Support • Guaranteed once-only Reliable Message Delivery • Automatic Message Timeouts and Resends • Disconnected Operation

  16. ebMS: Business Web Services A brief (6 slide) Overview

  17. OASIS and UN/CEFACT joint initiative • Mission: "... enable a global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other through the exchange of XML based messages" • Approach: “Standardize a layered platform-neutral infrastructure, to support real world business application use of XML technology” • ebMS Schedule: • September 1999 - begin work • June 2001 - complete version 1.0 • June 2002 - complete version 2.0

  18. ebXML Standards for B2B B2B Application Discover Core Components ebMS RegRep CPP/CPA Register B2B Application BPSS

  19. ebXML B2B Web Services and WUST EAI Web Services

  20. ebMS Vendors • XML Global • Sybase • Excelon • Web Methods • Sun Microsystems • …  Drummond Connectathons

  21. ebXML Adoption • RosettaNet (E-Commerce) • OTA (Travel Reservations) • OAG / STAR (Auto Dealers) • HL7 (Patient Records) • Others => Use ebXML infrastructure to allow concentration on XML Document Layer

  22. Open Travel Alliance (OTA) • Internet B2B Connections • Airlines / Hotels / Travel Agents / … • Distributed Database • Context Layer is CRUD .. and we’re proud of it! • Partial record locks • Strong Security (Multi-credentials) • Session AND Once-only Mode • Envelope : ebMS in V2001C • Status: V2002A and on use infrastructure • http://www.opentravel.org

  23. Conclusions Interoperability means agreement on: • Document Schemas • Document Context • Document Transaction Choreography • Document Envelope • Packaging / Routing / Transport • Security Options • Quality of Service Options And IFX “adopters” should be interoperable

  24. References • ebXML.org/specs/ebMS.pdf • www.w3.org/TR/SOAP • www.w3.org/TR/SOAP-attachments • oasis-open.org/committees/ebxml-msg/index.shtml • www.w3.org/2000/xp/Group/ • www.opentravel.org

  25. Questions?

More Related