eb XML Registry and Repository Dept of Computer

eb. XML Registry and Repository Dept of Computer Engineering Khon Kaen University 168493: XML and Web Services (II/2546)

Why We Need a Registry? n n n 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) 2

Goals of eb. XML Registry n 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) 3

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

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

Registry Use Case Scenario Schema documents are submitted Business process documents are submitted Seller’s CPP is submitted. 1. 2. 3. n n 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) 6

Registry Use Case Scenario Buyer browses, discovers seller’s CPP 4. n n 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 CPA is established 5. n n 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) 7

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

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

eb. XML Registry Security n Protect integrity of contents n n Authenticate identifies of users n n n Digital digest 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) 10

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

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

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