ebXML Messaging Version 3.0 Parts 1, Part 2 and AS4

Overview Part 1: Core Specification AS4 Profile OASIS Standard, October 2007 AS4 Profile OASIS Committee Specification, April 2010 Part 2: Advanced Features OASIS Committee Specification December, 2010

ebXML Messaging 2.0 & 3.0 Message Header with Business Metadata Identifies Business Partners, Transaction Semantics, Context, Agreement, Properties, Payloads Reliable Message Delivery At-Least-Once, At-Most-Once, In-Order delivery Security Digital Signature and Payload Encryption Support for Non-Repudiation of Origin & Receipt Leverages SOAP, MIME envelopes XML, EDI, multimedia payloads Multiple payloads per message Transport Protocol Mappings for HTTP and SMTP Composition with other eBusiness Components Functionality provided by ebMS, already in version 2.0 and in 3.0

ebXML Messaging Version 3.0 Part 1: Core Specification

ebXML Messaging 2.0 & 3.0 Message Header with Business Metadata Identifies Business Partners, Transaction Semantics, Context, Agreement, Properties, Payloads Reliable Message Delivery At-Least-Once, At-Most-Once, In-Order delivery Security Digital Signature and Payload Encryption Support for Non-Repudiation of Origin & Receipt Leverages SOAP, MIME envelopes XML, EDI, multimedia payloads Multiple payloads per message Transport Protocol Mappings for HTTP and SMTP Composition with other eBusiness Components Functionality provided by ebMS, already in version 2.0 and in 3.0

Further Web Services Convergence New in ebMS 3.0 Core Further Web Services Convergence SOAP 1.1 or SOAP 1.2 SOAP with Attachments or MTOM WS-Security 1.0 or 1.1 WS-Reliability 1.1 or WS- ReliableMessaging 1.1/1.2 Compatible with WS-I profiles Meets new user requirements SME endpoints, message partitioning Motivation behind ebMS3: ebMS 3.o Core was released 5 years beyond V2 release, which has seen much success, as described earlier. The technology base changed, and eBusiness practices are as well. Lower-levels of Web Services protocol stack have been standardized; much of what ebMS 2 described (reliability & security) are now ready for adoption, and ebMS 3 is much simplified by deferring to these new standards to achieve the required functionality. In addition, we have met new customer requirements to support small- to medium- size enterprises (SMEs); and for more flexibility in partitioning messages into separate, named channels. Will describe each of these, starting with WS Convergence…

New ebMS 3.0 Concepts & Features Processing Modes Parameters for capturing, expressing, sharing configuration choices, message QoS. Message Pull Feature Message Receiver is Polling the Message Sender Consumer “receives” messages by pulling them from Sender Benefit: Supports Small and Medium Size Enterprises Occasionally connected, no fixed IP address, behind firewalls Message Partition Channels Messages assigned to channels Supports priority handling Processing Modes: Explain relationship w/ CPA. Client-Only Partners  Message Pulling Selective Transfer  Message Channels (message pulling, channels, MECs, headers, message authorization, non-repudiation support, compliance with SOAP/WS/WS-I).

AS4 Profile

AS4 Profile Message packaging governed by ebMS 3.0 Support for both document push and pull message exchange choreographies Message security governed by WS-Security with added support for payload compression Support for an AS2-like business-level Non-Repudiation Receipt (MDN) Reception Awareness – “just enough” reliable messaging (similar to AS2 and ebMS 2.0)

AS4 compared to AS2 AS4 has comparable features to AS2 including: Document push message exchange patterns Support for Non-Repudiation Receipts Support for “lightweight” reliable messaging Support for common security aspects like digital signatures, encryption, and payload compression AS4 additionally supports the following features not available in AS2: Document pull message exchange pattern including support for secure access to MPCs Native support for Web Services Support for “lightweight” client implementations

ebMS3/AS4 Implementations OASIS successful use statements (2007): Axway, Fujitsu, NEC Vendor implementations Cisco, Data Applications Limited, ENEA, Flame Computing, Fujitsu, NEC Other implementations have expressed interest in interoperability testing, but have not yet been publicly announced Open Source: Holodeck http://holodeck-b2b.sourceforge.net/

Industry Endorsement RosettaNet MMS >>>>> Japan Electronics and Information Technologies Association (JEITA) http://ec.jeita.or.jp/eng/modules/contents01/index.php?id=3 HL7 Version 3 Standard: Transport Specification - ebXML http://www.hl7.org/v3ballot/html/infrastructure/transport/transport- ebxml.htm Aerospace industry in Europe http://www.edibasics.co.uk/edi-resources/messaging-protocols/index.htm OASIS Energy Interoperability TC http://www.oasis- open.org/committees/download.php/37925/energyinterop-1%200- spec-wd-12.pdf Textile, clothing, footwear industry in Europe eBIZ project http://www.ebiz-tcf.eu/

Testing and Certification Drummond Group is planning for the following upcoming testing events: A week-long “virtual” BAKEOFF ideally in early December 2010 to demonstrate AS4/ebMS3 interoperability Followed by a live BAKEOFF event at a TBD conference or expo in early 2011 A full-matrix interoperability Certification Test in 1H2011 Perhaps some of these testing events will be sponsored or co-sponsored by OASIS

ebXML Messaging 3.0 Part 2: Advanced Features OASIS ebXML Messaging TC

Multihop: ebMS Messaging Across Intermediaries

Intermediaries

Multi-hop: hub and spoke

Multi-hop: connected hubs

Multi-hop: hierarchical

Bundling, Splitting, Joining, Compression

Bundle, Split, Join, Compress Decouple “logical” from “physical” message Many small messages with same destination, submitted in a short interval, are more efficiently sent as a single ebMS SOAP message bundle A (very) big message is more effectively sent as a series of smaller message fragments Reduce data to send by using message compression Applies to large messages and to bundles Also covers (verbose) message headers

Application Scenarios Bundling High volume, non real-time transactions involving small payloads Event reporting and data synchronization Any legacy batch application Splitting Messages with large payloads, or with many payloads Compression Payloads and message headers

Features Specification concerns interoperability only Configuration parameters constrain what (not) to bundle, size/timing parameters, policy .. Allows for optimization and differentiation No impact to users: Can be handled within MSH, no change to submission/delivery Simple features that compose with other ebMS3 functionality Pull, push, reliable messaging, security …

Case Study GS1 Data Synchronization: Other case studies A sample bundle containing 23 GDSN 2.7 messages; total 306K ebMS3 eb3:UserMessage header overhead: 19K (6%) Total after bz2 compression: 13K, i.e. 4% Other case studies eCom 2.6 order (11 docs, 83K), UBL 2.0 (13 docs, 11.8K), bz2/zlib compression: worst case 8% Comparison with payload compression: Best case 14%; worst case 25% Use bundle, split and compress to “optimize” message sizes

Summary

ebMS 3.0 (and AS4) ebMS 3.0 Core Specification AS4 WS-* based WS-I profiles compliant Functional superset of ebMS 2.0 Important extensions for Small and Medium-Size businesses AS4 Profile of Core Specification Functional superset of AS2 Adds payload compression, Non-Repudiation of Receipt, Reception Awareness

Part 2: Advanced Features Intermediaries Enable SME-to-SME message exchange Bundling Support efficient high-volume message exchange Split, join, compress Support efficient transfer of very large messages (and message bundles) Variants in MEP Execution Better Pull and Sync replies (industry-specific) niche protocols: e.g. eBICS, PeSIT

ebMS 3.0 Parts 1, 2 and AS4 B2B protocol with the broadest coverage of user deployment scenarios Push, Pull and Synchronous exchanges From light-weight clients to high-end B2B gateways Point-to-point exchange and multi-hop exchanges From occasional exchanges to very high volume exchanges From small message exchanges to very large message exchanges Web Services based functionality that: Is not in any other WS-* specification Only exists in (industry) niche B2B or MFT protocols Is handled (redundantly) at the application layer

Q & A ……….

More Information ebMS Version 3.0 Part 1: Core Specification http://docs.oasis-open.org/ebxml- msg/ebms/v3.0/core/os/ AS4 Profile http://docs.oasis-open.org/ebxml- msg/ebms/v3.0/profiles/200707/ ebMS Version 3.0 Part 2: Advanced Features http://www.oasis- open.org/committees/download.php/38969/ebMS3- Part2-CD01-PR01.zip

More Information TC public page Public Review Announcement http://www.oasis-open.org/committees/ebxml-msg/ Public Review Announcement http://lists.oasis-open.org/archives/ebxml- msg/201008/msg00010.html