1. 1 Universal Description, Discovery, and Integration (UDDI) 大葉大學資工系

2. 2 Introduction UDDI is a technical specification for describing, discovering, and integrating web services. It contains two parts: Technical specification for building a distributed directory of businesses and web services. The UDDI Business Registry (UBR) that allows users to search existing UDDI data and enable companies to register.

3. 3 UDDI Categories White Page: General information about a specific company Unique business identifier Yellow Page: General classification data for either the company or the service offered Green Page: Technical information about a web service Including a pointer to an external specification and an address for invoking the web services

4. 4 UDDI Information Model UDDI information model includes business information, business service information, binding information, service specification information, publisher assertion information

5. UDDI Architecture 5

6. 6 UDDI Information Model publisherAssertion: Information about a relationship between two parties, asserted by both. businessEntity: Information about the party who publishes information about a family of services. businessService: Descriptive information about a particular service. bindingTemplate: Technical information about a service entry point. tModel: Descriptions of specifications for services or taxonomies. Basis for technical fingerprints Relationship between two parties Encapsulates bindingTemplate Data contains references to tModels

7. 7 Publisher Assertion The information indicates the relationship between two companies. Two parties must agree to the relationship by declaring identical assertions. Relationships: Parent-child: one organization owns another. It is identified in the fromKey and toKey. Peer-peer: the organization identified in the fromKey and the one in toKey are partners. Identity: the organization identified in the fromKey is the same as the one in toKey.

8. 8 Publisher Assertion Structure EntityDescription fromKeyA required element that uniquely identifies the business that instantiates the relationship. toKeyA required element that uniquely identifies the business that accepts the relationship. keyedReferenceA required element that identifies the type of relationship.

9. publisherAssertion Structure 9

10. 10 Business Entity It encapsulates a business’s general information, such as its name, and contact information. The businessEntity structure can include optional business identifiers and business categories. Identifier uniquely identifies the company. Dun & Bradstreet D-U-N Numbers. Thomas Registry Supplier Ids. A business can belong to multiple categories. NAICS: North American Industry Classification System. UNSPSC: Universal Standard Products and Service Classsification. ISO 3166

11. 11 Business Entity Structure EntityDescription businessKeyA required attribute that contains a unique hexadecimal identifier for the business. authorizedNameAn optional attribute that contains the name of the person who published the information. operatorAn optional attribute that contains the name of the operator node with which the business registered. discoveryURLsAn optional element that contains URLs to discover documents. nameA required element that contains the name of the business. descriptionAn optional element that contains a brief description of the business. contactsAn optional element that contains the business’s contact information. businessServicesAn optional element that lists the services offered by the business. identifierBagAn optional element that contains a list of unique identifiers associated with the business. categoryBagAn optional element that contains a list of industry,product or geographic classifications.

12. Business Entity Sample 12 <businessEntity businessKey="uuid:C0E6D5A8-C446-4f01-99DA-70E212685A40" operator="http://www.ibm.com" authorizedName="John Doe"> Acme Company We create cool Web services General Information John Doe (123) 123-1234 jdoe@acme.com... <keyedReference tModelKey="UUID:8609C81E-EE1F-4D5A-B202-3EB13AD01823" name="D-U-N-S" value="123456789" /> <keyedReference tModelKey="UUID:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2" name="NAICS" value="111336" />

13. 13 Business Service The businessService element includes information about a single web service or a group of related web services. It corresponds to the UDDI green pages. Each component is uniquely identified by two UUID’s – serviceKey and businessKey.

14. 14 Business Service Structure EntityDescription serviceKeyA required attribute that contains a unique, hexadecimal identifier for a service. businessKeyAn attribute that references the businessKey of the businessEntity structure. nameA required element that contains the name(s) of a service. descriptionAn optional element that contains a brief description of a service. bindingTemplatesA required structure that contains technical information about a service categoryBagAn optional element that contains a list of industry, product or geographic classifications.

15. Business Service Sample 15 <businessService serviceKey="uuid:D6F1B765-BDB3-4837-828D-8284301E5A2A" businessKey="uuid:C0E6D5A8-C446-4f01-99DA-70E212685A40"> Hello World Web Service A friendly Web service...

16. 16 Binding Template The bindingTemplate element includes information about how and where to access a specific web service.

17. 17 Binding Template Structure EntityDescription bindingKeyA required attribute that contains a unique hexadecimal identifier. serviceKeyAn attribute that references the serviceKey of the businessService element. descriptionAn optional element that contains brief description(s) of web service(s). accessPointAn element that states where to access a web service. hostingRedirectorAn element that contains a link to another bindingTemplate structure, which contains the description for a particular service. tModelInstanceDetailsA required structure that contains tModelInstanceInfo elements, which are “blueprints” of web services.

18. Binding Template Sample 18 <bindingTemplate serviceKey="uuid:D6F1B765-BDB3-4837-828D-8284301E5A2A" bindingKey="uuid:C0E6D5A8-C446-4f01-99DA-70E212685A40"> Hello World SOAP Binding http://localhost:8080 <tModelInstanceInfo tModelKey="uuid:EB1B645F-CF2F-491f-811A-4868705F5904"> references the description of the WSDL service definition http://localhost/helloworld.wsdl

19. 19 tModel tModel stands for technical model and are primarily used to provide pointers to external technical specifications. “tModel” and “service” type are frequently used interchangeably.

20. 20 tModel Structure EntityDescription tModelKeyA required attribute that uniquely identifies the tModel. authorizedNameAn optional attribute that contains the name of the individual who published the information. operatorAn optional attribute that contains the name of the custodian. nameA required element that contains a descriptive identifier for the tModel. descriptionAn optional element that describes the tModel. overviewDocAn optional element that redirects users to additional references, usually WSDL documents. identifierBagAn optional element that contains a list of unique identifiers. categoryBagAn optional element that contains a list of industry, product or geographic classifications.

21. tModel Sample 21 <tModel tModelKey="uuid:xyz987..." operator="http://www.ibm.com" authorizedName="John Doe"> HelloWorldInterface Port Type An interface for a friendly Web service http://localhost/helloworld.wsdl

22. 22 UDDI Inquiry API Function NameDescription find_bindingSearches for bindings associated with a specified service find_businessSearches for businesses that match the specified criteria. find_serviceSearches for services associated with a specified business. find_tModelSearches for tModels that match the specified criteria. get_bindingDetailRetrieves a complete bindingTemplate record. get_businessDetailRetrieves a complete businessEntity record. get_serviceDetailRetrieve a complete businessService record get_tModelDetailRetrieve a complete tModel record

23. Creating Registry Sample 23 POST /save_business HTTP/1.1 Host: www.XYZ.com Content-Type: text/xml; charset="utf-8" Content-Length: nnnn SOAPAction: "save_business" XYZ, Pvt Ltd. Company is involved in giving Stat-of-the-art.......

24. Retrieving UDDI Information 24 POST /get_businessDetail HTTP/1.1 Host: www.XYZ.com Content-Type: text/xml; charset="utf-8" Content-Length: nnnn SOAPAction: "get_businessDetail"

25. UDDI with WSDL 25 HertzReserveService WSDL description of the Hertz reservation service interface WSDL source document. http://mach3.ebphost.net/wsdl/hertz_reserve.wsdl <keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4" keyName="uddi-org:types" keyValue="wsdlSpec"/>