[.NET] UDDI (General Discovery and Publishing Specification)

xiaoxiao2021-03-06  66

UDDI is one of the core technologies of Microsoft's new generation .Net framework (other include web service, soap, xml), let's take a look at what it is?

Universal Discovery Description and Integration (UDDI, the General Discovery and Publishing Method Set) Specifications define a way to publish and discover network service information. It is an open implementation rule that allows companies to register their network service information so that other companies can find them. The term "network service" refers to a specific business functionality implemented by a company, usually providing these services to other companies or software programs via the Internet connection.

Network services are becoming programming focus on e-commerce. For example, a company uses another company's service to send a purchase order through the Internet connection. Another example is the cost of calculating a certain distance of a package that ships a certain size or mass.

It seems very simple to look at the network service discovery process. If a known business partner has a known e-commerce gateway, what else needs to find? However, this is known by default all information. When you want to find out which business partners have some kind of service, the problem is difficult to change. One choice is to call each business partner and find a suitable candidate. For a network service, hiring high-tech technicians to meet the needs of any discovery is difficult to do.

Another way to solve this problem is by using the network service description file on each company website. After all, the network crawler can access a registered URL and can discover the text on the web page. However, this "robots.txt" method determines the ability of the network reptile to locate each website and the website service description file. This distributed approach has upgraded potential, but lacks a mechanism to ensure the consistency of the service description file format and the convenience of tracking the changes they take.

UDDI depends on a business distributed registration method, and their service description text is using a universal XML format.

UDDI Business Registration Logic and UDDI Business Registration Database

The core part of the UDDI program is the UDDI service registration logic, namely UDDIBUSINESSREGISTRATION, an XML format for files to describe event entities and its business services. From a conceptual view, the information provided by a UDDI business registration logic consists of three parts: "White Page" includes address, protocol, and existing identifiers; "Yellow Pages" includes classification standards; "Green Page" is about enterprises The service technology information contained, including the network service description reference and the identity support for various files and URLs according to the discovery mechanism.

Use UDDI

UDDI includes a shared operation of an enterprise online. To a large extent, the programs and programmers use the UDDI service registration database, UDDibusinessRegistry find information about the service. For programmers, you can prepare the system that is consistent with the advertising network service, or to others to describe their network. service. UDDIBUSINESSREGISTRY can check if a specific partner has a specific network service interface at the enterprise level to find out some companies with specific types of services in a particular industry to find information about a partner or expected partner in order to understand The service is required for interaction.

From XML and SOAP, it is possible to simplify the integration and interoperability issues. XML provides a cross-platform approach to data coding and formatting. SOAP is based on XML, which defines a simple way for packaging exchange information between systems. SOAP's binding of HTTP is based on this packaging protocol, and defines how to remotely call between systems, this method is independent of the programming language or operating system selected by individual companies. Previous methods include complex distributed object standards or technology bridge software. Finally, these methods are not proven to be economical. Using XML and SOAP, this cross-language, cross-platform approach simplifies the problem of two companies' systems and compatibility. Even if a company takes into account XML and SOAP, any two companies may still have huge differences in implementing communication infrastructure. Just as any industry authority will tell you: "It is necessary to build a complete terminal to end-to-end on the standard for each computing platform." Obviously, There is more work to achieve this goal. The UDDI specification learns XML and SOAP lessons to define an upper structure so that two companies can share a method to query each other's characteristics and describe their own characteristics.

UDDI Technology Discovery

The UDDI specification describes the concept of network services. And a simple definition describing the programming interface of the architecture of any kind of network service. This specification has several related files and an XML schema, which defines SOAP-based programming protocols for registration and discovering network services. These norms are determined by technicians and managers from several leading companies for a few months. At the same time, these companies have assured the UDDI service first, and use these services as a task that is openly accessible, multi-site cooperation, multi-site cooperation.

The relationship between the registration (BusinessRegistry) specification provides an access to the "once registration, place" on network service information.

With UDDI discovery services, companies can register separately about the information about the network services they disclose for other companies. This information can be added to the UDDI Enterprise Registration through the website or using a tool for programming service interfaces described in the UDDIAPI specification. UDDI Enterprise Registration is a logical set, physically distributed, has multiple root-node services, which can regularly copy data from each other. Once a company is registered with an enterprise registration service example, the data is automatically shared with other UDDI root nodes, and can be free to use for anyone who needs to know the network services provided by a particular company.

Note that UDDI does not constitute a fully fully equipped discovery service is important. The UDDI service is intended to enable technology discovery services. With UDDI defined tools, a program or programmer can find information about the service provided by a partner, you can understand if a partner has a service compatible with internal technology, and you can find a suitable network according to the connection. The service specification, such an integrated layer can be built in a manner compatible with partner services. Enterprises can also find potential partners directly through UDDI, or to find potential partners by using UDDI's online shopping malls and search engines for its value-added service data source. This can discover technical compatibility so that software companies can use UDDI registration on the network, automatically configure certain specific technical connections when software installation and configuration.

Here, we have a condition to be a summary of the logical relationship between the .NET core technology, understand how they interact around the Web service.

.NET technology uses HTTP / TCP and other standard network protocols to complete the underlying transmission, as XML as the basis of data, by SOAP illustrates the method of exchange information between systems with XML in system, by WSDL (equally XML), etc. Service Description Language To describe and record messages generated and received by the web service, register and find services through UDDI.

future job

转载请注明原文地址:https://www.9cbs.com/read-119599.html

New Post(0)