Introduction to ebXML - Department of Computer Engineering

Download Report

Transcript Introduction to ebXML - Department of Computer Engineering

ebXML (Electronic
Business XML)
Kanda Runapongsa
Dept of Computer Engineering
Khon Kaen University
Outline


What is and Why ebXML?
Technical architecture
Business process
 CPP and CPA
 Registry/Repository
 Messaging Service
 Core components


ebXML adoption
168493: XML and Web Services (II/2546)
2
Objectives




Understanding the fundamental concepts
and motivations of ebXML effort as a
framework for electronic market place
Understanding the architecture of ebXML
and its functional modules
Being able to interpret and construct
ebXML messages
Understand the relationship of ebXML to
other web services standards
168493: XML and Web Services (II/2546)
3
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
ebXML effort was started and sponsored by
United Nations (UN/CEFACT, Organization for
Advancement of Structured Information
Standards) and Organization for Structured
Information Standards (OASIS)
168493: XML and Web Services (II/2546)
4
Why ebXML?



Need for standardizing business
collaboration which in turn enable
automation of business collaboration
Under ebXML, the actual business
transaction occurs by exchanging XMLbased business messages
The structure of these business messages
and the environment of business
collaboration need to be standardized
168493: XML and Web Services (II/2546)
5
Why ebXML?

SOAP, WSDL, UDDI alone are not
adequate



WSDL does not address business
collaboration
SOAP does not provide secure and reliable
message delivery
UDDI does not provide repository
168493: XML and Web Services (II/2546)
6
Why ebXML?


Existing B2B Framework are not adequate
EDI



RosettaNet


Too heavy-weight and too rigid
Has been used only by large companies
Does not provide machine-readable business
collaboration documents
BizTalk

Proprietary Single-vendor Single-platform
168493: XML and Web Services (II/2546)
7
Goals of ebXML



Make electronic business simple, easy, and
ubiquitous
Use XML to the fullest extent possible
Offer an open standard that enables
business transactions across industry
boundaries for both business-to-business
and business-to-consumer commerce
168493: XML and Web Services (II/2546)
8
Goals of ebXML



Bring together the structure and content
of various XML business vocabularies into
a single specification
Offer a migration path from current EDI
standards, as well as XML vocabularies
Keep adoption costs to a minimum
168493: XML and Web Services (II/2546)
9
ebXML Use Case Scenario


Step 1. Company A checks ebXML registry
to see what kinds of business processes
are already defined
Step 2. After company A finds the
business it wants, for example, “purchase
order” business process, it decides to
build and deploy its own application that
captures the semantics of that business
process
168493: XML and Web Services (II/2546)
10
ebXML Use Case Scenario

Step 3, company A then submits its own
business profile to ebXML registry. The
business profile describes the business
processes the company support as well as
its ebXML capabilities and constraints

For example, it might want to register its
business profile which says that it can
participate in purchase order business process
as a buyer
168493: XML and Web Services (II/2546)
11
ebXML Use Case Scenario



Step 4, company B discovers business
processes supported by company A in the
ebXML registry by looking at business
profile submitted by company A
Step 5, company B sends a request to
company A indicating its interest in
engaging business transaction
Step 6, company A accepts the business
arrangement and finally business
transaction occurs between the two
168493: XML and Web Services (II/2546)
12
ebXML Architectural Models

Core architectural components of ebXML






Business process
Partner profile and agreements
Registry and repository
Messaging service
Core components
ebXML is designed in a modular fashion so
that these modules can be used
individually or in a combination
168493: XML and Web Services (II/2546)
13
ebXML High-level Architecture
Business Process
Specifications
Specification
Partner Profiles
And Agreements
Registration
and
Discovery
Models
And
Profiles
Messaging Service
168493: XML and Web Services (II/2546)
14
ebXML Value Addition

Business process, CPP/CPA over WSDL


ebXML Reg/Rep over UDDI


Repository as well as registry
ebXML message service over SOAP


Defines business process collaboration
Reliability and security semantics
Core components
168493: XML and Web Services (II/2546)
15
ebXML Endorsements

Open Travel Alliance (OTA)



Open Application Group (OAGI)


Application integration and interoperability
Global Commerce Initiative (GCI)


International travel consortium
Airlines, can rental agencies, hotels, tour
operators
Consumer goods manufacturers and retailers
HL7

Healthcare
168493: XML and Web Services (II/2546)
16
Resources

ebXML home


ebXML demo


www.ebxml.org
www.sun.com/xml
www.sun.com/developers/evangcentral



All presentations
Audiocasts
Codecamp materials
168493: XML and Web Services (II/2546)
17