1 / 76

ebXML Overview

ebXML Overview. Computer Industry Lab. Incheon Paik. Contents. Introduction ebXML Overview ebXML Technical Architecture ebXML Business Process Specification. ebXML Overview. ＸＭＬ used in e-Business. XML diffusion. ｅｂＸＭＬ Initiative. Chaos to Tower of Babel.

gunnar
Download Presentation

ebXML Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ebXML Overview Computer Industry Lab. Incheon Paik

  2. Contents • Introduction • ebXML Overview • ebXML Technical Architecture • ebXML Business Process Specification

  3. ebXML Overview

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

  5. 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．．．．．．

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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.

  11. 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

  12. BP and Info Modeling Architecture Patterns Patterns Business Process Modeling InformationModeling Content Content Methodology Methodology BP-Metamodel Info-Metamodel BP-model Info-model Model-XML Rules Model-XML Rules Conversion to XML Conversion to XML XML BP-DTD XML Info-DTD XML BP-doc XML Info-doc Registry

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

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

  15. 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 ＣＣ

  16. 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

  17. Messaging Service ebXML Applications 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

  18. ebXML Technical Architecture

  19. XML XML Business Scenarios Business Scenarios 1 COMPANY A Business Profiles Business Profiles Request Business Details 2 Build Local System Implementation ebXML ebXML 3 Register Implementation Details Registry Registry Register COMPANY A Profile Download 4 Query about COMPANY A profile Agree on Business Arrangement Scenarios and Profiles 5 6 COMPANY B ebXML ebXML compliant compliant system system ebXML System Overview – Scenario 1 XML Business Scenarios 1 1 COMPANY A COMPANY A Business Profiles Request Business Details Request Business Details 2 2 Build Local System Build Local System Implementation Implementation ebXML 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

  20. Usage Example Company X Request ebXML specifications 1 2 ebXML specifications detail ebXML Repository Register scenarios and implementation details Register company business profile ebXML Software 4 ebXML BO Library 5 Confirm profile and scenarios accepted 3 ebXML BP Model Specifications Build local system implementation Profiles 12 7 Query about Company X Accept CPA 9 Scenarios DO BUSINESS! Company X’s Profile Submit CPA 8 6 INDUSTRY INPUT Request Company X’s Scenario 11 Company X’s Scenario 10 ebXML Software ebXML BO Library Company Y ebXML BP Model

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

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

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

  24. 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.

  25. 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 Based on ebXML Meta Model Business Context Core Library Core Library Business Library Business Library Core & Aggregate Business Processes Components Business Collaboration Knowledge Design Artifacts Analysis Artifacts Requirements Artifacts Activity Diagrams Collaboration Diagrams Use Case Diagrams Sequence Diagrams State Diagrams State Diagrams Use Case Descriptions Conceptual Diagrams Final Class Diagrams Business Process and Information Models (Compliant to the ebXML Meta Model) ebXML Business Operational View

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

  27. 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

  28. 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

  29. Others • ebXML Core Component • ebXML Repository and Registry • ebXML Messaging

  30. ebXMLBusiness Process Computer Industry Lab. Incheon Paik

  31. Business Process, Transaction, Collaboration

  32. Analysis of BP & BI (Activities)

  33. Analysis of BP & BI

  34. Analysis of BP Activities

  35. Modeling, Conversion to XML, and Registration Activity Flow

  36. Overview of Mapping from Worksheets to Metamodel

  37. Direct To Customer Retail Transaction and Physical Goods Flow Overview

  38. BP Methodology

  39. Business Operations Map (BOM) <<BusinessOperationsMap>> ebXML Common Business Operations <<BusinessOperationsMap>> Automotive Business Operations Business Operations Map <<BusinessArea>> Manufacturing Business Area Diagram <<ProcessArea>> Materials Management (from Manufacturing) Process Area Diagram Business Process Diagram

  40. Replenish Products Biz. Process Diagram Supplier Customer (from Materials Management) (from Materials Management) <<BusinessCollaboration>> <<BusinessCollaboration>> <<BusinessProcess>> Ship Products Authorize Action Replenish Products <<CommercialTransaction>> <<CommercialTransaction>> <<CommercialTransaction>> Notify of Shipment <<CommercialTransaction>> Authorize Shipment Notify of Delivery Exceptions Authorize Fabrication <<CommercialTransaction>> <<CommercialTransaction>> Authorize Raw Materials Notify of Shipment Receipt

  41. Business Process (Negotiate Contract) • Traceability Identifier: ebxml:Manufacturing.MaterialsManagement$0.1:NegotiateContract • Actors: Customer and Supplier • Pre-Conditions • Begins-When • Definition • Ends-When • Exceptions • Post-Conditions • Traceability

  42. Biz. Requirements View (BRV) • To specify the business collaborations, commercial transactions, partner types, agreements, economic contracts, commitments, and economic events <<BusinessCollaboration>> Authorize Action <<Commitment>> +Materials Manager RawMaterialAuthorization realization <<functional>> resultsIn +Fabricator <<functional>> <<functional>> +Production Scheduler Supplier Authorize Action - collaboration Customer (from Materials Management) (from Materials Management) +Shipper <<organizational>> resultsIn resultsIn <<Commitment>> <<Commitment>> FabricationAuthorization ShipmentAuthorization Authorize Action Biz. Collaboration Diagram

  43. Biz. Transaction View (BTV) • To specify the semantics of business information entities and their flow of exchange between roles as they perform business activities [ ProductDemand.IsRawMaterialAuthorized() = True ] <<CommercialTransactionActivity>> START Authorize Raw Materials [ exception.type = CONTROL ] [ AcceptanceAcknowledgment ] [ ProductDemand.IsFabricationAuthorized() = True ] <<CommercialTransactionActivity>> Authorize Fabrication [ exception.type = CONTROL ] [ AcceptanceAcknowledgment ] Authorize Shipment [ ProductDemand.IsShipmentAuthorized() = True ] <<CommercialTransactionActivity>> [ exception.type = CONTROL ] Notify of Failure [ AcceptanceAcknowledgment ] END FAILED Authorize Action Biz. Collaboration Protocol

  44. Commercial Transaction (CT) Notify of Shipment CT ProductionScheduler Shipper <<NotificationActivity>> Notify of Shipment Authorization [SUCCESS] [FAIL] END FAILED <<DocumentEnvelope>> Shipment Authorization <<DocumentEnvelope>> Shipment Authorization

  45. Functional Service View (FSV) :ProductionSchedulerAgent :ProductionSchedulerService :ShipperService 1: callTxn() 2: request(ShipmentAuthorizationAction) 3: signal(ReceiptAcknowledgement) 4: return(ReceiptAcknowledgement)

  46. Methodology (Analysis) Metamodel Business Operations Map Process Category Business Process Business Requirements View Agreement Business Collaboration Partner Types Economic Event Business Operational View Request Message Roles Commercial Transaction Response Message Functional Service View Request Signal(s) Network Component ServiceTransaction Response Signal(s)

  47. BP Metamodel

  48. Metamodel Methodology Artifacts Methodology-Based BP/Info Model (UML) Specification-Based BP/Info Model (UML) Specification-Based BP/Info Model (XML Schema) CPP/CPA RegRep

  49. Specification Metamodel • To specify the aspects of ebXML B2B business processes which • must be known to both (all) parties in the process, and • can or should be directly driving software behavior on either side • Derived from the ebXML Analysis Metamodel • forming the layer that contains parameters to drive software behavior • establishing the semantics and expression of the business aspects of the Trading Partner documents: profile and agreement • providing an expression that can either be included as is in a partner agreement (thick version), or be pointed to from a partner agreement (thin version) • You may use the analysis metamodel to guide you through the construction of a specification, or you may specify it directly against the specification metamodel

More Related