UDDI
The Universal Description, Discovery and Integration (UDDI) specification defines a way to publish and discover information about Web services.
In this specification:
The UDDI specification also associates Web services with Technical models. Using these models or generic categories, a UDDI registry user can search for a type of service, rather than needing to know the access details for a specific service.
For more general information about UDDI, see the UDDI community at uddi.org.
UDDI registries
UDDI registries use the UDDI specification to publish directory listings of Web services. There are Universal Business Registries (sometimes referred to as public UDDI registries) hosted worldwide, including one hosted by IBM. Enterprises can also host their own internal registries behind their firewalls (sometimes referred to as private UDDI registries) to better manage their internal implementation of Web services. The IBM WebSphere UDDI Registry is an example of a private UDDI registry.How the gateway interacts with UDDI registries
The gateway interacts with UDDI registries in two ways:
To enable your gateway to interact with a UDDI registry, you create one or more gateway pointers to the registry. The gateway refers to these pointers as UDDI references, and you create them as described in Deploying UDDI references to the Web services gateway. Each UDDI reference includes the following parameters:
A given UDDI reference can only access the Web services that are owned by the businesses that are owned by a single Authorized Name. Therefore if you need to access two Web services in the same registry, and each service is owned by a different "Authorized Name", then you need to create two UDDI references.
When you deploy a Web service, and you specify that the internal WSDL file is located through a UDDI registry, you enter the following two parameters:
When you tell the gateway to create entries for a deployed Web service in one or more UDDI registries, you enter the following two parameters:
Because the gateway only interacts with UDDI registries at the level of specific Web services, the gateway does not use UDDI Technical models.