04/13/2004

Sang Shin
ebXML sang.shin@sun.com
Java ™ Technology Evangelist
Sun Microsystems, Inc.
www.javapassion.com/webservices/
1 2

Agenda
? What is and Why ebXML?
? Technical architecture
– Business process
– CPP and CPA
–
–
Registry/Repository
Messaging Service What is ebXML?
– Core components
?

?
ebXML Case study
ebXML adoption & interoperability
Why ebXML?
? ebXML Message Service demo 5
4
04/13/2004

ebXML Vision

A global electronic market place where

enterprises of any size, anywhere can:
– Find each other electronically
– Conduct business through exchange of XML
based business messages

9
04/13/2004

Why ebXML? Why ebXML?

? Automation of business collaboration
SOAP, WSDL, UDDI alone are not adequate!
? Need for standardizing business collaboration
? WSDL does not address business
– What are the business processes?
collaboration
– Who are the parties involved in business
collaboration? What are their roles? ? SOAP (in its basic form) does not provide
– What and how do XML documents get exchanged secure and reliable message delivery
in the business collaborations? ? UDDI does not provide repository capability
– What are the security, reliability, quality of
service requirements of this business
for business objects
collaboration?
? ebXML addresses the above needs
10 11

ebXML Value Addition Why ebXML?

Existing B2B Frameworks are not adequate!
? Business process, CPP/CPA over WSDL ? EDI
– Defines business process collaboration
– Too heavy-weight and too rigid
? ebXML Reg/Rep over UDDI ? RosettaNet
– Repository as well as registry – PIP definitions are somewhat rigid and cannot be
discovered per partner basis
? ebXML Message Service over SOAP – RosettaNet community has decided to use ebXML
– Reliability and security semantics Message Service as their future implementation
framework
? Core components
– Common business objects ? BizTalk
– Proprietary, Single-vendor, Single-platform
12
– No concept of Business collaboration & Partner profile
13
04/13/2004

Simple Web Services (WUS) vs.

Web Services Adoption Phases B2B Collaboration (ebXML)
? 1st Phase – Simple Web Services (Now) Simple Web Services B2B Collaboration
– Consumer-focused, stateless
l Simple interaction l Complex interaction
? 2nd Phase – EAI Web Services (Begun) l Consumer oriented l Business oriented
– Deployed within organization boundaries to enable l Short-living process l Long-running process
internal integration l No business l Supports business
collaboration collaboration
? 3rd Phase – Business (B2B) Web Services (2004?) l No partner profile l Supports partner profile
l Not secure, not l Secure and reliable and
– Deployed on Extranets to enable business process reliable non-repudiation
integration with trading partners, customers, other l Does not support l Supports non-
players in your value chain non-repudiation repudiation
l No repository support l Registry and repository

14 15

EAI vs. B2B Collaboration (ebXML) ebXML Project Teams

? ebXML Requirements
EAI B2B Collaboration ? Business Process Methodology
l Within a business l Between business
? Technical Architecture
organization organizations ? Core Components
l Centralized l Distributed control ? Transport/Routing and Packaging
control ? Security
l Implicit contract l Explicit contract ? Registry and Repository
l Small number of l Potentially large ? Quality Review
business number of ? Proof of Concept
processes and business processes ? Trading Partners Profiles
participants and participants ? Marketing, Awareness and Education
16 17
04/13/2004

ebXML Use Case Scenario

Business Profiles 1
Business Profiles Request Business Details

2
Build Local System
EbXML
3 Register Implementation Details Implementatio
Registry n
Register COMPANY A Profile

ebXML

Qu
Do

ery
wn

ab
4

loa

ou
d

t
nt

CO
Sc
me

en

M
ge

PA
ar
an

ios
Arr

NY
an
ss

A
e

pr
sin

Use Case Scenario

Pr

ofil
Bu

of

e
on

ile
5

s
ree
Ag

EbXML compliant
system

18 19

ebXML Architectural Modules

? Business Process Specifications
? Partner Profile and Agreements
Registry and Repository
ebXML
?

? Messaging Service
Architecture ? Core components
They can be used individually!
20
21
04/13/2004

ebXML Architecture ebXML Architecture

Business Process Specifications
Business Process Registration
and Register/discover
Specifications Discovery
Specification Registry
Design
Time Models Repository Register/discover
Partner Profiles and and Registry
Agreements Profiles
Partner Profile Partner Profile
Derive Derive
Specification
Configure Partner Agreement Configure
Governs
Business Message Service Business
Runtime Messaging Service Service
Message Service
Interface Interface
Application Application
22 23

Business Process
Specification
04/13/2004

Business Process Specification Business Process Specification

? Describes collaboration between ? Can be modeled with UMM (UN/CEFACT
two partners Modeling Methodology)
? Defines roles, relationships and ? Formally described by Business Process
responsibilities Specification Schema (BPSS)
? Defines choreography of business ? Machine interpretable
documents ? Referenced by CPP and CPA
? Expressed in platform and vendor ? Refers to Business Document Definitions
neutral format
26 27

Business Process: Conceptual View Business Process Specification

Example (Partial)
<BusinessTransaction name="Create Order" >
<RequestingBusinessActivity name=""
Create Long Term Contract
Business Business isNonRepudiationRequired="true"
Process Process timeToAcknowledgeReceipt=”P2D"
... Forecast Component
Requirements timeToAcknowledgeAcceptance=”P3D">
Collaboration
<DocumentEnvelope BusinessDocument="Purchase Order"/ >
Transaction Customer
customer Send Planning Document Supplier </RequestingBusinessActivity>
Transaction <RespondingBusinessActivity name=""
Place Order isNonRepudiationRequired="true"
timeToAcknowledgeReceipt=”P5D">
<DocumentEnvelope isPositiveResponse="true"
Ship Material
Collaboration BusinessDocument="PO Acknowledgement"/>
</DocumentEnvelope>
Arrange Payment
</RespondingBusinessActivity>
</BusinessTransaction>

28 29
04/13/2004

How Does ebXML BPSS Relate To

Types of Choreography Standards
Others?
? BPML ? Interface definitions
? WSCI ? Collaboration (agreement) definitions
– What happens between interfaces
? WSFL
? Implementation definitions
? XLANG – What happens behind interfaces
? WSDL
? ebXML CPP/CPA
30 31

ebXML BPSS Versus ...

Interface

Implementation
CPP/CPA
Collaboration
32
04/13/2004

CPP (Collaboration CPA (Collaboration Protocol

Describes capabilities of Protocol Profile)
an individual Party
Agreement)
?

– Business capabilities
? Business processes ? Derived from CPP’s of trading
– Technology capabilities partners
? Messaging exchange capabilities
? Transport, messaging, security constraints ? Describes the capabilities that trading
? Provides per-party configuration to business partners have agreed to use to
process specifications perform a particular Business
? Stored in ebXML registry Collaboration
– Business partners can find each other's CPP – Contract between two or more trading partners
through registry – Does not dictate implementation details
34 35

CPA and Runtime Environment CPP (or CPA) and Business

Process Specification
? CPA is used by trading parties' computing
systems to set up runtime environment
CP P(A)
– For the exchange of business messages Process Specification (A1)
<PartyInfo Party Id="N01">

–
<ProcessSpecificationxlinkh ref="http:/

Manifested in Messaging Service Handler Business

(MSH) Collaboration

? Security
Process Specification (A2)
<PartyInfo Party Id="N02">

? Reliability <ProcessSpecificationxlinkh ref="http:/

Business
Collaboration
? Along with Process Specification, defines
a conversation between the two Parties
36 37
04/13/2004

CPA Example (Partial)

<CollaborationProtocolAgreement id = "yoursandmycpa" ...>
<Party partyId = "N01">
<CollaborationRole roleId = "N02" >
<CollaborationProtocol version = "1.0" name="OrderProcessing"
xlink:href = "http://www.ebxml.org/services/purchasing.xml"/>
<Role name = "buyer"/> </CollaborationRole>
<DeliveryChannel ...> <Characteristics nonrepudiationOfOrigin = "false"
confidentiality = "false"
authenticated = "false" Security
authorized = "false"/> </DeliveryChannel>
<Transport transportId = "N05">
<Protocol version = "1.1">SMTP</Protocol> Transport
Message Service
<Endpoint uri = "mailto:bob@localhost" type = "request"/> </Transport>
<DocExchange docExchangeId = "N06"> <ebXMLBinding version = "1.0">
<ReliableMessaging deliverySemantics = "BestEffort" idempotency = "true">
<Retries>5</Retries>
<RetryInterval>60</RetryInterval>
(TR&P)
</ReliableMessaging> Reliability
38

Messaging Service Overview XML Message Layers

? Transport, Routing, and Packaging (TRP)
? Uses SOAP with Attachments as payload XML Document
envelope
– Transport of non-XML data

<- Infrastructure ->

Context
? Supports higher-level semantics needed in
business transactions
– Security Envelope
– Reliability
? Runs over various communication protocols Transport
– HTTP, SMTP, FTP
40 41
04/13/2004

Message Service Design Goals Message Service Design Goals

? Support both XML-based and non XML-
? Robust, yet basic, functionality to
transfer messages between trading
based business information transfer
parties ? Allow vendors to add robustness and
? Using various existing communication higher performance in their
protocols implementation
– Scalability
? Allowing for messaging reliability,
persistence, security and extensibility
? Leverage existing standards
? Allowing robust, yet low-cost solution
42 43

Where is ebXML Message Service? Functional Modules of MSH

What is MSH (Message Service
Handler)?
MSH MSH
Application Application
Node Node
ebXML Message
Service

44 45
04/13/2004

Goals of ebXML Registry

? To enable sharing of information
between interested parties for the
purpose of enabling business process
integration between such parties

Registry and
Repository
47

ebXML Registry Specifications Registry Objects and Metadata

? Registry objects
? Registry services specification – Refers to an object that has been submitted to
– Registry services a Registry for storage and safekeeping
– Interaction protocols – Called "Repository item"
– Message definitions – XML document or DTD, business process
– XML schema models, CPPs, etc.
? Registry information Model ? Metadata
– Types of metadata – Used by registry to classify and manage registry
– Relationship among metadata classes objects
– Represented by RegistryEntry
48 49
04/13/2004

Registry Operations Life-cycle of Repository Item

? Type of operations
– Submitting
– Managing
– Searching
– Retrieving
– Removing
? Performed through registry interface

50 51

Motivation of Core Components

? Many business processes are common
across industry domains
– Procurement, Payment, and Shipping, etc
? Business information requirements are
the same
– Information on "product"
? How business information is used within
Core Components business processes are same
– How information on "product" is identified and
described
54
04/13/2004

Core Components Core Components Examples

? A set of common data items that
? Core component A
– Vendor (Industry1), Manufacturer (Industry 2),
captures real world business concepts Supplier (Industry 3)
– Reusable pieces of contents
? Core component B
? Use industry-neutral notation – Distributor (Industry 1), Wholesaler (Industry
? Enables interoperability among 2), Merchant (Industry 3)
different industry domains ? Core component C
– Store (Industry 1), Outlet (Industry 2), Retailer
(Industry 3)

55 56

ebXML
Case Study
04/13/2004
04/13/2004

Java™ Programming APIs for

ebXML
? Java API for XML Messaging (JAXM)
(JSR-67)
– with ebXML Message Service profile
? Java API for XML Registries (JAXR) (JSR-
93)
Adoption and – ebXML Registry
Interoperability ? Java API for CPP/CPA (JSR-157)
– CPP/CPA 66
04/13/2004

ebXML Endorsements ebXML Endorsements

? Open Travel Alliance (OTA) ? RosettaNet
– Travel industry – Adopted ebXML Messaging Service as their future
implementation framework
? Open Application Group (OAGI)
– Application integration and interoperability
? Covisint
– Automotive industry
? Global Commerce Initiative (GCI)
– Consumer goods manufacturers and retailers
? STAR (Standard for Technology for
Automotive Retail)
? HL7 – Automotive retail
– Healthcare
67 68

ebXML Commercial Products ebXML Open Source

? XMLGlobal (www.xmlglobal.com) ? ebXML V2 Registry
? BindSystems (www.bindsys.com) – Open source as well as public hosting by H.K.
University
? IONA Technology (www.iona.com) – ebxmlrr.sourceforge.net/
? eXcelon (www.exceloncorp.com) ? Messaging Service
? zenAptix (www.zenaptix.com) – Open source donated from Sybase
– www.sybase.com/developer/opensource
? KTNET (www.ktnet.com)
? BitDaemons (www.bitdaemons.com)
? Sybase (www.sybase.com)
69 70
04/13/2004

End

If You Only Remember

One Thing…
ebXML is the standard-based
electronic business framework that
will enable the next big thing,
Business Web Services.

71