UDDI

1
UDDI

• Universal Description, Discovery and Integration
• Discover a partner to do business with
• Standardize information sharing on services
• Characterize business transactions

2
Registry

• analogous to a phone book
• Business entity business info such as name,
  contact, URL
• Business service desc., category, URL
• Specification pointers how service is invoked
• Service type tModel defines a service type
  URL to WSDL

3
Role of UDDI

• Standards bodies define tModels
• Organizations register descriptions of their
  businesses and services assigned UUID
• Search engines find services that satisfy their
  criteria
• Found service may be executed using service
  interface

4
Role of UDDI Provider

• Advertising, discovery and storage
• Consistent way to advertise the services
• Ability to discover the services
• Persistent storage of XML and other resources
• UDDI is a registry, not a repository

5
Service interfaces

• May be WSDL, XML-RPC, CORBA, etc.
• Can be described using prose or a formal
  description language such as XML
• Can reference other service interface documents
  (import)

6
Business entity

• http//uddi.org/pubs/DataStructure-V2.03-Published
  -20020719.htm_Toc25130756

7
Business service

• http//uddi.org/pubs/DataStructure-V2.03-Published
  -20020719.htm

8
Binding template

• http//uddi.org/pubs/DataStructure-V2.03-Published
  -20020719.htm

9
tModel

• http//uddi.org/pubs/DataStructure-V2.03-Published
  -20020719.htm

10
Taxonomies

• Provides a list of allowable terms
• DUNS, UN/SPC, SIC, other
• You may create your own taxonomy
• UDDI APIs permit searching with different
  classification schemes
• Custom taxonomy example p193

11
Identifiers

• Uniquely identify a business based on known
  schemes
• Such as DUNS number,etc.
• It would appear as DUNS Number, 00-910-2001

12
Business entity relationships

• Different business entities for the same company
  may be related
• UDDI provides a find_relatedBusinesses API to
  view registered relationships
• Use save_business to create several entites
• Use add_publisherAssertion to create relationships

13
UDDI SOAP interfaces

• UDDI API uses request/response approach
• Two types of API are available
• Publishers API create, modify, delete
• Inquiry API query the registry

14
Browse Pattern

• Users provide general search criteria
• Generate a result set
• Select one or more
• Drill down

15
Drill-down Pattern

• Used to locate entities
• Start with find_business
• Use UUID and find_service
• Then find_binding
• And get_bindingDetail
• Used in UDDI Web interface

16
UDDI and SOAP/WSDL

• Services may be described other than WSDL
• It could be ASCII, RosettaNet or other
• WSDL description allows the user to
  programmatically generate a proxy to the service

17
Publishing WSDL in UDDI

• http//sourceforge.net/projects/wsdl4j
• Example p213

18
Tutorial

• http//www.cit.gu.edu.au/teaching/2507CIT/Resource
  s/jwstutorial13/doc/