ebxml technical overview l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
ebXML Technical Overview PowerPoint Presentation
Download Presentation
ebXML Technical Overview

Loading in 2 Seconds...

play fullscreen
1 / 37

ebXML Technical Overview - PowerPoint PPT Presentation


  • 426 Views
  • Uploaded on

ebXML Technical Overview. How all the pieces fit together. Duane Nickull CTO – XML Global Technologies Chair – UN/CEFACT eBusiness Architecture duane@xmlglobal.com. Agenda:. Examine some business and technical needs for ebXML. Look at the overall architecture of ebXML. Followed by:

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'ebXML Technical Overview' - sherlock_clovis


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
ebxml technical overview

ebXML Technical Overview

How all the pieces fit together

Duane Nickull

CTO – XML Global Technologies

Chair – UN/CEFACT eBusiness Architecture

duane@xmlglobal.com

agenda
Agenda:
  • Examine some business and technical needs for ebXML.
  • Look at the overall architecture of ebXML.

Followed by:

  • ( Technical Track | Business Track )
ebxml introduction

ebXML Introduction

Understanding Mission and Architecture

business needs
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.
the need for xml
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.
what is self describing
What is Self Describing???

ST*323*712990413

V1*7039610*NEW ZEALAND QUEEN*D*104N*SCAC***L

LS*0100

R4*D*D*JAX*JACKSONVILLE FL****

V9*EAD**920819**JACKSONVILLE FL***A26

R4*D*D*ORF*NORFOLK, VA**NORFOLK INTL TERMIN**

V9*EAD**920817**NORFOLK, VA***A26

R4*L*K*MEB*MELBOURNE, AUST****

V9*EDD**920712**MELBOURNE, AUST***A40

R4*L*K*SYD*SYDNEY, AUST****

V9*EDD**920715**SYDNEY, AUST***A40

R4*L*K*WLG*WELLINGTON, NEW ZEALAND****

V9*EDD**920721**WELLINGTON, NEW ZEA***A40

LE*0100

SE*25*712990413

This is not

self describing

data!

xml is self describing
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>

xml is not enough
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.
thoughts
Thoughts
  • XML by itself is not the magic bullet.
  • What we really need is a dynamic cross-walk mechanism for XML based vocabularies.
thus the need for ebxml
Thus the need for ebXML

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

architecture concepts
Architecture Concepts…

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 concepts13
Architecture Concepts…

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.

slide14

Business Operational View

Comply with

Business aspects

of

business transactions

BOV

related

standards*

Covered by

Viewed

as

Functional Service View

Information technology

aspects of

business transactions

Comply with

FSV

related

standards

Covered by

B

U

S

I

N

E

S

S

T

R

A

N

S

A

C

T

I

O

N

S

* UML Models

slide16

BDV

BRV

BTV

BSV

And more modelling….

Designers

Business Experts

Analysts

Facilitors & Modelers

slide17

And yet more modelling….

Business Process

And Information Models

fsv architecture
FSV Architecture

CPP

CPP

CPA

Interface

Interface

slide19
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

Synchronization

Registry

RIM

I / O

API

ebxml registry architecture

Passed by URI

Reference

Applications

GUI’s

Referenced

By URI

ObjectManager()

ObjectQuery

Manager()

ebXML MSH

Transport Layer

Transport Layer

ebXML Registry Architecture

Managed

Objects

RIM

API

RSS Messaging

RSS Messaging

Registry Side

Client Side

registry item examples
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
xml elements
XML Elements
  • XML elements can reference items from a Registry.
  • Examples:
    • <LastName>
    • <NomDeFamille>
    • <Name>
    • <姓>

All are the same item!!!

registry item examples23
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!!!

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

Most Registry Items are metadata – not instances of data.

<?xml version=“1.0”>

<UID>12345</UID>

<Element> 姓 </Element>

<Also org=“yourOrg”>

LastName

</Also>

Repository

Item

<?xml version=“1.0”>

< 姓UID=“FooRep:12345”>

Duane

</ 姓 >

Document

Instance

Registry

API

API

Managed

object

Managed

object

Managed

object

ebxml cpp and cpa
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

ebxml business process specification schema
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

core components
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.
ebxml business information
ebXML Business information

Collaboration

Protocol

Profile (CPP)

Supported

Business

Process

1..

<<References>>

Bridge to

Legacy Data

1..

<<Constructed From>>

DTD’s

Schemas?

DTD’s

Schemas?

DTD’s

Schemas?

<<Constructed From>>

XML Representations

Business Information Entities

<<Constructed From>>

Core

Comp.

Core

Comp.

Core

Comp.

Core

Comp.

Core

Comp.

Core

Comp.

Core

Comp

methodologies

BOTTOM

UPAPPROACH

TOP

DOWNAPPROACH

Methodologies

UMMModeling

Core Components

Payload Metadata

Final BusinessPayload

PayloadMetadata

Information Components

LegacyData

information harmonization
Information Harmonization

UN/CEFACT

Core Components

2005

2004

2003

UBL

2002

Existing eBusiness Standards

EDI

HL7

OAG

RosettaNet

xCBL

OTA

SAP

XBRL

runtime stack first look
Runtime Stack (first look).

CPP/A

BP Rules

BPEE

BPSS

URL

Port

Security

ebXML MHS

I/O

App Server

O/S

ebxml use case
ebXML Use Case

Management

PR / IR

CRM

Production

Sales and Marketing

Shipping

Procurement

ebxml business service interfaces
ebXML Business Service Interfaces

Management

PR / IR

CRM

Production

Sales and Marketing

OUTSOURCE

Shipping

Procurement

some final thoughts
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