Typical Application of a UDDI Registry

1.3.1. UDDI Data Model

The basic information model and interaction framework of UDDI registries consist of the following data structures: • A description of a service business function is represented as a businessService. • Information about a provider that publishes the service is put into a businessEntity. • The services technical details, including a reference to the services programmatic interface or API, is stored in a bindingTemplate . • Various other attributes, or metadata, such as taxonomy, transports, and policies, are stored in tModels. These UDDI data structures are expressed in XML and are stored persistently by a UDDI registry. Within a UDDI registry, each core data structure is assigned a unique identifier according to a standard scheme. This identifier is referred as a UDDI key. Business Entity A business entity represents an organization or group of people responsible for a set of services a service provider. It can also represent anything that overreaches a set of services; for example a development project, department or organization. The business entity structure contains the following elements: • Names and Descriptions. The business entity can have a set of names and descriptions, in a variety of languages if necessary. • Contacts. The list of people who are associated with the business entity. A contact can include, for example, a contact name, addresses, phone numbers, and use type. • Categories. Set of categories that represent the business entitys features or quantities. For example the business entity can be associated with the category California to say that the business entity is located in that geographical area. • Identifiers. The business entity can be associated with arbitrary number of identifiers that uniquely identify it. For example, the business entity can be identified by a department number or D-U-N-S number. • Discovery URLs are additional links to documents describing the business entity. Business entities can be linked to one another using so-called assertions that model a relationships between them. Business Service Business services represent functionality or resources provided by business entities. A business entity can reference multiple business services. A business service is described by the following elements: • Names and descriptions. The business service can have a set of names and descriptions, in a variety of languages if necessary. • Categories. A set of categories that represent the business service features and quantities. For example, the business service can be associated by a category that represents service availability, version, etc. A business service in a UDDI registry does not necessarily represent a Web service. The UDDI registry can register arbitrary services such as example EJB, CORBA, etc. Binding Template A business service can contain one or more binding templates. A binding template represents the technical details of how to invoke its service. Binding templates are described by the following elements: Page 155 Binding Template