1. ebXML Overview Computer Industry Lab. Incheon Paik Univ. of Aizu
ebXML Overview
Computer Industry Lab.　
Incheon Paik
Lecture for TBK SE

2. ebXML Technical Architecture
Univ. of Aizu
Contents
Introduction
ebXML Overview
ebXML Technical Architecture
Lecture for TBK SE

3. Introduction Motivation e-Business through collaboration
Application Integration
Intra-Enterprise Integration : EAI
Inter-Enterprise Integration : B2Bi
How can we deal with differences among companies?
Different Semantics, Documents, Business Processes… EDI, XML, Framework

4. eBusiness Collaboration Chronology
eBC Rating
Web Service
Process
Data
Telecom.
XML/EDI
Web-EDI
EDI DX
Internet World

5. B2B Collaboration Process
Univ. of Aizu
B2B Collaboration Process
Process
Definition
Process
Evolution
Partner
Discovery
Electronic
Business
Collaboration
Process
Management
Partner
Sign-Up
Process Definition - A community of trading partners -- for example AIAG or RosettaNet -- define the business processes to be used in the community. These business processes are defined according to a well know model -- “metamodel” -- are are described in agreed upon formats -- in ebXML, this is UML and XML.
Partner Discovery - Two trading partners in an electronic community or marketplace will want to do business and they will use the ebXML compliant registries to discover each other.
Partner Sign-up - Trading partners then negotiate their business level and transaction level agreements.
Electronic Plug-in - The trading partners then configure their interfaces and software business processes according to the agreed upon business processes and interface details of the collaborating partner.
Process Execution - Business services exchange documents and carry out the agreed up business processes.
Process Management - The business processes that were defined in the Process Definition phase and agreed upon in the Partner Sign-Up phase are monitored and facilitated by process management services.
Process Evolution - Participants in the electronic marketplace will evaluate their existing processes, improve them through process re-engineering, and create new processes to meet the needs of the market.
Process Evolution brings us back to Process Definition since the new processes will be defined according to the metamodel and published to the community.
Process
Execution
Electronic
Plug-in
Lecture for TBK SE

6. Some Problems From Current B2B Model
Univ. of Aizu
Some Problems From Current B2B Model
Lack of B2B Transaction Standard Model
Need for Interoperability among B2B
Need for International Transaction
Repetitive Work for Interoperability
Process Definition - A community of trading partners -- for example AIAG or RosettaNet -- define the business processes to be used in the community. These business processes are defined according to a well know model -- “metamodel” -- are are described in agreed upon formats -- in ebXML, this is UML and XML.
Partner Discovery - Two trading partners in an electronic community or marketplace will want to do business and they will use the ebXML compliant registries to discover each other.
Partner Sign-up - Trading partners then negotiate their business level and transaction level agreements.
Electronic Plug-in - The trading partners then configure their interfaces and software business processes according to the agreed upon business processes and interface details of the collaborating partner.
Process Execution - Business services exchange documents and carry out the agreed up business processes.
Process Management - The business processes that were defined in the Process Definition phase and agreed upon in the Partner Sign-Up phase are monitored and facilitated by process management services.
Process Evolution - Participants in the electronic marketplace will evaluate their existing processes, improve them through process re-engineering, and create new processes to meet the needs of the market.
Process Evolution brings us back to Process Definition since the new processes will be defined according to the metamodel and published to the community.
Deepening Ineffectiveness of B2B System
Lecture for TBK SE

7. BOV Model Sharing in eBC
Standardized Sharable Reusable
Framework Model Component
Business BP Pattern BP
Process Metamodel Catalogue
Business BI Core BI Entity
Information Metamodel Component Catalogue

8. ebXML Overview

9. ＸＭＬ used in e-Business ｅｂＸＭＬ Initiative XML diffusion Chaos to
Tower of Babel
Digital economy realization
by standardized IT infrastracture
１９９８ １９９９ ２０００ ２００１ ２００２ year
Awareness Proliferation Products Implementation
Standardization

10. Creating a Single Global Electronic Market
Univ. of Aizu
ebXML Initiative
Goal : To provide an open technical framework to enable XML to be utilized in a consistent and uniform manner for the exchange of Electronic Business data in application to application, application to person and person to application environments.
Terms : November/1999 – May/2001
　　Creating a Single Global Electronic Market　　
Participants :
ＯＡＳＩＳ，ＵＮ／ＣＥＦＡＣＴ，ＡＮＳＩ－Ｘ１２，ＤＩＳＡ，ＮＩＳＴ，ＩＳＯ－ＴＣ１５４，ＣＥＮ－ＩＳＳＳ，ＥＡＮ， ＤＩＮ，ＥＢＥＳ，ＨＬ７，ＳＷＩＦＴ，ＯＭＧ，ＯＡＧ，ＯＴＡ，ＣｏｍｍｅｒｃｅＮｅｔ，ＩＢＭ，ＳＵＮ，Ｍｉｃｒｏｓｏｆｔ， Ｏｒａｃｌｅ，ＲｏｓｅｔｔａＮｅｔ，Ａｍａｚｏｎ，ＡＩＡＧ，Ｂｏｅｉｎｇ，ＢＴ，Ｄｕｎ＆Ｂｒａｄｓｔｒｅｅｔ，Bank-of-America， ＪＩＰＤＥＣ，Ｔａｉｐｅｉ－ＩＩＩ，KIEC．．．．．．
Lecture for TBK SE

11. E-Business Framework Document Transaction Process : BP
Electronic Document : e-Document, e-Catalog
Directory Service : Registry & Repository
Electronic Transaction : Profile, Service, Partner
Messaging : Transport, Routing, Messaging Format
Security : Encryption, Decryption, Authentication

12. e-Business Elements Business Process Electronic Document Vocabulary
Univ. of Aizu
e-Business Elements
Business Process
Recognize BP by System, Management, Supervising BP, and Process Transactions
Electronic Document Vocabulary
Standardization of vocabularies which will be used in electronic document, and Consider re-usability and extensibility
Directory Service
Searching and Retrieval of Goods or Enterprises which will trade
Electronic Profile and Agreement
Well-Define of Company Profile and Electronic Agreement. Let information systems between trading partners be interoperable
Messaging
Transport electronic documents and messages to receivers securely
Security
Secure Transaction
Lecture for TBK SE

13. Other e-Business Framework
Univ. of Aizu
Other e-Business Framework
cBL, RosettaNet
RosettaNet : Business Standard Based on XML for IT and Electronics Industry SCM
RosettaNet
Dictionary
RosettaNet Implementation Framework (RNIF)
Partner Interface Process (PIP)
Common Set of Terms, Products, Industry Code of PIP
RNIF
Guideline for System Development, Communication Protocol, and Security
PIP
Upper Layer : Cluster
Middle Layer : Segment
Lower Layer : PIP
Lecture for TBK SE

14. ebXML Contents Requirements
Requirements for business, technology, organization, and procedures
Business Process
Standards for business transaction
Core Component
Standards for reusable document
Registry and Repository
Register and Search the sharing information
Trading Partner
Standard for information of trading partners
Transport/Routing and Packaging
Secure message transport

15. ebXML 1st Step Project Organization
Univ. of Aizu
ebXML 1st Step Project Organization
ebXML
Assembly
Executive Committee
Operational Committee
Req.
T. A.
B. P.
C. C.
T. P.
R.R.
T.R.P.
P.O.C.
Quality
Marketing
Lecture for TBK SE

16. ebXML 2nd Step Project Organization
Univ. of Aizu
ebXML 2nd Step Project Organization
ebXML
OASIS
UN/CEFACT
Management Group
R.R.
T.R.P.
T. P.
P.O.C.
B. P.
C. C.
Lecture for TBK SE

17. The First ebXML Work Result
Univ. of Aizu
The First ebXML Work Result
Lecture for TBK SE

18. e-Business Collaboration on Open-edi Reference Model
Univ. of Aizu
e-Business Collaboration on Open-edi Reference Model
BOV Related Standards
Business Transaction
Business Operational View
Functional Service View
Business aspects of Business transaction
IT aspects of Business Transaction
FSV Related Standards
Lecture for TBK SE

19. BP and Info Modeling Architecture
Univ. of Aizu
BP and Info Modeling Architecture
Patterns
Patterns
Business Process Modeling
Information Modeling
Content
Content
Methodology
Methodology
BP-Metamodel
Info-Metamodel
BP-model
Info-model
Model-XML Rules
Conversion to XML
Conversion to XML
Model-XML Rules
XML BP-DTD
XML Info-DTD
XML BP-doc
XML Info-doc
Registry
Lecture for TBK SE

20. ebXML Architecture Business Process Business Document Core Components
ReferenceTo
Core
Components
BuiltWith
ContextFor
Repository
Register
Fill one Role
Profile
Fill other Role
Profile
Agreement
agree
Business
Service
Business
Service
Collaboration
Transport
Message

21. Business Transaction Requesting Activity Responding Activity Success
Unit of Work
Requesting
Activity
Responding
Activity
Request Document
Non-Repudiation
Non-Repudiation
SignedReceipt
Response Document
Success
Failure
Time-Outs
Legally Binding

22. Core Component（ＣＣ） Party Party identifier Name Address Zip code State
City
Building
Core Component
Business Process
Context
Internal system
Scenario
Business Objects
Methods
Attributes ＣＣ
Message exchange ＣＣ

23. Registry & Repository Other Registry Other Registry Company Profiles
Standard Elements
CPA Negotiation
Software Development
Standard Development
* Standard Elements
　　Process Paterns Messages
　　Core Component Software Packages
　　Common Business Objects
ebXML Implementation

25. Messaging Service ebXML Applications Based on SOAP
Message Service Interface
Based on SOAP
Message Service Management
Error Handling
ebXML Message Envelope (MIME)
Header Envelope (MIME)
Header Information (XML)
Message Envelope (MIME)
Payload
Security
Communication Interface
HTTP
SMTP
IIOP
FTP
Other

26. ebXML Technical Architecture
Univ. of Aizu
ebXML Technical Architecture
Lecture for TBK SE

27. ebXML System Overview – Scenario 1
compliant
system
Business Profiles
Business Scenarios
Registry
XML
Request Business Details 1
Build Local System
Implementation
Register Implementation Details
Register COMPANY A Profile 3 2 5
Agree on Business Arrangement 4
Query about COMPANY A profile
Download
Scenarios and Profiles 6
COMPANY A
COMPANY B
ebXML
compliant
system
Business Profiles
Business Scenarios
ebXML
Registry
XML
XML
Business Scenarios 1 1
Business Profiles
COMPANY A
COMPANY A
Request Business Details
Request Business Details 2 2
Build Local System
Build Local System
ebXML
Implementation
Implementation 3 3
Register Implementation Details
Register Implementation Details
Registry
Register COMPANY A Profile
Register COMPANY A Profile
Download
Download 4 4
Query about COMPANY A profile
Query about COMPANY A profile
Agree on Business Arrangement
Agree on Business Arrangement
Scenarios and Profiles
Scenarios and Profiles 5 5
DO BUSINESS TRANSACTIONS 6 6
COMPANY B
COMPANY B
ebXML
compliant
system
A high level overview of the interaction of two companies conducting eBusiness using ebXML

28. Usage Example Company X ebXML Software ebXML Software Company Y ebXML
Univ. of Aizu
Usage Example
Company X
Request ebXML specifications 1 2
ebXML specifications detail
ebXML
Repository
ebXML
Software
Register scenarios and implementation details
Register company business profile 4
ebXML BO Library 5 3
Confirm profile and scenarios accepted
ebXML BP Model
Specifications
Build local system
implementation
Profiles 12
Query about Company X 7 9
Accept CPA
Scenarios DO
BUSINESS!
Company X’s Profile 8
Submit CPA 6
INDUSTRY INPUT
Request Company X’s Scenario 11
Company X has become aware of ebXML and that there is a repository that contains the ebXML specifications.
1. Company X request from the repository the specification in order to determine if it was to become a ebXML compliant participant.
2. The request results in the specification be send to Company X
3. Company X, after reviewing the specification, decides to build its own ebXML compliant application.
4. After completing the creation of the ebXML application, Company X send a request to upload its company profile (for discovery of its ebXML capabilities and constrains) as well as its scenarios. These scenarios as XML versions of the business processes and associated information parcels (based on Business Objects) the company is able to engage in.
5. After verification that the format and usage of BO is correct a acknowledgment is send to Company X.
6. Company Y (a SME) was informed by Company X that they like to engage in a business transaction using ebXML. Company Y finds a shrink-wrap application that is ebXML compliant and interfaces with its current PC based accounting and inventory applications. The ebXML program has already the base ebXML information such as a library of BO and models for the specific industry they are part of. However, since Company X just registered is scenarios they are not part of the purchased package. Therefore the program queries the ebXML repository about Company X.
7. Company X’s profile is provided.
8. Based on the profile the program determines that it is able to execute a certain scenario specified by Company X. Before engaging in that the scenario Company Y submits to Company Y the trading partner agreement (TPA) which outlines the scenario it wants to use with company X as well as certain transport and security related requirements.
9. The TPA is accepted by Company X and an acknowledgement is send.
10. Since the scenario from company X was not available in the software package that Company Y is using, the program requests it from the repository.
11. The scenario is being provided to company’s Y application.
12. Based on the processes (as contained in the process models) and information parcels (as presented in the class diagrams) Company X and Y are now engaging in eBusiness utilizing ebXML specifications. 10
Company X’s Scenario
ebXML
Software
Company Y
ebXML BO Library
ebXML BP Model
Lecture for TBK SE

29. Scenario 2
Three or more partners set-up a Business Process implementing a supply-chain and run the associated exchanges
Party 1
Party 2
Party 3

30. Scenario 3
A Company sets up a Portal which defines a Business Process involving the use of external business services
Partner1
Partner2
Partner3
Service
Provider
Client

31. Scenario 4
Three or more parties engage in multi-party Business Process and run the associated exchanges
Service
Provider
Client
Mail
Delivery
Company

32. ebXML Recommended Modeling Methodology
UN/CEFACT Modeling Methodology
Provide a clear distinction to ensure the maximum level of system interoperability and back wards compatibility with legacy systems.

33. ebXML Business Operational View
The semantics of business data in transactions and associated data interchanges
The architecture for business transactions, including
Operational conventions
Agreements and arrangements
Mutual obligations and requirements
Business Collaboration
Knowledge
Analysis Artifacts
Sequence Diagrams
Collaboration Diagrams
Design Artifacts
State Diagrams
Final Class Diagrams
Activity Diagrams
Conceptual Diagrams
Based on ebXML Meta Model
Core Library
Business Processes
Business Library
Core & Aggregate
Components
Business Context
Use Case Diagrams
Use Case Descriptions
Requirements Artifacts
Business Process and Information Models
(Compliant to the ebXML Meta Model)

34. ebXML Functional Service View
Functional capabilities
Business Service Interfaces
Protocols and
Messaging Services

35. ebXML Functional Phases [1]
Implementation Phase

36. ebXML Functional Phases [2]
Discovery and Retrieval Phase

37. ebXML Functional Phases [3]
Run Time Phase

38. ebXML Infrastructure Trading Partner Information [CPP and CPA’s]
Business Process and Information Modeling
Core Components and Core Library Functionality
Registry Functionality
Messaging Service Functionality

39. Trading Partner Information
Collaboration Protocol Profile (CPP)
A document which allows a Trading Partners to express their supported Business Processes and Business Service Interface requirements in a manner where they can be universally understood by other ebXML compliant Trading Partners.
Collaboration Protocol Agreement (CPA)
A document that represents the intersection of two CPP’s and is mutually agreed upon by both Trading Partners who wish to conduct eBusiness using ebXML.
The Messaging Service
The Business Process requirements that are agreed upon by two or more Trading Partners

40. Business Process and Information Modeling [1]
Business Process and Information Meta Model
A mechanism that allows Trading Partners to capture the details for a specific business scenario using a consistent modeling methodology.
Business Process <- {Business Transactions} <- {Business Documents} <- {Business Information Objects} <- {Core Components}

41. Business Process and Information Modeling [2]
ebXML Meta Model
ebXML Meta
Model
Semantic
Subset
Specification Schema
Production Rules
Specification Schema
(UML)
(DTD)
Interaction Patterns
Common Modeling Elements
Core Components
CPP
CPA
TP Document DTD’s

42. Business Process and Information Modeling [3]
ebXML Business Process and Information Modeling Layer
Business Document
Trading
Partner
Business Context
Core Processes
Aggregate Information
Entities/Core Components
Core Library
Business Processes
Business Information
Business Library

43. Core Components and Core Library Functionality [2]
Business Context
Core Component
Core
Component
Aggregate
Information Entity
Context
Business Context defined in terms of Aggregate Context, Aggregate Information Entities, and Core Components

44. Registry Functionality [3]
Content
XML Content Referencing
Access Index
Interface
Information
Model
Associated References
Registration of
Domain
Classification & Ownership
ebXML conformant XML object
Collections & Versioning
Transport
Layer
Request
Response
Detail Constraints
Industry Domain
Business Process
Details Content
Action Status
Registry Service Interface
Other Registry
Service Interface(s):
UDDI, CORBA
Compatibility Wrappers
Registry
Services
Access
Syntax
in XML
Remote ebXML
Repository

45. Messaging Service Functionality [1]
Provides a standard way to exchange business Messages among ebXML Trading Partners.
An abstract Service Interface
Functions provided by the Messaging Service Layer
The mapping to underlying transport service
ebXML Messaging Service

46. Messaging Service Functionality [2]
The Messaging Service Architecture

47. Messaging Service Functionality [3]
Provides a secure, consistent and reliable mechanism to exchange ebXML Messages between users of the ebXML infrastructure over various transport Protocols (possible examples include SMTP, HTTP/S, FTP, etc).
Prescribes formats for all Messages between distributed ebXML Components including Registry mechanisms and compliant user Applications.
Does not place any restrictions on the content of the payload.
Supports simplex (one-way) and request/response (either synchronous or asynchronous) Message exchanges.
Supports sequencing of payloads in instances where multiple payloads or multiple Messages are exchanged between Trading Partners governed by CPA.

48. Messaging Service Functionality [4]
ebXML Message Structure