copyright oasis, 2004 david rr webber [email protected] dan pattyn [email protected]...

Copyright OASIS, 2004

David RR [email protected]

Dan [email protected]

Presentation, November 2004 XML2004Washington DC

The New ebXML for SOAThe New ebXML for SOAThe New ebXML for SOAThe New ebXML for SOA

mailto:[email protected]

mailto:[email protected]


ebXML in the News "As ebXML becomes standardized, it will

become the de facto way everyone does business."

--Tony Scott, CTO, General Motors

Interview in Information Week – March, 2004

http://www.informationweek.com/shared/printableArticle.jhtml?articleID=18201098




ebXML in a nutshell Globally developed standard (ISO15000)

for: Exchanging business messages

Conducting trading relationships

Defining and registering business processes

Communicating data in common terms

Assembling business transactions

Using Internet as delivery vehicle


ebXML Adoption - 2004

Comparison of ebXML adoption by region, number / size / scope of projects as of December 22, 2003

China – 11,000 ebMS

serversUSA – DOD

EMALL

EU – Formal Adoption


Backed by Industry Groups

The Open Healthcare Group


Interactivemodels

Conventionalmodels

A New Approach to Software Engineering

AnalysisSpecification

Design

Coding

Test

Maintenance

Developers

Adaptation, integrationInstallation

Use

Needs

Requirements

ProcurementBusinessUsers


Traditional Approach ETL EAI UML Data warehouse B2B + electronic commerce

New Holistic Approach Service Oriented Architecture Business-centric models Context driven environment Semantic vocabularies and ontologies Leverage XML

Paradigm Shift


Value Co-Creation via Customer Centric Collaboration

Extreme Mobility Infrastructure

Occasionally Connected Application

Wearable Computing

Business Process Evolution

Cross-Enterprise Service Centric Digitization

Transaction Centric Digitization of Simple Task & Processes

Process Re-Engineering

Process Improvement


Emerging Supporting Standards


Agenda ebXML Today

Why ebXML? (deployment landscape)

Classic ebXML

Enhanced ebXML for SOA

ebXML component drill-down

Summary

Review


Deployment LandscapeDeployment Landscape

Today’s medium to large enterprises face a bewildering array of interchange format and mechanism choices Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness


The CIO nightmare What standards do I choose? How do I build significant ROI for my organization? Can I leverage my existing systems? What resources are available to deploy my

solution? What are my partners doing? How much of this is real? How do I avoid being in a vendor revolving doors

strategy? How is open source important to my organization? What if I just build it my way and ignore everyone

else?


Identifying the Needs What are you trying to build anyway? Better EDI system? Reach SME partners more effectively? e-Marketplace solution? Next generation XML system and network? Open e-Government systems? Customer facing service solution? Integration of major corporations applications? Common industry collaboration and vocabularies?


People accept that a digital world is coming and are adjusting their work habits accordingly: virtual presentations and meetings all digital documents and transactions digital photographs, voices, sounds, RFID,

and signatures (online banking, iTunes, UPS, Radio Shack, Home Depot).

Digital artifacts shared factor – naturally multi-lingual.

Vast gulf between First World and Third World.

The Challenge of Change


Business Challenges In determining operational needs there are

four levels and areas to include: The first level is the overall operational

approach to solving large enterprise level interactions,

then enterprise to small business interactions, small business to small business interactions and service solution to customer.

1

2

3

4


Business Goals Since everyone’s business needs vary

depending on their own circumstances, the focus here is on providing the means to understand the technology capabilities and then giving guidelines on how those relate to solving typical business needs

Obviously the optimum business solution is to purchase just the right amount of technology to solve the given business requirements.


How do you put this all together?

Action Event

InformationRuleWhatWhy

How When

Where / Who Where / Who Where / Who

Action Event


How When

Action Event


How When


How the pieces fit together

Classic ebXMLClassic ebXMLClassic ebXMLClassic ebXML


Classic ebXML vision

Two trading partners collaborate together to create working relationship

Interchange defined as requestor / responder Business transactions exchanged control the

state of the process Sharing of definitions and business

understanding between partners within a community

Allows smaller companies to participate, not just large corporations


ebXML components

Technical Architecture (TA1.04)

Message Services (ebMS – MHS)

Collaboration Protocol Agreements (CPA / CPP)

Business Process ( BPSS )

Registry Services / (RegRep / RIM)

Core Components (CCTS / UBL)


Initial Pieces – Defining the Interaction

Bulk Buying

Business Process

Specifications(BPSS)

CollaborationAgreement

(CPA)Specifies Bulk Buying

Business Process

Check Product AvailabilityDealer LocationProduct RequirementsSubmit Purchase Order

Schema definitions (XSD) + content processing templates

Contains

Contains

Business Transactions

XML Messages Grammars

Supplier<<BinaryCollaboration>>

Dealer


Classic Two-Role Business Process Requestor / Responder interaction model


ebXML CPA visual editing

ParticipantInformation

Messagingpreferences

Message exchange details

(DUNSParty IDCompanyContactWeb siteProcessRoleStatusDescription)

ProcessLinkage


ebXML CPA / BPSS functions

ebXML BP identifies Business processes

including multi-party, multi-step exchanges

Roles an organization must play

Business transactions Messages being exchanged Context variables Business rules of edge

conditions Transaction handling

services Error handling

ebXML CPA provides: Service name and parameters Endpoint for invocation Role of an organization in the context

of a service Organization demographic information Failure scenarios Business process scenario and

business transaction activity step Link to partner responsibilities Transaction Messages being

exchanged Transport level QOS parameters Certificate and Encryption

configuration Business status of agreement


ebXML Solution Architecture

Capture Process Details withParticipant Roles / Contextand Message ExchangingDefinitions

Reference – Domain Ontology and

Semantic Information

Reference - Domain Transactions +

Business Process Models

References

Business AgreementTemplates

1111

Messaging System

Drives

Messaging System

Partner A Partner B

Exchanges 2222

Enveloping + RoutingTransactions + Validation

Handles

Queue Integration Agent

Controlled by3333

Processes – state management,

linking and switching

Integration – application system interactions

Manages4444BPSS + Workflow – Models of Interaction

Service / Actions

CAM XML templates – Business Exchange Formats and Rules

CPA – Exchange Agreements

Produces


Classic ebXML exampleEach partnerhas ebMS exchangesystem

INTERNET

Partner A Partner B

Partne rCPA(s) Partne r

CPA(s)11

ebXMLebMS

ebXMLebMS Re sponde r

Docume nts

Re que ste rDocume nts

2

2

Excha ngeTra nsa ctions


De live ryQue ueDe live ry

Que ue

XM L s che m a

XM L s che m a

Partner BBusiness

Application(s)

Partner ABusiness

Application(s)

ebXM Lenveloping

anddelivery

S OA Pm essaging

44

5 5

6 6

SENDING

RECEIVING

3

3

BPSS implicitfrom exchange flow


Classic ebXML example + Registry

INTERNET

Partner A Partner B

Partn e rCPA(s) Partn e r

CPA(s)11

ebXMLebMS

ebXMLebMS

ebXMLRegistry

(optional)3

Re spo nd e rDo cume nts

Re qu e ste rDo cume nts

2

2



De live ryQue ueDe live ry

Que ue

Clie n t Use rIn te rface

Us e r Profile sCPA look upDocum e nt De finitionsSche m a XSD

XM L s che m a

XM L s che m a

Partne r BBusine ss

Application(s)

Partne r ABusine ss

Application(s)

ebXM Lenveloping

anddelivery

SOA Pm essaging

44

5 5

6 6

SENDING

RECEIVING

Registryprovidescommon referencepoint

BPSS implicitfrom exchange flow


Extending the core architecture

Enhanced ebXMLEnhanced ebXMLEnhanced ebXMLEnhanced ebXML


SOA - Business Needs Ability to manage a large community of participants

in an e-Service and e-Business system Manage central resources to allow partners to

quickly join the community and integrate their own applications into the e-Service network

Partners can select the business process they want to use, pick the version(s) of transactions they can support, create their CPA configuration(s), test compliance, certify their ebMS systems and begin interacting


Enhancing ebXML - Multiparty

Need to handle complex flows beyond two-party configurations

Today’s internet world is rarely simple

Partners perform multiple roles and interact with and provide range of services

Knowing context is vital

Partner A Partner B

Partner C

Partner D

Partner E

Partner F

Partner G

Partner F

Partner G

ebXMLBPSS

Model andScenario

1


BPSS key to eBusiness SOA SOA

provides technology foundation and open interchange model and specifications

BPSS formalizes this with business process control captures the business exchange details provides business agreement model for participants provides facilitation for components in the SOA XML template script sharable across an industry

domain context driven enables localization of standard models


Action ch e ckBu ye rsC re d it

To Role b u ye r

Bu

yin

g A

ge

nt

Cre

dit

B

ure

au

S ucce ss R e sp o n d C re d itS ta tu s

condition

O K

Fa ilure cre d itS ta tu sUn kn o wn

condition in va lid

Pro

du

ce

r

Action R e q u e stPr ice Q u o te

To Role tra d in g se rv ice

Action R e q u e stPr ice Q u o te

To Role b u ye rM

ark

etp

lace

S ucce ss re sp o n d Price Q u o te s

condition

O K

Fa ilure n o Se lle rsR e sp o n d e d

condition in va lid

S ucce ss re sp o n d Price Q u o te

condition

O K

Action D ra wD o wn C re d it


Se

lle

r C

re

dit

S

erv

ice

Action Acce p tPr ice Q u o te


Action ig n o re Pr ice Q u o te


Action R e p le n ish C re d it


Se

lle

r C

re

dit

S

erv

ice

Win

nin

g P

ro

du

ce

rL

osin

g

Pro

du

ce

rs

Multiparty Model with BPSS V2


EventsRules

TransactionTransaction

SchemaSchema

ContractContractAgreement Pattern

WorkflowWorkflowModeling & Business Patterns

request

process

request

process

response

process

reject

accept propose

counter

Exchange Exchange

SpecificationSpecificationModel & Schemas

Nouns

VerbsTransport

RolesConceptConceptRegistry

Tem

plat

eT

empl

ate --

driv

en

driv

en

Business GoalsBusiness GoalsGoal Pattern

CAM templateCAM template

Context

Business Agreement Languages (RINs)

Choreography & Coordination Lang.

(BPSS)

Collaboration Profile Agreement (CPA)

Context Driven Information

Exchanges (CAM)

Semantic Registry

Attaining SOA Through Component Layers


ebXML components work today Technical Architecture (ebSOA)

Message Services / Web Services (ebMS – MHS)

Collaboration Protocol Agreements (CPA / WSDL)

Business Process ( BPSS )

Federated Registry Services / Semantic Content (RegRep / RIM / SCM – OWL)

Core Components (CCTS / UBL)

Content Assembly Mechanism (CAM)

Context Management / State Management (new)


Enhanced ebXML –

BPSS andcontextdriven

jCAM

W eb service(optional)

ebXMLRegistry

(optional)

Clie n t Use rIn te rface

S OA Pm essaging

ebXMLBPSS

Model andScenario Us e r Profile s

CPA de tailsDocum e nt De fin itionsSche m a XSDCAM te m plate sConte xt Ins tance s

BP S S script

Partne rCPAs

BPSSScrip t

Partic ip atin gDocu me n ts

XM L s che m a

CAMte mp late s

Conte x tV a ria ble s /

Rule s


ebXMLebMS

De live ryQue ue

PartnerBusiness

Application(s)

6

7

ebX M Lenveloping and

delivery

INTERNETExcha nge

Tra nsa ctions

8

Eachpartnerhasexchangesystem

1

2

1

3

4

5

Complete CollaborationDetails Drive each ebM S

VocabularyManagem ent

Serv ices

ContentManagem ent

Serv ices

W SDLin te rface (s) 9

EX CHANGEPACKAGES

conte x t + rule ste m pla te s


Modelling the Business Process from the model – generates actual BPSS as XML instructions


Deterministic linking of BPM to layers Each step consists of deterministic action and outcomes

Select associated responding document

GroupPossible Responses

Configure outcomes and flow control

Transport layer returnsettings


ContentAssemblyTemplate

Configure the Business Exchange Rules

XMLinstance

structure(s)

Business context rules

+Content Reference rules

+Data Validation rules

+External Mapping rules

Logical business transaction can have more than one structure layout

can add inline rules directly into structure

makeOptional()excludeTree()

item type="noun" name="Agency/@AgencyID" UIDReference="ukt000910"

<conditional expression="'//SupplierID' and lookup(value,'SGIRWSDL:supplierID_check')"<MapRule output="type" input="Sales/Company/Year/Qtr/Product@type"/>

Simple Declarative Statements

BPSSStep

transactiontemplate


Context is the pervasive driver to effective engineering Drives dynamic process configuring and control Ensures accurate information capture, packaging and

delivery Key to correct relationships between partners in a

collaboration

Lack of context control mechanisms is the most prominent reason why legacy e-Business systems are difficult and complex to extend and support

Date: circa 15681 : the parts of a discourse that surround a word or passage and can throw light on its meaning2 : the interrelated conditions in which something exists or occurs

Date: circa 15681 : the parts of a discourse that surround a word or passage and can throw light on its meaning2 : the interrelated conditions in which something exists or occurs

Understanding about Context


Generating a Context Instance Add parameter value rules and document value rules

Check a document and change a BPSS parameter

Create a rule and set a value

Configure ContextInstance header


Moving to deployment

Business agreement

Drives documentexchanges

Participant ProfilesD

om

ain S

eman

tics

Information Purposing

Info

rmatio

n

Exch

ang

e


Example – Collaboration SOA

Industry Partners

XMLStructure

Rules

XMLStructure

Rules

TransportebMSserver

TransportebMSserver

Oracledatabase

Oracledatabase

CentralebXMLRegistry

CentralebXMLRegistry

CPAcheckCPA

checkCAM datavalidator

CAM datavalidator

PartnerManagementWeb forms

PartnerManagementWeb forms

(Persistent Storage)CPA

instances

CPAinstances

CPAinstances

CPAinstances

System AdministratorsManage PartnerInteractions

ApplicantCompany

ApplicantInstitution

Proxy SubmissionService Provider

MessagesMessages

2222

1111

33334444

5555e-Service authority systemMessages

Messages


Some extended details on each piece

ebXML component drilldownebXML component drilldownebXML component drilldownebXML component drilldown


Messaging Layers

CouplingTighter

Looser

SecurityLimited

Extensive

ebXML

Web Services for XML Message

Web Services for RPC

Reusable Components

SOAP/HTTP (JAX-M for ebXML)

ebXML

WS

SOAP/HTTP (JAX-RPC)

ORB (RMI/IIOP)

WS

SOAP/HTTP (JAX-M for WS-Routing)

Typical access via:

Granularity

Small A2A Integrated Apps

Homogeneous

Application

WS

Big A2A Integrated

App Families

B2B Market, Global Multi-enterprise

ebXML

Application Arena Message Services


WSDL and ebXML CPA / BPSS

WSDL provides: Service name Service parameters Endpoint for invocation

ebXML CPA provides: Service name and

parameters Endpoint for invocation Role of an organization in

the context of a service Failure scenariosWSDL identifies:

Business processes ebXML BP identifies Business processes Roles an organization must play Messages being exchanged Error handling

article comparing messagingtechnologies at ebXMLForum

http://www.ebxmlforum.org/articles/ebFor_Art_20030613_01.html

http://www.ebxmlforum.org/articles/ebFor_Art_20030613_01.html


Registry Roles“A semantic registry is the key

foundation block upon which global electronic business exchanges will be

built”.

BusinessAnalyst

Web Interface

InformationProfiles

Distribution

Administration

Program LevelSemantics

Information Engine

Industry Business StandardsRegistry Protocol StandardsebXML, ISO11179, OASIS,

OAGi, RosettaNet, UBL, UDEF

XML

Software Developers

Interchange


ebXML Registry - XML document management XML Registry +

Repository Life cycle

management features

Query management engine

Security features includes digital signatures, user Ids

Classification of any type of object

Federation of Content

Registry

Interface Life CycleManager

QueryManager

SecurityManager

PersistenceManager

Authentication

Authorization

Soap

RepositoryDatabase with RIM

RegistryObjects Organization

ExtrinsicObjects

BPSS, CPA, CC

http://registry.oasis-open.org

http://registry.oasis-open.org/


Storing the Enterprise Artifacts

Motivation Time People

Specifications Schema

Workflow

Contract

Directory Services

Collaboration PartnerProfiles - CPP

Collaboration PartnerProfiles - CPP

2

1

3

4

5

Presentation

Collaboration PartnerAgreements- CPA

Collaboration PartnerAgreements- CPA

Artifact relationships

Content Assembly Mechanism - CAM

Content Assembly Mechanism - CAM

BP SpecificationBP Specification

Data/Codes Services/Functions Network

XFormsXForms

MSH/SOAPMSH/SOAP

Source: BCM Lubash Pyramid

VerbsVerbs

MessagesMessages

RulesRules EventsEvents

ProcessProcess

RolesRoles

TransportRouting, Packaging

TransportRouting, Packaging

NounsNouns

Core Components

Core Components

WSDLWSDL


Capturing Noun Semantics


Review

SummarySummarySummarySummary


Summary

Enhanced ebXML allows business users to logically decompose the problem and express it coherently and reliably

Templates capture the business scenarios and rules Templates derived to ebXML artifacts – CPA, BPSS,

CAM, WSDL, plus context parameters as needed Deployment environment driven by software

templates Industry groups create catalogues of re-usable

solutions and networks of collaborating systems


Vendors Products

Full list available from http://ebxml.org/implementations

12 vendors certified for interoperable ebMS solutions

Implementations from: Oracle, Adobe, Sun, Fujitsu, Sybase, BCEmergis, BEA, Cyclone Commerce, Sterling Commerce, bTrade, webMethods, TIE Commerce, Smartdraw.com and more

Open source solutions – http://freebXML.com for messaging and registry

http://ebxml.org/implementations

http://freebxml.com/


Selected ebXML Projects

Automotive Industry moving to adopt ebXML - Feb 2004 ebXML underpins new Korean Bank and Insurance services

- Feb 2004 US Gov DOD EMall

Embraces ebXML Messaging - Jan 2004 US Center for Disease Control (CDC) ebXML implementatio

n - October, 2003

e-Invoice system for major Metro operator - September, 2003

ebXML Asia interoperability testing - August, 2003 Bangkok, Thailand Project - SMEs & Nectec - August, 2003 ebXML and Energy Utilities Market- July, 2003

http://www.informationweek.com/story/showArticle.jhtml?articleID=18201098

http://www.ebxmlforum.org/articles/ebFor_20040201.html

http://www.ebxmlforum.org/articles/ebFor_20040201.html

http://gcn.com/23_1/news/24582-1.html



http://www.ebxml.org/case_studies/documents/casestudy_cdc_phinms.pdf

http://www.ebxml.org/case_studies/documents/casestudy_cdc_phinms.pdf

http://www.kanetti.fi/~juslem/docs/Bridging%20the%20gap.pdf










Finding ebXML Resources

Download the specs from www.ebxml.org Open source resources www.freebxml.com News and Events www.ebxmlForum.com Join OASIS Subscribe to ebXML-DEV mail list (link @ ebXML.org) Review public archives of OASIS ebXML TC

work Encourage your industry group to adopt ebXML

specifications for their standards Specify ebXML-compliance from providers

http://www.ebxml.org/

http://www.freebxml.com/

http://www.ebxmlforum.com/


Books on ebXML

Kotok and Webber, ebXML: the New Global Standard, New Riders, Aug 2001, http://www.ebxmlbook.com/

Nickull, et al., Professional ebXML Foundations, Wrox Press, Nov. 2001

Chiu, ebXML Simplified, John Wiley & Sons, June 2002 Gibb and Damodaran, ebXML Concepts and Application,

John Wiley & Sons, Nov. 2002


www.ebxml.org

www.oasis-open.org

copyright oasis, 2004 david rr webber [email protected] dan pattyn [email protected]...

Documents

copyright oasis

needs n

n customer

n summary

nutshell n

agenda n ebxml

n traditional approach

cio nightmare n