Annex E (normative) DirectoryServices ToC Previous Next

E.2 UDDI ToC Previous Next

UDDI registries contain businessEntities which provide one or more businessServices. The businessServices have one or more bindingTemplates. bindingTemplates specify a physical address and a Server Interface (called a tModel). Figure 31 illustrates the relationships between the UDDI registry elements.

readme_files/image033.png Figure 31 – UDDI Registry Structure

This specification defines standard tModels which shall be referenced by businessServices that support UA. The standard UA tModels shown in Table 72.

Table 72 – UDDI tModels

Name domainKey uuidKey
Server uddi:server.ua.opcfoundation.org uddi:AA206B41-EC9E-49a4-B789-4478C74120B5
DiscoveryServer uddi:discoveryserver.ua.opcfoundation.org uddi:AA206B42-EC9E-49a4-B789-4478C74120B5

The name of the businessService elements should be the same as the ApplicationName for the UA application. The serviceKey shall be the ApplicationUri. At least one bindingTemplate shall be present and the accessPoint shall be the URL of the DiscoveryEndpoint for the UA server identified by the serviceKey. Servers with multiple DiscoveryEndpoints would have multiple bindingTemplates

A UDDI registry will generally only contain UA servers, however, there are situations where the administrators cannot know what Servers are available at any given time and will find it more convenient to place a DiscoveryServer in the registry instead.

Previous Next