Transcript ebXML Update, August 2004

The New ebXML for SOA
Presentation, November 2004
XML2004
Washington DC
David RR Webber
[email protected]
Dan Pattyn
[email protected]
Copyright OASIS, 2004
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=1
8201098
Copyright OASIS, 2004
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
Copyright OASIS, 2004
ebXML Adoption - 2004
China –
11,000 ebMS
servers
EU – Formal
Adoption
USA – DOD
EMALL
Comparison of ebXML adoption by region, number / size / scope of projects as of December 22, 2003
Copyright OASIS, 2004
Backed by Industry Groups
The Open Healthcare Group
Copyright OASIS, 2004
A New Approach to Software Engineering
Developers
Conventional
models
Analysis
Specification
Design
Test
Maintenance
Coding
Installation
Business
Users
Procurement
Adaptation,
integration
Use
Requirements
Needs
Interactive
models
Copyright OASIS, 2004
Paradigm Shift


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
Copyright OASIS, 2004
Business Process Evolution
Cross-Enterprise
Service Centric
Digitization
Transaction Centric
Digitization of Simple
Task & Processes
Process
Re-Engineering
Value Co-Creation
via Customer Centric
Collaboration
Extreme Mobility
Infrastructure
Occasionally
Connected Application
Wearable Computing
Process Improvement
Copyright OASIS, 2004
Emerging Supporting Standards
Copyright OASIS, 2004
Agenda


ebXML Today

Why ebXML? (deployment landscape)

Classic ebXML

Enhanced ebXML for SOA

ebXML component drill-down
Summary

Review
Copyright OASIS, 2004
Deployment 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
Copyright OASIS, 2004
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?
Copyright OASIS, 2004
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?
Copyright OASIS, 2004
The Challenge of Change

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 multilingual.
Vast gulf between First World and Third World.
Copyright OASIS, 2004
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,
1

2

then enterprise to small business interactions,
3

small business to small business interactions
4

and service solution to customer.
Copyright OASIS, 2004
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.
Copyright OASIS, 2004
How do you put this all together?
Where / Who
Where / Who
Action
How
Information
What
Action
How
Information
What
Where / Who
Event
When
Rule
Why
Event
When
Action
How
Information
What
Event
When
Rule
Why
Rule
Why
Copyright OASIS, 2004
Classic ebXML
How the pieces fit together
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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)
Copyright OASIS, 2004
Initial Pieces – Defining the
Interaction
<<BinaryCollaboration>>
Bulk Buying
Supplier
Dealer
Collaboration
Agreement
(CPA)
Specifies
Business
Process
Specifications
(BPSS)
Contains
Business
Transactions
Bulk Buying
Business Process
Check Product Availability
Dealer Location
Product Requirements
Submit Purchase Order
Contains
XML Messages Schema definitions (XSD) +
content processing templates
Grammars
Copyright OASIS, 2004
Classic Two-Role Business Process

Requestor / Responder interaction model
Copyright OASIS, 2004
ebXML CPA visual editing
Process
Linkage
Participant
Information
(DUNS
Party ID
Company
Contact
Web site
Process
Role
Status
Description)
Message
exchange
details
Messaging
preferences
Copyright OASIS, 2004
ebXML CPA / BPSS functions
ebXML BP identifies

Business processes
including multi-party, multistep exchanges

Roles an organization must
play

Business transactions

Messages being exchanged

Context variables

Business rules of edge
conditions
ebXML CPA provides:










Transaction handling
services


Error handling

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
Copyright OASIS, 2004
ebXML Solution Architecture
Capture
Process
Details with
Participant
Roles /
Context
and
Message
Exchanging
Definitions
Business Agreement
Templates
1
Exchanges
Messaging
System
References
Reference - Domain
Transactions +
Business Process Models
Reference – Domain
Ontology and
Semantic Information
Drives
Partner A
Partner B
Handles
Produces
Enveloping + Routing
Transactions + Validation
CPA – Exchange
Agreements
CAM XML templates –
Business Exchange
Formats and Rules
BPSS + Workflow –
Models of Interaction
Service / Actions
Messaging
System
4
Manages
Integration – application
system interactions
2
3
Controlled by
Queue Integration Agent
Processes – state
management,
linking and switching
Copyright OASIS, 2004
Classic ebXML example
Each partner
has ebMS
exchange
system
BPSS implicit
from exchange flow
SENDING
RECEIVING
Partner A
Partner B
SOAP
messaging
INTERNET
Requester
Documents
ebXM L
enveloping
and
delivery
re
Exchange
Transactions
Exchange
Transactions
ig
u
s
nf
re
ebXML
ebMS
ebXML
ebMS
4
2
XML schem a
n fi
gu
4
Delivery
Queue
Delivery
Queue
3
Partner A
Business
Application(s)
5
Partner
CPA(s)
co
1
Partner
CPA(s)
s
6
6
co
Partner B
Business
Application(s)
1
Responder
Documents
2
5
XML schem a
3
Copyright OASIS, 2004
Classic ebXML example +
Registry
Registry
provides
common
reference
point
User Profiles
CPA lookup
Docum ent Definitions
Schem a XSD
ebXML
Registry
(optional)
BPSS implicit
from exchange flow
Client User
Interface
3
SENDING
RECEIVING
Partner A
Partner B
SOAP
messaging
INTERNET
Requester
Documents
ebXML
enveloping
and
delivery
re
Exchange
Transactions
Exchange
Transactions
ig
u
s
nf
re
ebXML
ebMS
ebXML
ebMS
4
2
XML schem a
n fi
gu
Delivery
Queue
Partner A 5
Business
Application(s)
Partner
CPA(s)
co
1
Partner
CPA(s)
s
6
6
co
4
Delivery
Queue
Partner B
Business
Application(s)
1
Responder
Documents
2
5
XML schem a
Copyright OASIS, 2004
Enhanced ebXML
Extending the core
architecture
Copyright OASIS, 2004
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
Copyright OASIS, 2004
Enhancing ebXML - Multiparty




Need to handle complex
flows beyond two-party
configurations
Partner A
Today’s internet world is
rarely simple
Partners perform multiple
roles and interact with
and provide range of
services
Knowing context is vital
Partner C
Partner B
co
c o m pl
l l a ete
b o sc
r a en
t io ar
io
n
Partner D
Partner F
Partner G
Partner F
of
Partner E
Partner G
1
ebXML
BPSS
Model and
Scenario
Copyright OASIS, 2004
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
Copyright OASIS, 2004
Success
RespondCreditStatus
conditio
n
OK
Multiparty Model
with BPSS V2
Action
To Role
Action
Action
RequestPriceQuote
buyer
To Role
Failure
noSellersResponded
condition
invalid
Success
respondPriceQuotes
conditio
n
OK
Marketplace
Buying Agent
To Role
Action
To Role
Action
To Role
Action
To Role
Producer
invalid
RequestPriceQuote
trading service
Success
respondPriceQuote
conditio
n
OK
DrawDownCredit
trading service
AcceptPriceQuote
trading service
ignorePriceQuote
trading service
ReplenishCredit
trading service
Seller Credit Service
creditStatusUnknown
Winning Producer
Failure
condition
Losing
Producers
buyer
Credit Service
checkBuyersCredit
Credit Burea
Action
To Role
Copyright OASIS, 2004
Attaining SOA Through Component
Layers
Business Agreement
Languages (RINs)
Collaboration Profile
Agreement (CPA)
Choreography &
Coordination Lang.
(BPSS)
Context Driven
Information
Exchanges (CAM)
Semantic Registry
Copyright OASIS, 2004
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)
Copyright OASIS, 2004
1
ebXML
BPSS
Model and
Scenario
EXCHANGE
PACKAGES
Client User
Interface
User Profiles
CPA details
Docum ent Definitions
Schem a XSD
CAM tem plates
Context Instances
ebXML
Registry
(optional)
BPSS script
2
Partner
CPAs
1
BPSS
Script
Context
Variables /
Rules
Complete Collaboration
Details Drive each ebMS
4
3
Content
Management
Services
Vocabulary
Management
Services
XML schem a
Participating
Documents
CAM
templates
5
Exchange
Transactions
ebXML
ebMS
Each
partner
has
exchange
system
jCAM
7
Partner
Business
Application(s)
Exchange
Transactions
ebXM L
enveloping and
delivery
9
Web service
(optional)
8
6
Delivery
Queue
WSDL
interface(s)
Enhanced
ebXML –
BPSS and
context
driven
INTERNET
SOAP
messaging
context + rules
templates
Copyright OASIS, 2004
Modelling the Business Process

from the model – generates actual BPSS as XML instructions
Copyright OASIS, 2004
Deterministic linking of BPM to layers

Each step consists of deterministic action and outcomes
Group
Possible
Responses
Transport
layer
return
settings
Configure outcomes
and flow control
Select associated responding document
Copyright OASIS, 2004
Configure the Business Exchange Rules
Logical business transaction can have more than one structure layout
BPSS
Step
transaction
XML
instance
structure(s)
template
Content
Assembly
Template
can add inline rules directly
into structure
Simple Declarative Statements
Business context rules
+
Content Reference rules
+
Data Validation rules
+
External Mapping rules
makeOptional()
excludeTree()
item type="noun"
name="Agency/@AgencyID"
UIDReference="ukt000910"
<conditional
expression="'//SupplierID' and
lookup(value,'SGIRWSDL:supp
lierID_check')"
<MapRule output="type"
input="Sales/Company/Year
/Qtr/Product@type"/>
Copyright OASIS, 2004
Understanding about Context

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 1568
1 : the parts of a discourse that surround a word or passage and can throw light on its meaning
2 : the interrelated conditions in which something exists or occurs
Copyright OASIS, 2004
Generating a Context Instance

Add parameter value rules and document value rules
Configure Context
Instance header
Create a rule and
set a value
Check a document
and change a BPSS
parameter
Copyright OASIS, 2004
Moving to deployment
Business
agreement
Information
Exchange
Information
Purposing
Domain Semantics
Drives
document
exchanges
Participant Profiles
Copyright OASIS, 2004
Example – Collaboration SOA
Industry
Partners
1
Messages
5
Messages
Transport
ebMS
server
Applicant
Institution
e-Service
authority
system
CPA
check
CAM data
validator
XML
Structure
Rules
Partner
Management
Web forms
CPA
instances
2
Proxy
Submission
Service
Provider
3
Applicant
Company
Oracle
database
Central
ebXML
Registry
CPA
instances
(Persistent
Storage)
4
System
Administrators
Manage Partner
Interactions
Copyright OASIS, 2004
ebXML component drilldown
Some extended details on
each piece
Copyright OASIS, 2004
Messaging Layers
Message Services
Application Arena
ebXML
B2B Market, Global
Multi-enterprise
Big A2A
Integrated App
Families
Typical access via:
ebXML
SOAP/HTTP
(JAX-M for ebXML)
ebXML
SOAP/HTTP
(JAX-M for WS-Routing)
Web Services
for XML Message
Web Services
WS
Small A2A
for RPC
Integrated Apps
Homogeneou
s Application
Reusable
Components
Tighte
rLimited
SOAP/HTTP
(JAX-RPC)
WS
ORB
(RMI/IIOP)
WS
Granularity
Coupling
Security
Looser
Extensive
Copyright OASIS, 2004
WSDL and ebXML CPA / BPSS
WSDL provides:
 Service name
ebXML CPA provides:
 Service name and
parameters

Service parameters

Endpoint for invocation

Endpoint for invocation

Role of an organization in
the context of a service
WSDL identifies:
 Business processes

Failure scenarios
article comparing messaging
technologies at ebXMLForum

Roles an organization must play

Messages being exchanged

Error handling
ebXML BP identifies
 Business processes
Copyright OASIS, 2004
Registry Roles
Information Engine
“A semantic registry is the key
foundation block upon which global
electronic business exchanges will be
built”.
Business
Analyst
Administration
Distribution
Web Interface
Interchange
Program Level
Semantics
Software
Developers
XML
Information
Profiles
Industry Business Standards
Registry Protocol Standards
ebXML, ISO11179, OASIS,
OAGi, RosettaNet, UBL, UDEF
Copyright OASIS, 2004
ebXML Registry - XML document management






XML Registry +
Registry
Repository
Interface Life Cycle
Query
Life cycle
Manager
Manager
Soap
management
features
Authentication Security Persistence
Query management
Manager
Authorization Manager
engine
Security features
Repository
includes digital
Database with RIM
signatures, user Ids
Registry Organization Extrinsic
Objects
Classification of any
Objects
BPSS, CPA, CC
type of object
Federation of
http://registry.oasis-open.org
Content
Copyright OASIS, 2004
Storing the Enterprise Artifacts
Collaboration Partner
Agreements- CPA
Collaboration Partner
Profiles - CPP
5
Contract
4
BP Specification
Workflow
Process
XForms
3
Specifications
Schema
Messages
Content Assembly
Mechanism - CAM
2
Motivation
Rules
1
Data/Codes
Nouns
Core
Components
Source: BCM Lubash Pyramid
Time
Events
Services/Functions
Verbs
People
Roles
Network
MSH/SOAP
Transport
Routing, Packaging
WSDL
Copyright OASIS, 2004
Capturing Noun Semantics
Copyright OASIS, 2004
Summary
Review
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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
implementation - 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
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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
Copyright OASIS, 2004
www.ebxml.org
www.oasis-open.org
Copyright OASIS, 2004