Universal Description, Discovery and Integration

from Wikipedia, the free encyclopedia

Universal Description, Discovery and Integration ( UDDI ) is a term from the service-oriented architecture (SOA) environment and describes a standardized directory service that should play the central role in an environment of dynamic web services . At the end of 2005, the biggest supporters of UDDI - IBM , Microsoft and SAP - announced that they would switch off their UDDI directory service UBR (UDDI Business Registry), which in many places was interpreted as the end of UDDI.

construction

The directory service has a SOAP interface. It contains companies, their data and their services. UDDI can distinguish between three types of information: the "white pages", a kind of telephone book , the "yellow pages", i.e. the electronic equivalent of the yellow pages and the interface descriptions in the so-called "green pages". The exact breakdown, including the data that will come from the individual parts, is shown in the following list:

White Pages

The white pages (basic information) work in a similar way to a telephone book (hence the English term "white pages") and provide information about the identity of the service provider. This includes information about the business area, contact details of a contact person and a globally unique company code that is assigned according to the Data Universal Numbering System (DUNS). The so-called DUNS number is issued free of charge by the US credit agency Dun & Bradstreet .

Yellow Pages

The yellow pages (service categorization) of the web service from the provider identified in the basic information are classified according to their purpose according to various classification schemes. This is necessary in order to easily find the right services. Because of this purpose, one speaks of a "business directory", the "yellow pages". The services are classified using international standards such as UNSPSC .

Green Pages

The interface descriptions of a web service are provided in this area. Information about these descriptions is stored in the so-called tModel . In order to check the suitability of the web service provider and web service user, the tModel descriptions (tModel keys) are compared with one another. This area is called the Green Pages .

Data model

The data model describes the relationships between companies, their services and interfaces. The categoryBag , identifierBag and tModel can be used to find services that meet certain requirements.

The five main ingredients:

businessEntity
Information ( metadata ) about the provider (e.g. company, name, description), contains a list of the services offered (the root element from an XML perspective)
businessService
General description of a service class ( metadata about the service), represents a logical service classification and is a child element of a businessEntity structure
bindingTemplate
describes technical characteristics of the service
publisherAssertion
describes the relationship between the parties
t model
References to technical requirements, storage using generic data

Descriptive components:

categoryBag
describes the categorization
identifierBag

Specification element:

tModel
technical specification of the service (e.g. data format and transmission protocol)

Individual evidence

  1. ↑ Microsoft: UDDI Business Registry Shutdown FAQ. (No longer available online.) December 14, 2005, archived from the original on March 18, 2010 ; accessed on March 6, 2010 (English). Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  @1@ 2Template: Webachiv / IABot / uddi.microsoft.com
  2. ^ Dave Linthicum: UDDI is a Dead Parrot. In: infoworld.com/. International Data Group (IDG), December 22, 2005, archived from the original on January 3, 2006 ; Retrieved on March 6, 2010 (English): “What's important here is that we are missing a common shared directory of services on the Internet, a global catalog of sorts, where services can be posted, discovered, and leveraged. That was the purpose of UDDI, it did a bad job [...] "
  3. ↑ Joe McKendrick: IBM acknowledges bypassing UDDI; calls for new SOA registry standard. In: ZD Net. CBS Interactive Inc., April 26, 2007, accessed March 6, 2010 .

Web links