UDDI

UDDI is the protocol for communicating with registries.

core -UDDI Business Registry,

a global, public, online directory that provides businesses a uniform way to describe their services, to discover services from other companies,

understand the details of how to connect and interact with the software that implements a service.

UDDI defines a layer above SOAP in an interoperability stack that builds on TCP/IP, HTTP, and XML.

UDDI defines an XML-based infrastructure for software to automatically discover available services on the Web, using SOAP as the protocol to invoke services

UDDI: Public versus Private Registries

Microsoft, IBM, and HP have agreed to provide a public UDDI registry, open for search and connection across the entire Internet.

But private registries will also be available either internally within companies or among a closely knit family of trusted partners and collaborators.

In Version 2 - both public and private Web service registries, allowing enterprises to deploy private registries to manage internal Web services using the UDDI specification.

Many IT companies are beginning to use Web services technologies behind their firewalls for application-to-application integration.


The UDDI Family of Specifications-Describe how a program can interact with a registry, including the following.

The UDDI Programmer's API Specification

30 SOAP messages that are used to perform inquiry and publishing functions against any UDDI-compliant business registry.

The UDDI Data Structure Specification

defines the four major data structures used by Programmer API.

These include

businessEntity


businessService


bindingTemplate


tModel

Using UDDI to Make the ZwiftBooks Connection

Scenario connecting to our ZwiftBooks server using UDDI discovery:

A company -writing software that connects to several book-service providers and comparing price and delivery times for each.

It needs a program that can connect to the UDDI business registry

After a lookup based on an appropriate yellow pages listing, the company obtains a businessEntity that represents ZwiftBooks.

businessEntity

The client can either drill down for more detail or request a complete businessEntity structure.

In either case, the objective is to obtain a bindingTemplate that provides the information about how to connect to ZwiftBooks Web service.

bindingTemplate

The company sets up its program to interact with the ZwiftBooks Web service.

The semantics of the service may be obtained by accessing the tModel contained in the bindingTemplate for the service.

At runtime, the program invokes the Web service based on the connection details provided in the bindingTemplate.

If the remote Web services and the calling program each accurately implement the required interface conventions -calls to the remote service will be successful.