Universal Description Discovery and Integration

Universal Description, Discovery and Integration (UDDI) is a platform-independent, XML-based registry for businesses worldwide to list themselves on the Internet. UDDI is an open industry initiative, sponsored by OASIS, enabling businesses to publish service listings and discover each other and define how the services or software applications interact over the Internet. A UDDI business registration consists of three components:

*White Pages — address, contact, and known identifiers;
*Yellow Pages — industrial categorizations based on standard taxonomies;
*Green Pages — technical information about services exposed by the business.

UDDI was originally proposed as a core Web service standard [ [http://www.w3.org/2001/03/WSWS-popa/paper08 "W3C"] ] . It is designed to be interrogated by SOAP messages and to provide access to Web Services Description Language documents describing the protocol bindings and message formats required to interact with the web services listed in its directory.

UDDI was written in August, 2000, at a time when the authors had a vision of a world in which consumers of Web Services would be linked up with providers through a public or private dynamic brokerage system. In this vision, anyone needing a service such as credit card authentication, would go to their service broker and select one supporting the desired SOAP or other service interface and meeting other criteria. In such a world, the publicly operated UDDI node or broker would be critical for everyone. For the consumer, public or open brokers would only return services listed for public discovery by others, while for a service producer, getting a good placement, by relying on metadata of authoritative index categories, in the brokerage would be critical for effective placement.

The UDDI was integrated into the Web Services Interoperability (WS-I) standard as a central pillar of web services infrastructure. By the end of 2005, it was on the agenda for use by more than seventy percent of the Fortune 500 companies in either a public or private implementationFact|date=July 2008. Many of these enterprises subscribe to some form of service-oriented architecture (SOA), server programs or database software licensed by some of the professed founders of the UDDI.org and OASIS.

The UDDI specifications supported a publicly accessible Universal Business Registry in which a naming system was built around the UDDI-driven service broker. IBM, Microsoft and SAP announced they were closing their public UDDI nodes in January 2006. [ [http://webservices.sys-con.com/read/164624.htm Microsoft, IBM, SAP To Discontinue UDDI Web Services Registry Effort @ SOA WORLD MAGAZINE ] ]

Some assertFact|date=July 2008 that the most common place that a UDDI system can be found is inside a company where it is used to dynamically bind client systems to implementations. They would say that much of the search metadata permitted in UDDI is not used for this relatively simple role. However, the core of the trade infrastructure under UDDI, when deployed in the Universal Business Registries (now being disabled), has made all the information available to any client application, regardless of heterogeneous computing domains.

UDDI Nodes & Registry

UDDI nodes are servers which support the UDDI specification and belong to a UDDI registry while UDDI registries are collections of one or more nodes.

UDDI Implementations

Clients

* [http://uddi4j.sourceforge.net uddi4j] : UDDI for Java
* [http://www.microsoft.com/downloads/details.aspx?FamilyId=542991CF-9056-49FD-BABF-7FF3638EE6B1 UDDI.NET SDK] : UDDI for .NET Framework and Microsoft Visual Studio and Microsoft InfoPath [ [http://support.microsoft.com/kb/939689 How to publish a Web service in UDDI installed on Microsoft Windows Server 2003] ] [ [http://support.microsoft.com/kb/833380/ How to publish an XML Web service to an internal UDDI server by using Visual C# .NET 2003] ]
* [http://uddi4r.rubyforge.org uddi4r] : UDDI for Ruby
* [http://www.alphaworks.ibm.com/tech/uddi4py uddi4py] : UDDI for Python
* [http://search.cpan.org/dist/SOAP-Lite/lib/UDDI/Lite.pm UDDI::Lite] : UDDI for Perl

ervers

* [http://ws.apache.org/juddi/ Apache jUDDI: Open-Source UDDI Server]
* [http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/products/aqualogic/service_registry/ BEA Aqualogic Service Registry]
* [http://developer.novell.com/wiki/index.php/Novell_Nsure_UDDI_Server Novell nSure UDDI Server: Open-Source UDDI Server]
* [http://openuddi.sourceforge.net OpenUDDI: Open Source UDDI v3 Server]
* [http://www.ibm.com/developerworks/websphere/zones/soa/ IBM WebSphere Server]
* [http://msdn.microsoft.com/en-us/library/aa286530.aspx Microsoft Enterprise UDDI Services: Part of Windows Server]
* [https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.jsp?zn=bto&cp=1-11-130-27^2661_4000_100__ HP SOA Systinet Registry]
* [http://www.oracle.com/technology/tech/soa/uddi/index.html Oracle Service Registry]
* [http://www.softwareag.com/Corporate/products/centrasite/default.asp Software AG CentraSite]
* [https://www.sdn.sap.com/irj/sdn/enterprisesoa SAP Enterprise SOA PI7.1]
* [http://www.esigma.com eSigma's Public UDDI Registry]
* [http://www.tibco.com/software/soa/activematrix_registry/default.jsp TIBCO ActiveMatrix Registry]
* [http://www.ruddi.org/ INSPIRE IT Ruddi]

ee also

* XML-RPC
* Java API for XML Registries
* WS-I Basic Profile
* Web Services Discovery
* United Nations Standard Products and Services Classification (UNSPSC)
* ebXML

External links

* [http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm UDDI specifications]
* [http://www.oasis-open.org/committees/uddi-spec/ OASIS UDDI Technical Committee]
* [http://uddi.xml.org/ UDDI XML.org community site]
* [http://soapclient.com/uddisearch.html UDDI Browser]
* [http://wiki.codesynthesis.com/Schemas/UDDI C++ Data Binding for UDDI]
* [http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci916789,00.html SearchWebServices Compilation of UDDI ressource]
* [http://uddi.org/pubs/uddi-tech-wp.pdf Introduction to UDDI: Important Features and Concepts]
* [http://www2008.org/papers/fp389.html Web Service Deployment]

References