EbXML Overview Computer Industry Lab. Incheon Paik.
-
Upload
calvin-cox -
Category
Documents
-
view
214 -
download
1
Transcript of EbXML Overview Computer Industry Lab. Incheon Paik.
ebXML Overview
Computer Industry Lab.
Incheon Paik
22ebXML Univ. of Aizu
Contents
Introduction
ebXML Overview
ebXML Technical Architecture
33ebXML Univ. of Aizu
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
44ebXML Univ. of Aizu
eBusiness Collaboration Chronology
eBC Rating
Process
Data
Telecom.
EDI
Web-EDIXML/EDI
Web Service
DX
Internet World
55ebXML Univ. of Aizu
ElectronicElectronicBusinessBusiness
CollaborationCollaboration
ElectronicElectronicBusinessBusiness
CollaborationCollaboration
ProcessDefinition
PartnerDiscovery
PartnerSign-Up
ElectronicPlug-in
ProcessExecution
ProcessManagement
ProcessEvolution
B2B Collaboration Process
66ebXML 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
Deepening Ineffectiveness of B2B System
77ebXML Univ. of Aizu
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
88ebXML Univ. of Aizu
ebXML Overview
99ebXML Univ. of Aizu
XML used in e-Business
1998 1999 2000 2001 2002 year
Awareness Proliferation Products Implementation
Standardization
Digital economy realization
by standardized IT infrastracture
Chaos to
Tower of Babel
ebXML InitiativeXML
diffusion
1010ebXML 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 :OASIS,UN/CEFACT,ANSI-X12,DISA,NIST,ISO-TC154,CEN-ISSS,EAN, DIN,EBES,HL7,SWIFT,OMG,OAG,OTA,CommerceNet,IBM,SUN,Microsoft, Oracle,RosettaNet,Amazon,AIAG,Boeing,BT,Dun&Bradstreet, Bank-of-America , JIPDEC,Taipei-III, KIEC ......
1111ebXML Univ. of Aizu
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
1212ebXML 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
1313ebXML 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)
Dictionary 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
1414ebXML Univ. of Aizu
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 PartnerStandard for information of trading partners
Transport/Routing and PackagingSecure message transport
1515ebXML Univ. of Aizu
ebXML 1st Step Project Organization
ebXML
Assembly
Operational Committee Executive Committee
Req.
T. A
.
B. P
.
C. C
.
T. P
.
R.R
.
T.R
.P.
P.O
.C.
Quality
Marketing
1616ebXML Univ. of Aizu
ebXML 2nd Step Project Organization
ebXML
Management Group
OASIS UN/CEFACTB
. P.
C. C
.
T. P
.
R.R
.
T.R
.P.
P.O
.C.
1717ebXML Univ. of Aizu
The First ebXML Work Result
1818ebXML Univ. of Aizu
Business Operational View
Functional Service
View
e-Business Collaboration on Open-edi Reference Model
Business aspects of Business transaction
IT aspects of Business Transaction
BOV
Related
Standards
FSV
Related
Standards
Bu
siness
Tran
saction
1919ebXML Univ. of Aizu
BP and Info Modeling Architecture
Registry
Conversion to XML
XML BP-DTD XML Info-DTD
Model-XML Rules Model-XML Rules
XML BP-docXML BP-doc
Conversion to XML
XML Info-docXML Info-doc
InformationModeling
InformationModeling
Info-MetamodelInfo-MetamodelInfo-model
MethodologyMethodology
ContentContent
PatternsPatterns
BP-MetamodelBP-Metamodel BP-model
MethodologyMethodology
ContentContent
PatternsPatternsBusiness Process Modeling
Business Process Modeling
2020ebXML Univ. of Aizu
ebXML Architecture
BusinessService
Repository
Register
CoreComponentsBuiltWith
Fill one Role
Profile
Fill other Role
Profile
BusinessProcess
BusinessDocument
ReferenceTo
Transport
Message
Agreementagree agree
BusinessService
ContextFor
Collaboration
2121ebXML Univ. of Aizu
Business Transaction
RequestingActivity
RespondingActivity
Request Document
Response Document
Success Failure
Unit of Work
Non-Repudiation
Non-Repudiation
Time-Outs
Legally Binding
SignedReceipt
2222ebXML Univ. of Aizu
Core Component (CC)
Party
Party identifier
Name
Address Zip code
State
City
Building
Context
Internal system
Scenario
Business Objects
Methods
AttributesMessage exchange
CC
CC
Core Component
2323ebXML Univ. of Aizu
Registry & Repository
Company Profiles
Standard Elements
Standard Development
Software Development
ebXML Implementation
CPA Negotiation
Other Registry
* Standard Elements
Process Paterns Messages
Core Component Software Packages
Common Business Objects
Other Registry
2424ebXML Univ. of Aizu
Collaboration-Protocol Agreements (CPA)
CPA ID
Party’s information
- Party A
- Party B
Transport Protocol
Transport Security
DocExchange Protocol
Link to Process-
Specification Doc.
Retry
-etc.
CPPFor
Party A
CPPFor
Party B
CPA
AgreedCPA
AgreedCPA
1
negotiate
2
negotiate
3
Agree-ment on CPA has arrived.
3
Agree-ment on CPA has arrived.
4 Start Business activities with each other
2525ebXML Univ. of Aizu
Messaging Service
ebXML Applications
Message Service Interface
ebXML Message Envelope (MIME)
Header Envelope (MIME)
Header Information (XML)
Message Envelope (MIME)
Payload
Security
Communication Interface
HTTP SMTP IIOP FTP Other
Message S
ervice M
anagem
ent
Error H
and
ling
Based on SOAP
2626ebXML Univ. of Aizu
ebXML Technical Architecture
2727ebXML Univ. of Aizu
ebXML System Overview – Scenario 1
ebXML compliantsystem
Business ProfilesBusiness Scenarios
ebXMLRegistry
XML
Request Business Details
1
Build Local SystemImplementation
Register Implementation DetailsRegister COMPANY A Profile
3
2
5 Agree on Business Arrangement4
Query about COMPANY A profile
DownloadScenarios and Profiles
6
COMPANY A
COMPANY B
ebXML compliantsystem
Business ProfilesBusiness Scenarios
ebXMLRegistry
XML
Request Business Details
1
Build Local SystemImplementation
Register Implementation DetailsRegister COMPANY A Profile
3
2
5Agree on Business Arrangement4
Query about COMPANY A profile
DownloadScenarios and Profiles
DO BUSINESS TRANSACTIONS
6
COMPANY A
COMPANY B
ebXML compliantsystem
Business ProfilesBusiness Scenarios
ebXMLRegistry
XML
Request Business Details
1
Build Local SystemImplementation
Register Implementation DetailsRegister COMPANY A Profile
3
2
5 Agree on Business Arrangement4
Query about COMPANY A profile
DownloadScenarios and Profiles
6
COMPANY A
COMPANY B
A high level overview of the interaction of two companies conducting eBusiness using ebXML
Query about Company X
Request Company X’s S
cenarioDO BUSINESS!
Company X’s Scenario
Company X’s Profile
Submit CPA
Accept CPA
Usage Example
INDUSTRY INPUT
ebXML BP Model
ebXML BO Library
ebXML BP Model
ebXML BO Library
Request ebXML specifications1
ebXML specifications detail
3
2
Build local system implementation
Register scenarios and implementation detailsRegister company business profile
6
7
8
9
10
Confirm profile and scenarios accepted
11
4
5
12 Scenarios
Profiles
Specifications
2929ebXML Univ. of Aizu
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
3030ebXML Univ. of Aizu
Scenario 3
A Company sets up a Portal which defines a Business Process involving the use of external business services
Partner1 Partner2 Partner3
ServiceProvider
Client
3131ebXML Univ. of Aizu
Scenario 4 Three or more parties engage in multi-
party Business Process and run the associated exchanges
ServiceProvider
Client
MailDeliveryCompany
3232ebXML Univ. of Aizu
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.
Business Operational View
Functional Service View
Comply with
Covered by
Comply with
Covered by
Business aspects of
business transactions
Information technology aspects of
business transactions
BOV RELATED
STANDARDS
FSV RELATEDSTANDARDS
Viewedas
Interrelated
BUSINESS
TRANSACTIONS
Business Operational View
Functional Service View
Comply with
Covered by
Comply with
Covered by
Business aspects of
business transactions
Information technology aspects of
business transactions
BOV RELATED
STANDARDS
FSV RELATEDSTANDARDS
Viewedas
Interrelated
BUSINESS
TRANSACTIONS
3333ebXML Univ. of Aizu
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 CollaborationKnowledge
Analysis Artifacts
Sequence Diagrams
Collaboration Diagrams
Design Artifacts
State Diagrams
Final Class Diagrams
Activity Diagrams
Conceptual Diagrams
State Diagrams
Based on ebXML Meta Model
Core Library
Business Processes
Business LibraryCore Library
Core & AggregateComponents
Business Library
Business Context
Use Case Diagrams
Use Case Descriptions
Requirements Artifacts
Business Process and Information Models(Compliant to the ebXML Meta Model)
3434ebXML Univ. of Aizu
ebXML Functional Service View
Functional capabilities
Business Service Interfaces
Protocols and
Messaging Services
Registration
Business Process and Information Models(Compliant to the ebXML Meta Model)
Model to XML Conversion
InternalBusiness
Application
Implementers
Retrieval of Profiles &new/updated ebXML Models
Retrieval of Profiles &new/updated ebXML Models
RegisterCollaboration
Protocol Profile(CPP)
Retrieval of ebXMLModels and Profiles
Build Build
CollaborationProtocol
Agreement (CPA)
Payload
CPA
Gov
erns
CPP
Business ServiceInterface
InternalBusiness
Application
Business ServiceInterface
Registry ServiceInterface
Registries
RegisterCollaboration
Protocol Profile(CPP)
3535ebXML Univ. of Aizu
ebXML Functional Phases [1]
Implementation Phase
TradingPartner
Request
ReceiveUpdate
ebXMLRegistry
BusinessProcess &InformationMeta Models
Core Library
BusinessLibrary
CollaborationProtocol Profiles
3636ebXML Univ. of Aizu
ebXML Functional Phases [2]
Discovery and Retrieval Phase
Request
ReceiveUpdate
Send
Receive
ebXMLRegistry
Trading Partner
Trading Partner
List ofScenarios
MessagingConstraints
SecurityContstraints
BusinessProcess &InformationMeta Models
Core Library
BusinessLibrary
CollaborationProtocol Profiles
3737ebXML Univ. of Aizu
ebXML Functional Phases [3]
Run Time Phase
Send
Receive
Trading Partner Trading Partner
3838ebXML Univ. of Aizu
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
3939ebXML Univ. of Aizu
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
4040ebXML Univ. of Aizu
Business Process and Information Modeling [1]
Business Process and Information Meta ModelA 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}
4141ebXML Univ. of Aizu
ebXML Meta ModelebXML Meta
Model
Specification Schema(UML)
Specification Schema(DTD)
SemanticSubset
Interaction Patterns Common Modeling Elements
Production Production RulesRules
Core Components
CPPCPP CPACPA
TP Document DTD’sTP Document DTD’s
Business Process and Information Modeling [2]
4242ebXML Univ. of Aizu
ebXML Business Process and Information Modeling Layer
Business Document
TradingPartner
TradingPartner
Business Context
Core Processes
Aggregate Information
Entities/Core Components
Core Library
Business Processes
Business Information
Business Library
Business Process and Information Modeling [3]
4343ebXML Univ. of Aizu
Business Context
Core Component
Core
Component
Core
Component
Aggregate
Information Entity
Core Component
Aggregate
Context
Context
Core Component
Core
Component
Component
Aggregate
Context
Aggregate
Information Entity
Core
Component
Core
Component
CoreCore Component
Core Component
Core Component
Business Context defined in terms of Aggregate Context, Aggregate Information Entities, and Core Components
Core Components and Core Library Functionality [2]
4444ebXML Univ. of Aizu
Registry Functionality [3]
Content
XML Content ReferencingAccess Index
Interface Information Model
Associated References
Registration of Domain
Classification & Ownership
ebXML conformant XML objectCollections & Versioning
TransportLayer
Request Response
Detail Constraints
Industry DomainBusiness Process
Details Content
Action Status
Registry Service InterfaceOther Registry
Service Interface(s): UDDI, CORBA
Compatibility Wrappers
Registry Services
Access Syntax in XML
Remote ebXMLRegistry
Registry
Repository
4545ebXML Univ. of Aizu
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
Abstract ebXML Messaging Service Interface
EbXML Messaging Service Layer mapsthe abstract interface to the underlying
transport service
Transport Service(s)
ebXML Messaging Service
4646ebXML Univ. of Aizu
Messaging Service Functionality [2] The Messaging Service Architecture
HTTP SMTP IIOP FTP …
ebXML Applications
Messaging Service I nterface
Messaging Service
Authentication, authorization andrepudiation services
Header Processing
Encryption, Digital Signature
Message Packaging Module
Delivery ModuleSend/Receive
Transport Mapping and Binding
4747ebXML Univ. of Aizu
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.
4848ebXML Univ. of Aizu
Messaging Service Functionality [4] ebXML Message Structure
Transport Envelope (SMTP, HTTP, etc.)
ebXML Message Envelope (MIME multipart/related)
ebXML Header Envelope
ebXML Header Document
ebXML Payload Envelope
Payload Document(s)ebXMLPayload
Container
Manifest
Header
ebXMLHeader
Container