EbXML Technical Overview How all the pieces fit together Duane Nickull CTO – XML Global Technologies Chair – UN/CEFACT eBusiness Architecture [email protected]

ebXML Technical Overview

How all the pieces fit together

Duane NickullCTO – XML Global Technologies

Chair – UN/CEFACT eBusiness Architecture

[email protected]

2

Agenda:

Examine some business and technical needs for ebXML.

Look at the overall architecture of ebXML.

Followed by: ( Technical Track | Business Track )

ebXML Introduction

Understanding Mission and Architecture

4

Business Needs Link traditional data exchanges (EDI or new XML)

to business applications.

Lower costs to configure new e-Business

relationships.

Create “Smart” Business Processes.

Provide a reusable set of core information

components.

Low cost server and client based solutions.

Protect investments in existing systems.

5

The need for XML

It is desirable to transport data around networks (including the internet).

XML is the format of choice for marking up that data.

SGML was too complex, HTML not robust enough.

6

What is Self Describing???ST*323*712990413V1*7039610*NEW ZEALAND QUEEN*D*104N*SCAC***LLS*0100R4*D*D*JAX*JACKSONVILLE FL****V9*EAD**920819**JACKSONVILLE FL***A26R4*D*D*ORF*NORFOLK, VA**NORFOLK INTL TERMIN**V9*EAD**920817**NORFOLK, VA***A26R4*L*K*MEB*MELBOURNE, AUST****V9*EDD**920712**MELBOURNE, AUST***A40R4*L*K*SYD*SYDNEY, AUST****V9*EDD**920715**SYDNEY, AUST***A40R4*L*K*WLG*WELLINGTON, NEW ZEALAND****V9*EDD**920721**WELLINGTON, NEW ZEA***A40LE*0100SE*25*712990413

7

XML is Self Describing<?xml version=“1.0”?><Data> <Item ID=“112”> <Name>Rod</Name> <Price>12.00</Price> <Units>1</Units> </Item> <Item ID=“114”> <Name>Reel</Name> <Price>15.00</Price> <Units>1</Units> </Item> <Item ID=“120”> <Name>Bait</Name> <Price>24.00</Price> <Units>3</Units> </Item> </Data>

8

XML is not enough. XML is for marking up data. XML, by itself, does not solve

interoperability problems yet it is an important tool for doing so.

XML does not provide semantics. XML does not solve business problems. XML Schemas do not provide semantics

or solve business problems.

9

Thoughts

XML by itself is not the magic bullet.

What we really need is a dynamic cross-walk mechanism for XML based vocabularies.

10

Mission: ebXML enables anyone, Mission: ebXML enables anyone, anywhere to do business with anywhere to do business with anyone else over the Internetanyone else over the Internet

Thus the need for ebXML

11

ebXML Technical Architecture

eb X M L co mp lian tso f tw are system

Bus ines s P rof iles

S c enar ios

e bX M LR e g is try

INDUSTRY

XM L S pec if ic ations

R eq u est In d u stry Pro cess D eta ils

1

B u ild L o cal S ystemImp lemen tat io n

R eg ister Imp lemen tat io n D eta ilsR eg ister C O M PA N Y A Pro f ile

3

2

5A g ree o n T rad in g A rran g emen t4

Q uery ab o u t C O M PA NY A p ro f ile

D ow n lo ad ebX M L compon en ts

DO BUSINESS TRANSACT IO

NS

6

COMPANY A

COMPANY B

12

1. Business Processes and associated Core Components (in XML)

2. A mechanism for registering and storing them (Registry)

3. A mechanism for declaring a Trading Partners capabilities and they can do/support (CPP)

Architecture Concepts…

13

5. A mechanism for describing a Trading Partners capabilities (CPP).

4. A mechanism for describing a Trading Partner Agreement (CPA).

6. A standardized messaging service (ebXML MS)

7. A standardized methodology/process for modeling the real world business and translating it into XML.

Architecture Concepts…

14

BUSINESS

TRANSACTIONS

BUSINESS

TRANSACTIONS

Viewedas

Information technologyaspects of

business transactions

Information technologyaspects of


Business Operational View

Functional Service View

Business aspectsof


Comply with

Covered by

BOV related

standards*

Comply with

Covered by

FSVrelated

standards

* UML Models

15

Modeling ….

B D VB usinessD om a in

V iew

B R VB usiness

R equirem entV iew

B T VB usiness

T ra nsa ctionV iew

B SVB usiness Service

V iew

BOVBusiness Operational View

16

BDV

And more modelling….

BRV BTV BSV

Business Experts Analysts Designers

Facilitors & Modelers

17

And yet more modelling….

Business ProcessAnd Information Models

18

FSV Architecture

Registry Service Interface

Payload

Business ServiceInterface

Business ServiceInterface

InternalBusiness App

Shrink-wrappedApplication

Registry

Implementers

Business Process and Information Models

Build

Registration

TPA

UML to XML conversion

Retrieval of ebXML Specifications & Models

Build

Retrieval of Profiles & new or updated ebXML Models

Retrieval of Profiles & new or updated ebXML Models

Registration RegistrationTPP

ebXML metamodel XML content

TPP

Registration

TPA Governs

TPP Derives

Interface Interface

CPA

CPP CPP

19

At the heart of ebXML is a powerful system of Registries and Distributed Repositories.

The Registry provides the interfaces. Registries contain pointers and meta information

in the Registry Information Model (RIM). ebXML v 1.0 Registries have two main interfaces

– ObjectManager() and ObjectQueryManager(). The methods exposed by the interfaces have set

metadata for expressing queries and returns.

Repository RegistrySynchronization API I / O

RIM

20

ebXML Registry Architecture

Transport Layer

Registry Side Client Side

ebXML MSH

RSS Messaging

Transport Layer

RSS Messaging

ObjectManager() ObjectQueryManager()

RIM

ManagedObjects

API

ApplicationsGUI’sPassed by URI Reference

Referenced By URI

21

Registry Item Examples Registry systems can give you

information about many types of ebXML and even non-ebXML documents.

- CPP and CPA templates- Business Process Documents- Core Components and CC Aggregates- DTD’s and Schemas (Assembly documents)- Programming artifacts

22

XML Elements XML elements can reference items from

a Registry.

Examples: <LastName> <NomDeFamille> <Name> < 姓 >

All are the same item!!!

23

Registry Item Examples XML elements in business messages can

reference items in a registry.

Examples: <LastName UID=“myrep:1236”> <NomDeFamille UID=“myrep:1236”> <Name UID=“myrep:1236”> < 姓 UID=“myrep:1236”>

All are the same item!!!

24

XML Elements in document instances contain pointers to Repository Item’s.

Most Registry Items are metadata – not instances of data.

RegistryRegistry

API

<?xml version=“1.0”>

< 姓 UID=“FooRep:12345”>Duane

</ 姓 >

API

<?xml version=“1.0”><UID>12345</UID>

<Element> 姓 </Element><Also org=“yourOrg”>LastName</Also>

Managedobject

Managedobject

Managedobject

25

ebXML Messaging Service

HTTP SMTP IIOP FTP …

ebXML Applications

Messaging Service I nterface

Messaging Service

Authentication, authorization andrepudiation services

Header Processing

Encryption, Digital Signature

Message Packaging Module

Delivery ModuleSend/Receive

Transport Mapping and Binding

26

ebXML – CPP and CPA

Trading Partner Profiles and Agreements. Tells you Business Service Interfaces,

bindings etc. Provide a list of Business Processes or

Web Services. NOT designed to be a legal agreement. example

27

ebXML Business Process Specification Schema

BPSS are Runtime and Design Time artifacts.

Captures particulars of BP in an XML schema controlled instance.

References Business Information used in each step of process.

Should Identify Assembly Docs at Design time.

example

28

Core Components:

A Core Component captures information about a real world (business) concept.

A Core Component can be atomic or aggregate.

It is ‘Core’ because it occurs in many different areas of industry/business information exchange.

29

Core Component Realization

30

ebXML Business information

Collaboration

ProtocolProfile (CPP)

1..

SupportedBusinessProcess

<<References>>

DTD’sSchemas?

DTD’sSchemas?

DTD’sSchemas?

<<Constructed From>>

1..

CoreComp.

CoreComp.

CoreComp.

CoreComp.

CoreComp.

CoreComp.

CoreComp

Business Information Entities



XML Representations

Bridge toLegacy Data

31

Methodologies

Final BusinessPayload

Payload Metadata

PayloadMetadata

Core Components

Information Components

UMMModeling

LegacyData

TOPDOWNAPPROACH

BOTTOMUPAPPROACH

32

Information Harmonization

EDI xCBL HL7 OTA RosettaNetOAG SAP XBRL

UN/CEFACTCore Components

2002

2003

2004

2005

Existing eBusiness Standards

UBL

33

Runtime Stack (first look).

O/S

App Server

ebXML MHSURLPort

Security

BPEE

BP Rules

BPSS

CPP/A

I/O

34

ebXML Use Case

Management

Production

Sales and Marketing

CRM

PR / IR

Shipping Procurement

35

ebXML Business Service Interfaces

Management

Production

Sales and Marketing

CRM

PR / IR

Shipping Procurement

OUTSOURCE

36

Some Final Thoughts.. ebXML ideal foundation for Web Services. Build an open architecture, not a “Standard” Truly interoperable and Extensible (Global) Includes everyone from SME’s to Fortune 1000. Facilitates global eBusiness.

Q & A Duane Nickull

37

Q & A