1. ebXML Messaging Version 3.0 Part 1, Part 2 and AS4
OASIS Committee Note Draft
OASIS ebXML Messaging TC
Copyright © OASIS® All Rights Reserved. This document is a Committee Note Draft.
A Committee Note Draft is Non-Standards Track Work Product.
The patent provisions of the OASIS IPR Policy do not apply to this document.

2. Overview Part 1: Core Specification – Summary AS4 – Introduction
Part 2: Advanced Features – Overview and examples

3. ebXML Messaging 2.0 & 3.0 High Level Capabilities
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

4. ebXML Messaging Version 3.0 Part 1: Core Specification

5. New ebMS 3.0 Concepts & Features
Processing Modes
Parameters for capturing and expressing configuration choices (Message Exchange, Reliability, Security etc.).
Message Pull Feature
Message Receiver Polls 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).

7. AS4 Profile

8. AS4 – The lightweight solution
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)
Suitable for SME/lightweight clients

9. 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:
Message pull operation including support for secure access to Message Processing Channels
Native support for Web Services
Support for “lightweight” client implementations

10. ebMS3/AS4 Implementations
Known implementations
Axway, Fujitsu, NEC, Cisco, Data Applications Limited, ENEA, Flame Computing
Other implementations have expressed interest in interoperability testing (scheduled for 2011).
Open Source: Holodeck

11. Industry Endorsement RosettaNet MMS
Services/tabid/474/Default.aspx
Japan Electronics and Information Technologies Association (JEITA)
HL7 Version 3 Standard: Transport Specification - ebXML
Aerospace industry in Europe
OASIS Energy Interoperability TC
1%200-spec-wd-12.pdf
Textile, clothing, footwear industry in Europe
eBIZ project

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

13. Multihop: ebMS Messaging Across Intermediaries

14. Intermediary Cloud No direct connection between endpoints
End to end secure, reliable routing of messages across the Cloud
Enables connections (store & forward) between two light clients

15. Multi-hop: hub and spoke

16. Multi-hop: Inter-connected hubs

17. Multi-hop: hierarchical

18. Bundling, Splitting, Joining, Compression

19. Bundle, Split, 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 message headers
Composes well with multi-hop intermediary features

20. 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

21. Compression Case Studies
Case Study 1 : GS1 Data Synchronization - Sample bundle containing 23 GDSN 2.7 messages
Without Compression
Total size of messages
306K
ebMS eb3:UserMessage header overhead
19K (6%)
With Compression
Total after bz2 compression
13K (4%)
Case Study 2/3: eCom 2.6 order & UBL
Without Compression
2.6 order (11 docs)
83K
UBL 2.0 (13 docs)
11.8K
With Compression
Total after bz2/zlib compression
8% (worst case)
Comparison with payload compression:
Best case 14%; worst case 25%
Use bundle, split and compress to “optimize” message sizes

22. Summary

23. 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

24. Part 2: Advanced Features
Intermediaries
Enables SME-to-SME message exchange across I-Cloud
Supports flexible and scalable topologies
Bundling
Support efficient high-volume message exchange
Split, join, compress
Support efficient transfer of very large messages (and message bundles)
(industry-specific) niche protocols: e.g. eBICS, PeSIT

25. 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

26. Q & A
……….

27. Transparent Multihop End-to-end Business Agreements
Service, action, identification, document schemas
End-to-end Security
Non-repudiation of origin and receipt
Confidentiality
End-to-end Reliability
Retries, acknowledgments
ebMS intermediaries interconnect the I-Cloud
Service, action, identification, content schemas
Routing
Based on Business Identifiers and Services
Storage
Store-and-forward (push), store-and-collect (pull)
Receiver
Sender
Inter-hop Configuration within the I-Cloud
Transport Protocol Binding (HTTP, SMTP)
Transport Security (SSL/TLS)
Transport Channel Binding (Push, Pull)
Store-and-forward or streaming
Point-to-point Techical Configuration for Edge Hops
Transport Protocol Binding (HTTP, SMTP)
Transport Security (SSL/TLS)
Transport Channel Binding (Push, Pull)

28. Implementation Flexibility
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 …
Backup

29. More Information ebMS Version 3.0 Part 1: Core Specification
AS4 Profile
ebMS Version 3.0 Part 2: Advanced Features
Part2-CD01-PR01.zip
TC public page
Public Review Announcement
msg/201008/msg00010.html

30. Contributors
The following members of the ebXML Messaging Services TC contributed to this Committee Note Draft:
Timothy Bennett, Drummond Group
Jacques Durand, Fujitsu
Sander Fieten, Individual Member
Ian Jones, BTplc
Dale Moberg, Axway Inc.
Makesh Rao, Cisco
Pim van der Eijk, Sonnenglanz Consulting

31. Backup

32. Standards Supported 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
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…