Introduction to UDDI (Common discovery and Publishing specification)

Specification

Introduction: UDDI is one of the core technologies of Microsoft's new generation of. NET Framework (others include Web SERVICE, SOAP, XML), so let's see what it really is.
--------------------------------------------------------------------------------
The universal Discovery Description and Integration (UDDI, the common discovery and publishing method Set) specification defines a way to publish and discover Network Service information. It is a set of public implementation rules that allow businesses to register the information they provide for their Web services so that other businesses can find them. The term "network services" refers to the specific business functions that a company implements, typically through an Internet connection, to provide a way for other companies or software programs to use these services.

Network Service is becoming the center of programming of electronic commerce. For example, a company uses the services of another company to send a purchase order directly over an Internet connection. Another example is the calculation of the cost of transporting a certain size or quality parcel at a distance through some form of transport.

At first glance the Network service discovery process seems to be very simple. What do you need to discover if a known business partner has a known E-commerce gateway? However, this is the case where all the information is known by default. When you want to find out which business partner has some kind of service, the problem becomes difficult immediately. One option is to call each business partner and then find the right person. For a network service, it is difficult to employ High-tech technicians to meet the needs of any discovery.

Another way to solve this problem is by using the Network Service description file on each company's Web site. After all, web crawlers can access a registered URL and can find and index text on the page. However, this "robots.txt" approach determines the ability of web crawlers to locate service profiles on each site and on the Web site. This distributed approach has the potential to upgrade, but lacks a mechanism to ensure the consistency of the service description file format and the convenience of tracking changes that occur to them.

UDDI relies on an enterprise distributed registration method whose service description text is in a common XML format.

UDDI Business Registration Logic and UDDI Business Registration database

A central part of the UDDI scheme is the UDDI Business registration logic, the uddibusinessregistrations, an XML-formatted file that describes the entity and its services of things. Conceptually, the information provided by a UDDI business registration logic includes three parts: "White Pages" include addresses, protocols, and existing identities; "Yellow Pages" include industrial types based on classification criteria; "Green page" is about the service technology information that the enterprise contains, Includes Network service description Reference and identification support for various files and URLs based on discovery mechanism.

Using UDDI

UDDI includes the shared operations of businesses on the web. To a large extent, programs and programmers use the UDDI Business Registration database, Uddibusinessregistry, to find information about services, for programmers to prepare systems that are consistent with advertised Web services, or to describe their network services to other callers. Uddibusinessregistry can check whether a particular partner has a specific Network service interface at the enterprise level to find a company with a specific type of service within a particular industry, to find information about a partner or prospective partner, To learn the technical details needed to interact with the service.

From XML and SOAP, you can go to the point where integration and interoperability issues have been simplified at all levels. XML provides a cross-platform way to encode and format data. SOAP is based on XML, which defines a simple way to package the exchange of information between systems. Soap's binding to HTTP is based on this packaged protocol and defines a method for making remote calls between systems, regardless of the programming language or operating system chosen by the individual company. Previous approaches include complex distributed object standards or technical bridging software. Finally, none of these methods is proven to be economical. Using XML and SOAP, this cross-language, cross-platform approach simplifies the compatibility of systems among two companies.

Even if a company takes XML and SOAP into account, any two companies may still have significant differences in the implementation of the communications infrastructure. As any industry authority will tell you: "What is needed is a fully end-to-end (End-to-end) solution based on the universally supported standards for each computing platform." "Obviously, there is more work to be done to achieve this goal." The UDDI specification, which absorbs the lessons of XML and SOAP, defines a superstructure that allows two companies to share a method for querying each other's attributes and describing their own characteristics.

UDDI Technology Discovery Layer

The UDDI specification describes the concept of network services. And a simple programming interface that defines the architecture that describes any kind of network service. This specification consists of several related files and an XML schema that defines a SOAP based programming protocol for registering and discovering network services. These specifications are determined by technicians and managers from several leading companies in a few months. At the same time, these companies assume the task of implementing UDDI Services first and exposing these services as publicly accessible, multi-site cooperative operations that share all the registration information.

The relationship between the registration (BUSINESSREGISTRY) specification, which provides a way to access the "once registered, published everywhere" information about network services.

With the UDDI Discovery service, organizations can register separately for information about the network services they expose for use by other enterprises. This information can be added to a UDDI enterprise registry by means of a Web site or using a tool that uses the programming service interface described in the UDDIAPI specification. UDDI Enterprise Registration is a logically centralized, physically distributed service with multiple root nodes that can replicate data to each other on a regular basis. Once an enterprise registers with an enterprise registration service sample, data is automatically shared with other UDDI root nodes and can be used freely by anyone who needs to know about the network services provided by a particular enterprise.

Please note that it is important that UDDI does not constitute a full-featured discovery service. UDDI Services are designed to enable the adoption of technology discovery services. With a UDDI-defined tool, a program or programmer can find information about a service provided by a partner, understand whether a partner has a service that is compatible with the internal technology, and can follow the connection to find the appropriate specification for a network service. Such an integration layer can be built in a way that is compatible with partner services. Companies can also find potential partners either directly through UDDI or by using UDDI as an online marketplace and search engine for their value-added service data sources. This enables the discovery of technical compatibility so that software companies can use UDDI registration on the network to automatically configure specific technical connections when software is installed and configured.

Here, we have the conditions and it is necessary to make a summary to straighten out. NET core technologies to understand how they interact around Web services.

. NET technology uses the standard network protocol such as HTTP/TCP to complete the low-level transmission, using XML as the basis of data representation, through SOAP, illustrates the method of exchanging information between systems with XML, A service description language such as WSDL (also xml-based) is used to describe and record messages generated and received by Web services, and to register and look for services through UDDI.

The work of the future

Teams working on UDDI are planning to extend the functionality in the Opendraft specification so that it can solve more problems, not just technical discovery issues. Future features will provide the ability to find products and services, define Network service implementation specifications, and provide the ability to manage tiered business organizations, groups, and trade groups. The driving goal is to provide a public specification for network Service interoperability.