Copyright © OASIS® 2011. All Rights Reserved. ebXML Messaging Version 3.0 & AS4 Interoperability...

Copyright © OASIS® 2011. All Rights Reserved.

ebXML Messaging Version 3.0&

AS4 Interoperability Demo

OASIS ebXML Messaging TC



Overview Part 1: Core Specification – Summary

Presenter: Sander Fieten Part 2: Advanced Features – Overview

Presenter: Sander Fieten AS4 – Introduction

Presenters: Pim van der Eijk AS4 – Interoperability demo

Presenters: Theo Kramer, Mike O’Connell, Akihisa Sako, Makesh Rao

Summary Presenter: Pim van der Eijk

Q&A


ebXML Messaging Version 3.0Part 1: Core Specification

Sander Fieten


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


New ebMS 3.0 Concepts & Features

Build on WS-* standards Processing Modes

Parameters for capturing and expressing configuration choices

Message Exchange, Reliability, Security etc. Message Pull Feature

Message Receiver Polls the Message Sender Message Partition Channels

Messages assigned to channels Supports priority handling


Message Pull Feature

Receiver with restricted connectivity Intermittent connection, firewalls, no static IP

Getting messages “just in time” Avoid liability of locally storing too long before processing

Authorization Only authorized endpoints can pull on a specific channel

“Light”MSH

Business application

Pull capable MSHBusiness

application

Consumer Producer

mpc

HTTP POST

Pull Request

HTTP response

Pulled Message1

2

3

45

Receiver Sender


ebXML Messaging 3.0 Part 2: Advanced Features

Sander Fieten


Extended Concepts & Features

Multi-hop messaging Route messages through a cloud of intermediaries

Message Bundling Send multiple user messages as one SOAP message High volume, non real-time transactions involving

small payloads Message Splitting

Send one large user message as multiple SOAP messages

Message Compression Payloads and message headers


AS4 Profile

Pim van der Eijk


AS4 – The lightweight solution

Message packaging governed by ebMS 3.0 Support for both 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


AS4 Interoperability Demo

Theo Kramer


Participants Axway

Akihisa Sako The Business Interaction Networks Company

www.axway.com Cisco

Makesh Rao Transforming how people connect, communicate and

collaborate www.cisco.com Flame Computing

Theo Kramer Red hot software solutions for business messaging

www.flame.co.za

http://www.axway.com/

http://www.cisco.com/

http://www.flame.co.za/


Basic scenario

OAG Purchase Order process Message exchange patterns:

① Push and Push

② Push and Pull Message signing Using internet connections

MSHBusiness applicatio

n

Buyer

ProcessPurchaseOrder

AcknowledgePurchaseOrder

2

56

1


n

Seller

4

3


Scenario 1 – Push and Push


n

Buyer

6

1


n

Seller

4

3

Two HTTP requests Receipts sent in the HTTP response


ebMS Receipt


ebMS Receipt

2

3

5

6


Scenario 2 – Push and Pull


n

Buyer

7

1


n

Seller

4

3

Three HTTP requests Receipt for PO sent in the HTTP

response Receipt for PO Acknowledgement sent in

separate HTTP connection


ebMS Receipt


ebMS Receipt

2

3

7

5 PullRequest

6


Demo 1

FlameMSH

Business applicatio

n

Buyer

6

1

AxwayMSH

Business applicatio

n

Seller

4

3ProcessPurchaseOrder

ebMS Receipt


ebMS Receipt

2

3

5

6

Push and Push scenario Flame Computing as Buyer Axway as Seller Messages and Receipts are signed


Demo 2

Push and Pull scenario Cisco as Buyer Flame Computing as Seller No signing is used

CiscoMSH

Business applicatio

n

Buyer

7

1

FlameMSH

Business applicatio

n

Seller

4

3


ebMS Receipt


ebMS Receipt

2

3

7

5 PullRequest

6


Summary

Pim van der Eijk


ebMS 3.0 and AS4 ebMS 3.0

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


ebMS3/AS4 Implementations Implementations in demonstration:

Axway Cisco Flame Computing

Other implementations: Covast adapter for Microsoft Biztalk, Data

Applications Limited, ENEA, Fujitsu, NEC Open Source: Holodeck

http://holodeck-b2b.sourceforge.net/ More implementations exist, but are not yet publicly

announced

http://holodeck-b2b.sourceforge.net/


GS1 and AS4 GS1 eCom Technology

Group (eTG) provided input into design of AS4

GS1 AS4 white paper to spread awareness on AS4 in GS1 community

Compares AS4 to the AS2 protocol and to the SBDH

SME connectivity seen as main benefit

GS1 considers replacing AS1 with AS4


Industry Endorsement (i) Aerospace industry in Europe

AS4 pilot Cisco

Uses AS4 with its B2B reseller partners EASEE-gas

European Association for the Streamlining of Energy Exchange – Gas considers migration to AS4

Electronics and High Tech RosettaNet Multiple Messaging Services (MSS)

European E-Government Common Infrastructure for all Cross-Border e-

Government


Industry Endorsement (ii) Healthcare

HL7 Version 3 Standard: Transport Specification - ebXML

Japan Electronics and Information Technologies Association (JEITA)

Multiple implementations, free JEITA EDI client OASIS Energy Interoperability TC

Planning an ebMS3 binding for smart grid communication

Open Applications Group (OAGIS) Textile, Clothing, Footwear in Europe

ebMS3 using SMTP transport


Q & A ……….


More Information ebMS Version 3.0 Part 1: Core Specification

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/os/

ebMS Version 3.0 Part 2: Advanced Features http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/

AS4 Profile http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-

profile/v1.0/AS4-profile-v1.0.pdf

TC public page http://www.oasis-open.org/committees/ebxml-msg/



http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.pdf

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.pdf

http://www.oasis-open.org/committees/ebxml-msg/


AS4 compared to AS2

AS4 has comparable features to AS2 including: 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

Copyright © OASIS® 2011. All Rights Reserved. ebXML Messaging Version 3.0 & AS4 Interoperability...

Documents

Transcript of Copyright © OASIS® 2011. All Rights Reserved. ebXML Messaging Version 3.0 & AS4 Interoperability...