Understanding UDDI (2): Data Model of UDDI Registration Information
(This article was originally published by the IBM DeveloperWorks China website, its URL is http://www.ibm.com/developerWorks/cn/)
(This article is the data model of UDDI registration information published in the developerWorks column, you need to browse the original text, please visit http://www.ibm.com/developerworks/cn/)
Unified Description, Discovery and Integration Protocol (UDDI) standards include the XML Schema (UDDI Data Structure Reference) and UDDI Specifications API (UDDI Programmer's API) of SOAP messages. Both the two creates the foundation model and interactive framework, with the ability to publish various web services description information. The interaction framework is a message convention for UDDI Client to interact with UDDI Registry, which we will discuss later.
The core information model used by UDDI registration is defined by XML Schema. Using XML is because it provides a platform-independent data description and naturally describes the hierarchical relationship of data. And the XML Schema is because it supports rich data type, convenient description, and its ability to verify the data by the information model.
Data model overview
UDDI XML Schema defines four main information types, which are technical information that technicians must understand when using the Web services provided by partners. They are: Business Structure (BusinessService Structure), BindingTemplate Structure, and Technical Specification Information (TMODEL Structure). In the UDDI data model, TMODEL is a very special data item. TMODEL describes all technical information, and TMODEL's all the technical registration information in UDDI. I will give the details of TMODEL to each other in the TMODEL section.
Business entity information: businessentity element
In business sectors, partners and potential partners expect to accurately position information about services or products that can be provided by commercial entities, and use this information as the beginning of your company. In terms of technical fields, technicians, programmers or applications expect to know the names and some key identifiers they need to integrate, and the business entity is classified information that belongs to that specific industrial classification, and contact Methods (including Email, Phones, URLs), etc. Support for commercial information publishing and discovery of UDDI commercial registration is included in the "BusinessSentity" structure. This structure is the highest layer of data container for commercial entity exclusive information set, located at the top of the entire information structure.
Business Service Information: BusinessService Elements
The BusinessService structure combines a series of descriptions of the web services for business processes or classified catalogs. BusinessService and the BindingTemplate you want to form together form a "green page". Among them, an example of a possible business process is a set of related web service information, including procurement services, transportation services, and other high-level business processes. These services will be a web service that provides registration of commercial entities that provide these business processes services.
These BusinessService's information sets can be classified again, making the description of the web application service can be done in different industries, products, service types, or geographical partitions. The mechanism for classification methods is similar to BusinessSentity.
Technology Binding Information: BindingTemplate Elements
For each BusinessService, there is a technique for one or more web services, BindingTemplate. These technical descriptions include information necessary for the application to connect the remote web service and communicating with it. This information includes an address of the web application service, an additional application service that must be called before the application service host and call service. In addition, some complicated routing, such as load balancing, and the like by additional characteristics. Meta technical information: TMODEL element
Calling an information required is defined in the structure of BindingTemplate, which has been explained in the previous section. However, in general, only the address of the Web service is not enough. For example, if I know that my partner provides a web service to let me order, and I know the URL of this service, but if I don't know some specific information, such as the specific format of the order, the protocol that should be used, needs to be used Safety mechanism, call returned response format, etc.,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
When a program or programmer needs to call a particular web service, it is necessary to obtain a sufficiently adequate call specification and other related information, so that the call is properly executed. Therefore, each bindingTemplate element contains a special element that contains a list, each sub-element of the list is a reference specification. These references consist of a compact set of identifiers, which constitute a technical identity similar to fingerprint, used to identify web services that implement a given behavior or programming interface.
