1 IEEM 5352 Enterprise Integration ebXML. 2 Outline Introduction to ebXML Background on ebXML...

1

IEEM 5352Enterprise Integration

ebXML

2

Outline Introduction to ebXML Background on ebXML Initiative ebXML e-Business Framework ebXML deliverables ebXML specifications/documents

3

Introduction to ebXML A framework for developing a business

transaction vocabulary based on XML. Provides descriptors for modeling business

processes that include the definition of software components.

Encourage the interoperability of electronic commerce in both technical and business perspectives.

4

ebXML mission Provide an open XML-based infrastructure

enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties

Bring benefits of traditional EDI to SMEs (small and medium-sized enterprises) – social agenda

Royalty-free (vs. RAND) availability

5

ebXML vision A global electronic marketplace where enterprises of

any size, anywhere can:– Find each other electronically– Conduct business through the exchange of XML-

based messages:• Using standard message structures• According to standard business-process sequences• With clear business semantics• According to standard or mutually agreed trading

partner agreements• Using off-the-shelf purchased business applications

6

ebXML Value Provides the only globally developed open XML-

based standard built on a rich heritage of electronic business experience.

Creates a single global electronic market to enable all parties irrespective of size to engage in internet-based electronic business.

Enables parties to complement and extend current EC/EDI investment expand electronic business to new and existing trading partners.

Facilitates the convergence of current and emerging XML efforts.

7

Guidelines to deliver ebXML value

Using the strengths of OASIS and UN/CEFACT to ensure a global open process.

Developing technical specifications for the open ebXML infrastructure.

Creating the technical specifications with the world’s best experts.

Collaborating with other initiatives and standards development organizations.

Building on the experience and strengths of existing EDI knowledge.

8

Enlisting industry leaders to participate and adopt ebXML infrastructure.

Realizing the commitment by ebXML participants to implement the technical specifications.

9

ebXML guide

10

Background on ebXML Initiative Driven by

– The United Nations Center for Trade Facilitation and Electronic Business (UN/CEFACT, http://www.uncefact.org/)

– The Organization for the Advancement of Structured Information Standards (OASIS http://www.oasis-open.org/

Has been launched in November 1999.

11

The ebXML project Phase 1: November 1999 to May 2001 to develop

family of specifications to Version 1.0 Phase 2:

– OASIS TCs take over Message Service, Reg/Rep, and CPP/CPA in May 2001

– UN/CEFACT takes over Business Process and Core Components in May 2001, creates eBusiness Transition Working Group (eBTWG)

12

The ebXML project involved over 300 active participants working in the various teams, and over 4000 subscribers to mailing lists.

The project had its first meeting in November 1999. The final meeting took place in May 2001 in Vienna, Austria.

At this meeting, the project delivered some 25 documents, all of which are available for download from the project's web site, http://www.ebxml.org/

13

UN Organization Structure

General Assembly

Security Council International Court of Justice

Trusteeship Council

Economic & SocialCouncil Secretariat

Regional EconomicCommission

ECA (Economic Commission for Africa)ECE (Economic Commission for Europe)ECLAC (Economic Commission for Latin America and Caribbean Sea)ESCAP (Economic and Social Commission for Asia and Pacific)ESCWA (Economic and Social Commission for West Asia)

ICAOUPUITUWMOIMOWTOWIPOUNCTADUNCITRAL

Functional CommitteeSessional, Permanent, Adhoc Committee

14

Initiatives to ebXML project RosettaNet is an e-business standardization

initiative in the high tech industry. (http://www.rosettanet.org/)

The Open Applications Group (OAG) is the largest XML-based horizontal e-business framework. (http://www.openapplications.org/)

The Open Travel Alliance (OTA) is an initiative to develop standards for the travel industry. (http://www.ebxml.org/news/pr_20010801.htm)

15

Covisint is one of the best-known and successful digital marketplaces in the world. (http://www.covisint.com/)

The Global Commerce Initiative (GCI) is an international standardization consortium for companies in the consumer goods industry, supported by the major players in this industry (http://www.globalcommerceinitiative.org/)

16

Industry Groups Support ebXML

The Open Healthcare Group

17

OASIS Members Support ebXML

18

ebXML e-Business FrameworkA Sample Scenario for ebXML

12

3

4

56

87

Compant A

Compant B

ebXML registry

19

1. Project team analyze a particular B2B process to engage in e-business interactions– an e-business methodology (UN/CEFACT

Modeling Methodology, UMM) to analyze– a formal description of the process (ebXML

Business Process Specification Schema, BPSS). – business information to be exchanged (ebXML

Core Components framework) – use ebXML-compliant repository to implement,

and make it available through an ebXML registry

20

2.A particular company should – use the ebXML registry's search functionality

to find business processes.– see what kind of ebXML message interactions

it needs to support to perform the 'Insurer' role in this process.

– make sure it can support this process.

21

3.The insurance company – state its capability to fulfill a document known

as a collaboration protocol profile (CPP).– encode information – such as message payload

packing information, and digital signatures. 4.Other companies

– browse the registry to find relevant business processes.

– is similar to Step 2.

22

5.Once this company has found the same business process, it can start a search for business partners that offer complementary services.

6.The exporting company – needs to make sure its B2B integration product

supports the ebXML framework. – create a proposal for a trading partner

agreement, called a collaboration protocol agreement (CPA).

23

7. The insurance company– can agree with this proposal or reply to it with a

counter- proposal. – needed to support the business interactions

controlled by the CPA. 8. Business collaboration

– be started as long as the CPA remains valid.– messages exchanged can use the facilities of the

ebXML messaging services

24

ebXML Framework Components Business Process Specification Schema:

– an XML-based specification language defining "public" business processes.

– focuses on the collaboration of trading partners, the binary collaborations.

– is strongly influenced by UMM. Core Components:

– provide the business information that is encoded in business documents that are exchanged between business partners.

25

Registry/Repository: – deliverables specify a general-purpose

repository that is useful for more than merely conducting business searches.

Collaboration Protocol Profiles and Agreement:– these are XML documents that encode a party's

e-business capabilities or two parties' e-business agreements, respectively.

26

Transport, Routing, and Packaging:– ebXML messaging services provide an elegant

general-purpose messaging mechanism. – ebXML messaging service is layered and

transported over SOAP with Attachments Security:

– is pervasive to all the components and is critical for a production e-business system.

Architecture:– the ebXML architecture

27

ebXML functional architecture

28

Main ebXML concepts Business messages - expressed in XML Business processes - defined in UML, expressed in

XML Business service interface -handles one role in a

business process . expressed in XML Trading partner agreement - specifies protocol

properties required for two specific business service interfaces to talk to each other . expressed in XML

Transport and routing layer - moves the actual XML data between business service interfaces

29

ebXML e-business framework comprises five layers:– Business Process (BP)– Core Components (CC)– Collaborative Partner Profiles and Agreements

(CPP/CPA)– Registry/Repository (Reg/Rep)– Message Service (TRP)

30

Architecture ( 1st Draft)

31

ebXML deliverables ebXML registry/repository ebXML message service ebXML collaboration protocol profile &

collaboration protocol agreement (CPP/CPA) ebXML core components ebXML business process specifications

32

ebXML registry/repository Registry and repository together form a database Provide services to:

– Store and retrieve objects– Query– Update– Track versions– Classify

Repository

Registry

33

Registry represent data objects– XML schemas, – business process descriptions, – ebXML Core Components, – UML models, – generic trading partner information, and– software components.

Two ways to look at the ebXML registry: – from the outside looking in, or – from the information model looking outward.

34

Role of registry/repository

35

UN/CEFACT registry architecture

36

UN/CEFACT Registry functional view

37

UN/CEFACT artefact submissionRegistry Storage (ebRIM)

Technical Solution

Electronic Docs

BRS/RSM

UN/CEFACT artefact

submission

Attached docs

RSM

RSM Metadata (DTD)

CC/BIE (XMI/XML)

BRS

BRS Metadata (DTD)

XML Metadata

Project pkg

ebXML RR

BP (XMI/XML)

Registry objects

Repository items

38

ebXML message service Provides a reliable and secure way for trading

partners to exchange business messages. Broken down into three parts: (1) an abstract

Service Interface, (2) functions provided by Message Service Layer, and (3) the mapping to the underlying transport protocol(s).

The development of the Messaging Services system, or Message Service Handler (MSH), must consider and reference the communication requirements specified in a CPA document.

39

ebXML collaboration protocol profile & agreement (CPP/CPA)

Responsible for maintaining and developing the collaboration protocol profile and agreement specification.

CPP includes the essential information about the trading partners, such as the contact information, supported business processes, industry classification, interface requirements and messaging service requirements.

CPA contains the message interface requirements and other implementation details pertaining to the mutually agreed upon business process.

40

ebXML core components Building blocks for XML schemas, etc. “Syntax neutral”, with unique IDs Similar to “common business objects” but with

context Naming conventions follow ISO 11179 Description of context drivers Approach for extending core components into

context dependent domain components

41

Related documents– Core component overview– Core component discovery and analysis– Context and re-usability of core components– Guide to the core components dictionary– Naming convention for core components– Core component dictionary– Core component structure

42

ebXML business process specifications Primary methodology is UN/CEFACT’s Modeling

Methodology (UMM) Defines process and the types of information required

from the analysis Business process document’s information:

– Choreography for the exchange of business document instances

– References to business process and information meta model

– Definition of the roles for each participant in a business process

43

Business Process Specification Schema (BPSS)– Production Rules defining the mapping from

the UML version of the Business Process Specification Schema to the XML version

– Implements subset of UN/CEFACT Meta Model

– UML version of the Business Process Specification Schema

– XML version of the Business Process Specification Schema

44

UMM metamodel and ebXML business process specification schema

45

ebXML business process specification schema to UMM, CPP/CPA and core components

46

UN/CEFACT’s MetaModelling Methodology (UMM)

Business Process Definition

Business Collaboration Analysis

Business Transaction Design

Process

Sequence

Design

Business

Document

Design

Business Process

XML Schema

Business Document

XML Schema

CC/BIELibrary

ProcessPattern

BusinessOperation

MapBusiness

RequirementSpecification

BDV

BRV

BTV

BSV

UN/CEFACT’s MetaModelling Methodology (UMM)

Business Process Definition

Business Collaboration Analysis

Business Transaction Design

Process

Sequence

Design

Business

Document

Design

Business Process

XML Schema

Business Document

XML Schema

CC/BIELibrary

ProcessPattern

BusinessOperation

MapBusiness

RequirementSpecification

BDV

BRV

BTV

BSV

47

BDV (Business Domain View) BRV (Business Requirement View) BTV (Business Transaction View) BSV (Business Service View)

48

ebXML business process specification schema and other ebXML specifications

49

ebXML specifications/documents Four categories of ebXML deliverables

– technical specifications• Standards companies must follow in case they want to

build up ebXML compliant systems• Requirements Specification• Technical Architecture• Business Process Specification Schema• Registry Information Model• Registry Services Specification• Messaging Services Specification• Collaboration Protocol Profile & Agreement

50

– technical reports• documents, which are either guideline to

interpret/implement the ebXML concepts or• catalogues, which contains the foundation material

based on the ebXML specifications

51

– reference materials• documents, which are normative references in

approved specifications– white papers

• documents, which constitute a snapshot of the work within respective project team and represent a report that has been approved by the project team

• Using UDDI to find ebXML Registry• Registry Security Proposal• Proposed revisions to architecture

52

– Documents’ web site• http://www.ebxml.org/specs/index.htm#technical_s

pecifications• http://www.ebxml.org/specs/index.htm#technical_re

ports• http://www.ebxml.org/specs/index.htm#reference_

materials• http://www.ebxml.org/specs/index.htm#white_paper

s

53

References http://www.cecid.hku.hk/ebxml.php http://www.perfectxml.com/wp/readchap.asp?Cur

Book=31 http://dev2dev.bea.com/pub/a/2004/12/ebXML.ht

ml http://www.ebxml.org/specs/ebBPSS.pdf