se3316a_2013_10_ebxml

SE3316a Web Technologies

ebXML - Electronic Business XML

Dr. Jagath Samarabandu

[email protected]

TEB 351

519-661-2111 x80058

Fax: 519-850-2436

SE3316 Jagath Samarabandu 27-Nov-13

ebXML Drivers Electronic Business XML is an initiative from

Organization for the Advancement of Structured Information Standards (OASIS) and

United Nations Centre for Trade Facilitation and Electronic Business (CEFACT)

Resources http://ebxml.xml.org/ http://www.uncefact.org/ http://www.oasis-open.org/ http://www.ebxmlforum.net/ Interesting article on Adoption of ebXML - Hiding in

Plain Sight


Electronic Business XML ebXML aims to provide the exchange of

electronic business data in Business-to-Business and Business-to-Customer environments E.g. Exchanging orders, delivery schedules, receipts

and invoices as well as the choreographing the events that generate these documents

The ebXML specifications provide a framework in which EDI's substantial investments in Business Processes can be preserved in an architecture that exploits XML's technical capabilities


B2B Integration LevelsCompany A Company B

Communication

Choreography

Agreement

Transactions


ebXML Promises A secure and reliable way to communicate A way to specify the semantics of business

documents A protocol for conducting business transactions A way to specify the choreography of

collaborations A way to negotiate and document agreements A place to register profiles, agreements,

processes, and business information


ebXML A primary objective of ebXML is to lower the

barrier of entry to electronic business in order to facilitate trade, particularly with respect to small-and medium-sized enterprises (SMEs) and developing nations.

A key aspect for the success of the ebXML initiative is adherence to the use of the W3C suite of XML and related Web technical specifications to the maximum extent practical.

Technologies will also be borrowed from other consortiums, as appropriate.


Technical Architecture

Internet

Messaging Service

BusinessServiceInterface

BusinessServiceInterface

Company A Company B

Protocol

Profile Profile

BusinessApps

BusinessApps

Agree-ment

Choreo-graphy


The Collaboration Protocol Profile (CPP) The Collaboration Protocol Profile (CPP)

provides the definition (DTD and W3C XML Schema) of an XML document that specifies the details of how an organization is able to conduct business electronically

The Collaboration Protocol Profile (CPP) is an XML document that specifies: Contact information (business address, industry

classification, etc.) Supported business processes Transport protocol Security mechanisms


Collaboration Protocol Agreement (CPA) The Collaboration Protocol Agreement (CPA)

specifies the details of how two organizations have agreed to conduct business electronically

It is formed by combining the CPPs of the two organizations

The information in the CPA is used to implement Business Service Interfaces (BSI) to enable exchange of Messages with trading parties

The ebXML Message Service Handler is used to implement the exchange of messages


Collaboration Protocol Agreement

Basic Tasks:

CPP of Company A CPP of Company B

Role

Packaging

Transport

Role

Packaging

Transport

match

match

match


Configuring CPA: Matching Business Processes and the Roles ebXML mandates CPPs to reference the same

BP document in order to create a CPA If BP references are NOT same

Structural matching of BP documents performed prior to Role matching

Matching transitions between Binary Collaborations as specified in Multiparty Collaboration

Roles should be complementary ex : Buyer & Seller in Request Purchase Order PIP


Configuring CPA: Matching Document Packaging ebXML message payloads are packaged using

the MIME multipart/related content type Matching by structural comparison is performed

MIME types of the SimplePart elements of corresponding subtrees should match

CompositeList matched in MIME types and in sequence of composition

Matching Document Level Security is difficult to do automatically due to several radically different approaches to document-level security


Business Process Specification Schema (BPSS) Business Process Specification Schema (BPSS)

provides the definition of an XML document (in the form of an XML DTD) that describes how an organization conducts its business

While the CPA/CPP deals with the technical aspects of how to conduct business electronically, the Specification Schema deals with the actual business process


Business Process Specification Schema (BPSS) A Business Process specifies the sequence of

exchanging business data with other Trading Partners Business Processes are capable of expressing the

following types of information: Choreography for the exchange of document instances (for

example, the choreography of necessary Message exchanges between two Trading Partners executing a "Purchasing" ebXML transaction)

References to Business Process and Business Documents (possibly DTD's or Schemas) that add structure to business data

Definition of the roles for each participant in a Business Process


ebXML and EDIEDI Limited to large

organizations High cost-of-entry Rigid message sets Used by 5% of

enterprises outside the Fortune 1000

ebXML Takes advantage of cheap

Internet technology Built on EDI experience

with input from EDI community

Preserves EDI investment Designed for the other 95%


ebXML and Web Services Step 1: Description

WSDL ebXML CPP Spec and ebXML Business Process

Spec Step 2: Publication and Discovery

UDDI ebXML Registry Spec

Step 3: Invocation SOAP over HTTP ebXML Messaging Spec integrating SOAP, HTTP


WSDL and ebXML CPPWSDL provides: Service name Service parameters Endpoint for invocation

ebXML CPP provides: Service name Service parameters Endpoint for invocation Role of an organization in

the context of a service Error-handling Failure scenarios


WSDL and ebXML BPWSDL identifies Business processes

ebXML BP identifies Business processes Roles an organization

must play Messages being

exchanged


UDDI and ebXML Registry SpecUDDI Basic identification Industry classification Technical capabilities

ebXML Registry Spec Basic identification Industry classification Technical capabilities Search capability Retrieval of objects in

corresponding repositories

NOTE: ebXML offers a way to use UDDI to locate ebXML

registries http://www.ebxml.org/specs/rrUDDI.pdf


ebXML Summary and Implementation Status Through ebXML it is possible to automate public

business processes although how to form the CPAs automatically have only been partially attacked yet!

Currently ebXML compliant registries are available, for example, OASIS ebXML Registry Reference Implementation Project (ebxmlrr), ebxmlrr.sourceforge.net

ebXML messaging has been implemented by several companies


ebXML compared

Negotiation

Process

Description

Transport

Transactions

Discovery

Message

The Microsoft way The HP wayThe IBM way The ebXML way

Collaborationpartner profile

BizTalkXLang

SOAP

XML / EDI / Flat File

E-speak

XAML

Coll. Partneragreement

Registry &repository

Businessprocess meth.

Transport, routing, pack.

BizTalkComponents

tpaML

WSFL WSCL

Core comp.

SFS

WSDL

UDDI


Summary of ebXML ebXML offers a comprehensive framework for

Collaborative E-Business Web Services An open framework, not another standard Solves interoperability both at the business and

the technology level Enables plug & play e-business

se3316a_2013_10_ebxml

Documents

Transcript of se3316a_2013_10_ebxml