Along with SOAP and WSDL, UDDI is one of the core technologies that supports Web Services. A UDDI implementation is a Web Service Registry that provides a mechanism to advertise and find Web Services. A UDDI registry contains categorized information about businesses and the services that they offer, and it associates those services with technical specificiations of the Web Service. These technical specifications are usually defined using WSDL. WSDL describes what a Web Service does, how it communicates, and where it lives. A Web Service consumer queries the UDDI registry to find the WSDL descriptions to determine how to use the Web Service. A UDDI registry is itself a Web Service. The UDDI specification defines an API based on SOAP messages, with a WSDL description of the registry service. Most UDDI registries also provide a browser-based human interface. The UDDI Project operates a global public registry called the UDDI Business Registry. This registry is available to everyone at no charge (see http://www.uddi.org), and all information registered in the public registry is available to the general public. Organizations can also set up a private registry to support the requirements of an enterprise or a private community. A private registry can impose additional security controls to protect the integrity of the registry data and to prevent access by unauthorized users. A private registry might contain only private information, it might contain a subset of the public registry information, or it might contain a combination of public and private information.
Dig Deeper on Topics Archive
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading