1. UDDI Ashish Jain University of Colorado 3 October, 2001

2. What is UDDI ?  Stands for Universal Description, Discovery and Integration  Defines a way to publish and discover information about web services  “Web service” describes specific business functionality to be used by another company.  Joint industry effort initiated by Microsoft and Ariba.  Not a standard

3. Motivation  No single point of access to all markets of opportunity. Difficult for a business to find services that meet requirements.  Lack of standard mechanism to figure out how to conduct electronic business with remote partner

4. Objectives  To enable businesses to quickly and dynamically discover and interact with each other on the Internet.  Programmatically describe their services and business processes and their preferred methods for conducting business.  Simplify the effort of integrating disparate business processes  Advertise its business and services in a global registry

5. A mid-sized manufacturer needs to create 400 online relationships with customers, each with their own set of standard and protocols Broader B2B A flower shop in Australia wants to be “plugged in” to every marketplace in the world, but doesn’t know how Smarter Search A B2B marketplace cannot get catalog data for relevant suppliers in its industry, along with connections to shippers, insurers, etc. Easier Aggregation Describe Services Discover Services Integrate Them Together Overview

6. Technical View Common Internet Protocols (HTTP, TCP/IP) Extensive Markup Language ( XML ) Simple Object Access Protocol ( SOAP ) UDDI  An XML file describes a business entity and its services to UDDI Business Registry  Access to and from the Business Registry is described by SOAP  UDDI defines the framework of describing any kind of Web service.

7. How does UDDI work ? Business Registrations Businesses populate the registry with descriptions of the services they support 2.2. Service Type Registrations SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services 1.1. Marketplaces, search engines, and business apps query the registry to discover services at other companies 4.4. Business uses this data to facilitate easier integration with each other over the Web 5.5. 3.3. UBR assigns a programmatically unique identifier to each service and business registration

8. UDDI Business Registry  Business individually register information about the Web services to it.  Provides programmatic description of web services  Physically distributed with multiple root nodes  Data replicated on each server

9. Registry Data  Businesses register public information about themselves. White pages address, contact and known identifies Yellow pages contains industrial categorization Green pages Technical information about the services that are exposed by the businesses  Standards bodies, Programmers, Businesses register information about their Service Types

10. Structure name, contacts, descriptions, categories (1..n) Name Description URL pointers  Business Entity is a top level information manager for the business unit – serves as white and yellow pages

11. Structure (II)  Business service and binding template define the green pages  businessService structure describes a group of related Web services  bindingTemplate consists of the information required to invoke services.  tModel contains information about specification supported for compatibility.

12. Inquiry API  Find things find_business find_service find_binding find_tModel  Get Details about things get_businessDetail get_serviceDetail get_bindingDetail get_tModelDetail

13. Inquiry example  find_business  Syntax: [findQualifiers/] [  Result : List of businesses matching the criteria

14. Conclusions  Significant benefits for B2B eCommerce  Open process with clear roadmap to a standards body  Industry momentum