Understanding UDDI (1): System Architecture Implemented by UDDi Service
(This article was originally published by the IBM DeveloperWorks China website, its URL is http://www.ibm.com/developerWorks/cn/)
(This article is the architecture implemented by the UDDi service I have 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, Universal Description, discovery and integration) is a web-based, distributed, implementation standard specification for the information registry provided by Web services, and also contains a group of enabled companies. The Web service provided by itself is registered to achieve the implementation of the access protocol of the other enterprises.
The web service is the next generation of WWW, which allows programmable elements to be placed on the Web site to make Web-based distributed calculations and processing. The purpose of the UDDI Registration Center is to promote the development of the company's Web services and find the appropriate Web services for the enterprise.
This paper mainly describes the architecture of the UDDI registration center based on UDDI standard specification, as well as implementation architectures based on UDDI and SOAP-based web services.
basic concepts
UDDI specification: UDDI specification V1 includes two specification text, UDDI Programmer's API V1.0 (UDDI programmer API specification 1.0) and UDDI Data Structure Reference V1.0 (UDDI Data Structure Reference 1.0). The former defines the API interface that the UDDI Operator Site can support, while the latter describes the specific definitions of the data structure described in the API. The UDDI specification is the UDDI Operator site to implement blueprint, but also a reference specification for web services that need to access UDDI Registry.
UDDI Registry (UDDI Registration Center): UDDI Registry is a generality of all sites that provide public UDDI registration services. UDDI Registry is a logical unity, which is implemented in the architecture of the distributed system, and between the different sites is implemented using the P2P (peer-to-peer network) architecture, so access to any of the sites is basically equal to Access UDDI Registry.
UDDI Operator Site (UDDI Registration Center Operating Inlet Site, Abbreviation UDDI Operating Inlet): UDDI Operator Site is a peer-to-peer node in UDDI Registry, and the result obtained for the UDDI Operator Site query is to overwrite information in full UDDI registry. Information query does not require authentication; and in the UDDI Operator Site, you must use the UDDI Operator Site itself to implement, and later updates, the deletion must pass this Operator Site, and use the initial release Users permission certification.
Compatible UDDI Registry (compatible UDDI Registration Center): All UDDI registrations that are compatible with UDDI but are not to provide public services, namely compatible UDDI registry.
UDDI - Technology Discovery Layer
Unified Description, Discovery and Integration Protocol (UDDI) Specifies a logical cloud service constructed by the web service, and also defines a programming interface, which provides a simple framework for describing the web service. Specifications include several related documents and a XML Schema to define protocols based on SOAP-based registration and discovery of Web services. These regulations have been completed by technicians and managers from major companies from many industry a few months. These companies also have tasks that implement the first UDDI Business Registration Center service, which will be accessed by everyone, while their multiple cooperative sites can seamlessly share registration information.
In the core system implementation of P2P (Peer to Peer), the P2P (Peer to Peer) is used in the core system implementation of UDDI. From the outside of UDDI Registry, UDDI Registry is a whole service for users, while different UDDI Operation Inlet Sites is a different access entry for the entire UDDI Registry service, and user information is associated with access portals. And the information registered with the user has nothing to do with the access entry on the query. All users can select the UDDI Operating Inlet Site (Operator Site) to perform information queries, and the range of data obtained is to override the data existing in all UDDI registry. The duties of the UDDI Operating Inlet Site (Operator Site) are hosting rights for registration data. The ownership of each registration data entry has two levels. The first level is a certain operating entry site, the second level it belongs to a certain Operate the user (publisher) registered on the entry site. It is worth noting that different operating entry sites can have different user authentication mechanisms and different user management methods.
UDDI information model
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.
UDDI XML Schema defines four main information types, which are technical information that technicians must understand when they need to use the Web services provided by partners. They are documentation information for business entity information (BusinessService), BindingTemplate, and Service Calling Specification (TMODEL).
Query API and Publish API
The query API contains two types of calls, so that the program can quickly locate candidate commercial entities, Web services, and their call specifications, and then obtain further information on the initial information initially invoked to obtain further information. This type of API named by Find_xx provides a variety of search criteria to search for data in the registry.
The release API includes four Save_xx functions and four delete_xx functions, each corresponding to a UDDI main structure (Business, BinsinessService, BindingTemplate, TModel).
to sum up
This paper focuses on the service architecture implemented by UDDI, briefly introduces the registration information model and query / release the API. I will introduce the information model in the later article and combine the use of the UDDI service and the precautions for the UDDI service.
