1 / 19

ebXML Message Service

ebXML Message Service. Dept of Computer Engineering Khon Kaen University. Outline. What and Why Message Service? Functional modules of MSH (Message Service Handler) Packaging ebXML SOAP Extensions Reliable messaging Security Versioning. Messaging Service Overview.

branden-shaw
Download Presentation

ebXML Message Service

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. ebXML Message Service Dept of Computer Engineering Khon Kaen University

  2. Outline • What and Why Message Service? • Functional modules of MSH (Message Service Handler) • Packaging • ebXML SOAP Extensions • Reliable messaging • Security • Versioning 168493: XML and Web Services (II/2546)

  3. Messaging Service Overview • The ebXML message service deals with transport, routing, and packaging of messages • It uses SOAP with attachment as payload envelope structure • Attachment allows transporting of not only XML data but also non-XML data such as JPG file 168493: XML and Web Services (II/2546)

  4. Message Service Overview • Supports high-level semantics needed business transactions • Security • Reliability • Runs over various communication protocols • HTTP • SMTP • FTP 168493: XML and Web Services (II/2546)

  5. Message Service Design Goals • Robust, yet basic, functionality to transfer messages between trading parties • Using various existing communication protocols • Allowing for messaging reliability, persistence, security, and extensibility • Allowing robust, yet low-cost solution 168493: XML and Web Services (II/2546)

  6. Message Service Design Goals • Support both XML-based and non XML-based business information handler • Allow vendors to add robustness and higher performance in their implementation • Scalability • Leverage existing standards 168493: XML and Web Services (II/2546)

  7. ebXML Message Structure Communication Protocol Envelope (HTTP, SMTP, etc.) SOAP with Attachments MIME Envelope Message Package MIME Part Header Container MIME Part(s) Payload(s) Payload Container(s) 168493: XML and Web Services (II/2546)

  8. ebXML Message Structure: Header Container SOAP-ENV: Envelope SOAP-ENV: Header eb:MessageHeader eb:TraceHeaderList … SOAP-ENV: Body eb:Manifest … 168493: XML and Web Services (II/2546)

  9. Message Service and SOAP • ebXML Message packaging comply with • SOAP 1.1 • SOAP Messages with Attachments • ebXML Message Service defines a set of namespace-qualified SOAP Header and Body element extensions within the SOAP Envelope 168493: XML and Web Services (II/2546)

  10. ebXML Message Envelope <SOAP-ENV:Header ….> <eb:MessageHeader …> … </eb:MessageHeader> </SOAP-ENV:Header> <SOAP-ENV:Body …> <eb:Manifest …> … </eb:Manifest> </SOAP-ENV:Body> 168493: XML and Web Services (II/2546)

  11. ebXML SOAP Extensions • SOAP Header extensions • MessageHeader • TraceHeaderList • ErrorList • Signature • Acknowledgment • Via • SOAP Body extensions • Manifest • StatusRequest • StatusResponse • DeliveryReceipt 168493: XML and Web Services (II/2546)

  12. ebXML SOAP Extensions • MessageHeader • A REQUIRED element that contains routing information for the message as well as other context information about the message • TraceHeaderList • An element that contains entries that identifies the Message Service Handler(s) that send and receive the message • Manifest • An element that points to any data present either in the Payload Container or elsewhere on the web 168493: XML and Web Services (II/2546)

  13. ebXML Message Service • ebXML message service functionality is provided by message service handler • Message Service Handlers (MSH), on behalf of applications, perform reliable and secure message delivery 168493: XML and Web Services (II/2546)

  14. MSH Node MSH Node Application ebXML and MSH Application Application ebXML Message Service 168493: XML and Web Services (II/2546)

  15. MSH Node MSH Node Application MSH Service #1: Is Remote Partner Reachable? Ping Application Pong Eb:Service & eb:Action elements  Message Type Ping: Are you Alive? Pong: Obviously! 168493: XML and Web Services (II/2546)

  16. MSH Node MSH Node Application MSH Service #2: What happened to my Message? Query Status Application Report Status Eb:Service & eb:Action elements  Message Type Query: MSH Ack received; no business response Report: Message undelivered or Response lost 168493: XML and Web Services (II/2546)

  17. Reliable Messaging • Reliability is achieved by a Receiving MSH responding to a message with an Acknowledgment message • The receiving party should receive the message once and only once • It should be able to withstand • System failure • Network failure 168493: XML and Web Services (II/2546)

  18. Reliable Messaging • A MSH that supports Reliable Messaging MUST keep messages that are sent or received reliably in persistent storage • What is a persistent storage? • The storage in which data is still there after a system failure or interruption • Things to be maintained in persistent storage • MessageId • Complete message (recommendation) • Time the message was received • Complete response message 168493: XML and Web Services (II/2546)

  19. Resending Unacknowledged Messages Party A MSH Party B Application Party A Application Party B MSH Data Message Acknowledgment Data Ack. lost Msg. lost Message Message Acknowledgment Ignore Duplicate 168493: XML and Web Services (II/2546)

More Related