blob: baabb38dc7b3273e2947615cbd1e6b9b9770fba5 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<!--Arbortext, Inc., 1988-2005, v.4002-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="cuddi" xml:lang="en-us">
<title>Universal Description, Discovery, and Integration (UDDI)</title>
<titlealts>
<searchtitle>Universal Description, Discovery, and Integration (UDDI)</searchtitle>
</titlealts>
<shortdesc>Universal Description, Discovery, and Integration (UDDI) specification
defines a way to publish and discover information about Web services.</shortdesc>
<prolog><metadata>
<keywords><indexterm>UDDI</indexterm><indexterm>Universal Description, Discovery,
and Integration </indexterm><indexterm>Web services<indexterm>UDDI</indexterm></indexterm>
</keywords>
</metadata></prolog>
<conbody>
<p>UDDI has two functions: <ul>
<li>It is a SOAP-based protocol that defines how clients communicate with
UDDI registries.</li>
<li>It is a particular set of global replicated registries.</li>
</ul></p>
<p>UDDI includes an XML schema for SOAP messages that defines a set of documents
to describe business and services information, a common set of APIs for querying
and publishing information to the directories, and an API for replicating
directory entries between peer UDDI nodes.</p>
<p>For more information on UDDI refer to <xref format="html" href="http://www.uddi.org"
scope="external">www.uddi.org</xref></p>
<section><title>UDDI registries</title><p>UDDI manages the discovery of Web
services by relying on a distributed registry of businesses and their service
descriptions implemented in a common XML format. Before you can publish your
business entity and Web service to a public registry, you must first register
your business entity with a UDDI registry.</p><p>UDDI registries come in two
forms: public and private.&nbsp; Both types comply to the same specifications.&nbsp;
A private registry enables you to publish and test your internal e-business
applications in&nbsp;a secure, private environment.</p><p>A public registry
is a collection of peer directories that contain information about businesses
and services. It locates services that are registered at one of its peer nodes
and facilitates the discovery of published Web services. Data is replicated
at each of the registries on a regular basis. This ensures consistency in
service description formats and makes it easy to track changes as they occur. <tm
tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> maintains
two public registries called the <tm tmclass="ibm" tmowner="IBM Corporation"
tmtype="reg" trademark="IBM">IBM</tm> UDDI Business Registry and the <tm tmclass="ibm"
tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI Test
Registry. The <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI
Test Registry allows you to develop your Web service and experience the UDDI
registration process without placing your Web service in an official registry.&nbsp;
Use the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> UDDI
Test Registry to experiment with UDDI, and to test and validate your Web service.&nbsp;
For more information on the IBM's public registries, refer to <xref format="html"
href="http://uddi.ibm.com" scope="external">http://uddi.ibm.com</xref> For
a list of public registries, refer to <xref href="http://www.uddi.org/register.html"
scope="external">http://www.uddi.org/register.html</xref></p><p>A private
registry allows you to publish and test your internal applications in a secure,
private environment.</p><p>The UDDI Business Registry acts as a B2B directory
linking marketplaces, buyers, and sellers. The information provided in the
registry consists of three components: white pages, yellow pages, and green
pages. White pages include the business name, contact information, and a text
description of the business's services. Yellow pages include industrial categorizations
based on standard taxonomies such as NAICS, ISO 3166, and UNSPSC. Green pages
include references to specifications for Web services and pointers to various
file and URL-based discovery mechanisms. This makes it easy for businesses
to integrate across marketplaces. Because it is registered, information is
made available across all applications. For more information on NAICS refer
to <xref format="html" href="http://www.naics.com" scope="external">www.naics.com</xref> For
more information on UNSPSC refer to <xref format="html" href="http://www.unspsc.org"
scope="external">www.unspsc.org</xref> For more information on ISO 3166 refer
to <xref format="html" href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html"
scope="external">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</xref></p><p>Businesses
populate the registry with descriptions of the services that they support.
UDDI assigns a unique identifier to each service description and business
registration. These become the service and business keys respectively. Search
engines, and applications query the registry to discover services. UDDI servers
are a directory of available services and service providers.</p></section>
</conbody>
<related-links>
<linklist><title>Related Concepts</title>
<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer">
<linktext>Web services development</linktext></link>
<link href="cwsdlud.dita"></link>
<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita" scope="peer">
<linktext>Relationship between UDDI and WSIL</linktext></link>
</linklist>
<linklist><title>Related Tasks</title>
<link href="../tasks/tuddiexp.dita"></link>
</linklist>
<linklist><title>Related Reference</title>
<link href="../ref/ruddi.dita"></link>
</linklist>
</related-links>
</concept>