Anatomy of a UDDI Registry
Continuing on the UDDI topic started last week this article looks at a specific UDDI server and instance
- Organizations (Providers)
- Services
- Bindings
Below we can see each of these graphically represented.
The Hierarchy becomes reasonably clear in the image above and you can also see some features we’ll cover later in this series (specifically Search, Subscribe, and Coordinate).
Providers
The folder ‘Providers’ is exactly that – the place in the tree where all the service providers are listed in your UDDI server (meaning Organizations, or more likely departments). Below this we see services, and below those are bindings for the services (endpoints or physical locations / implementations).
In the image above, Nova Enterprise Systems is the Organization (White Page entry). Below is a screen shot of the details for this Organization. 
The image shows that there can be multiple names in different languages and descriptions as well. There are also tabs for Services and Contacts. The Contacts include details such as Name, Email, Phone, and Address. This metadata helps provide visibility and responsibility at the organizational level.
There is also a Relationships tab that allows us to specify organizational structures (Parent-Child) and partnerships (Peer). Through this we can describe the operational structure of a company, convey business relationships or simply identify that two organizations are really the same entity (Identity). The choices for Relationships are Parent-Child, Peer, and Identity (in the order they were introduced above).
Categories are also listed in this and at every level in the hierarchy. They are part of what make UDDI so powerful. We’ll cover more on Categories shortly.
Services
Services also have a similar properties page for names and descriptions in multiple languages. Importantly they have a collection of Bindings (covered below) and again a collection of Categories.

The important part here is that a single service is a child of an Organization (Provider) and has one or more Bindings associated with it as that Service’s own children. The service is the logical container; the bindings are the endpoints where the services or their detailed technical descriptions actually exist. If you click the More Details link you can see the service key for this service:
- uddi:42f392a5-0fc3-4d25-b4c9-1003bba4ac63
Bindings
Bindings are the lowest level in the hierarchy and are really meant to represent locations of implementations or service details, like WSDLs. Bindings correspond to the Green Pages in our phone book analogy. Here is an example of a binding for a service from the UDDI Services portal.

We can see that the Access Point for this service is a URL to where the service exists; in this case it is a service

