ebXML Registry and Repository Dept of Computer Engineering Khon Kaen University

168493: XML and Web Services (II/2546) 2 Why We Need a Registry? To securely store shared information that is submitted and owned by various parties To identify, name, describe, classify, relate, group, and annotate shared information To query, discover, and retrieve shared information from the registry

168493: XML and Web Services (II/2546) 3 Goals of ebXML Registry To enable sharing of information between interested parties for the purpose of enabling business process integration between such parties

168493: XML and Web Services (II/2546) 4 Registry vs. Repository Registry A set of services for sharing of information Catalog of things Uses repository internally Repository Storage for shared information Holder of things Implementation dependent

168493: XML and Web Services (II/2546) 5 ebXML Registry Specifications Registry services specification Registry services Interaction protocols Message definitions XML schema Registry information model Types of metadata Relationship among metadata classes

168493: XML and Web Services (II/2546) 6 Registry Use Case Scenario 1. Schema documents are submitted 2. Business process documents are submitted 3. Seller’s CPP is submitted. The seller publishes its Collaboration Protocol Profile or CPP as defined by to the Registry. The CPP describes the seller, the role it plays, and the services it offers

168493: XML and Web Services (II/2546) 7 Registry Use Case Scenario 4. Buyer browses, discovers seller’s CPP The buyer browses the Registry using Classification schemes defined within the Registry using a Registry Browser GUI tool to discover a suitable seller The buyer discovers the seller’s CPP and decides to engage in a partnership with the seller 5. CPA is established The buyer unilaterally creates a CPA as defined by with the seller using the seller’s CPP and their own CPP The seller accepts the proposed CPA

168493: XML and Web Services (II/2546) 8 ebXML Registry Conforms to ebXML Registry Information Model Supports syntax and semantics of registry interfaces and security model Supports defined ebXML Registry DTD Optionally support SQL query

168493: XML and Web Services (II/2546) 9 ebXML Registry Client Supports ebXML CPA and bootstrapping process Communicates with ebXML Registry using ebXML Message Service Supports the syntax and the semantics of the Registry Client Interfaces

168493: XML and Web Services (II/2546) 10 ebXML Registry Security Protect integrity of contents Digital digest Authenticate identifies of users Digital certificate and signature Per-request basis for now (no session) Control access to contents for predefined roles

168493: XML and Web Services (II/2546) 11 Security Roles: Different Levels of Access Privileges Content owner Has access to all procedures on the contents he owns Registry administrator Has access to all procedures on all registry objects Registry guest Unanthenticated visitors Has only read-only access

168493: XML and Web Services (II/2546) 12 ebXML Reg/Rep Value Addition over UDDI Repository as well as registry UDDI is a Yellow Pages-like registry that has no repository, or database, for storing company information as the ebXML registry/repository does ebXML registry/repository can be hosted by any company UDDI registry are hosted by specific companies, such as IBM and Microsoft

168493: XML and Web Services (II/2546) 13 ebXML Reg/Rep Value Addition over UDDI Can store user-defined information Supports both synchronous and asynchronous interaction model Life-cycle support of registry items Uses secure and reliable ebXML Message Service