Browse Prior Art Database

Distributed UDDI (Universal Description Discovery and Integration) registry lookup and storage Disclosure Number: IPCOM000015766D
Original Publication Date: 2002-Mar-13
Included in the Prior Art Database: 2003-Jun-21

Publishing Venue



Disclosed is a system to incorporate distributed discovery and search capability across UDDI registries. A significant limitation of existing UDDI implementations is that, there is only one global UDDI registry in the implementation. In the future, UDDI registries other than the global network will become prevalent. In fact, this is being encouraged byIBM with the announcement of its private UDDI registry product. However, a given UDDI registry that lives within a network of peer nodes has no mechanism of discovering or searching other UDDI registries. Ass privately maintained UDDI registries become more prevalent, they will need a mechanism searching for information that does not belong to them in order to satisfy queries. Therefore, the key idea of this disclosure is to add transparent distributed discovery and search capability across UDDI registries. Conceptually, this allows a global (or top-most) UDDI registry to act as a peer to a set of other, (potentially privately maintained) UDDI registries, therefore extending the power and applicability of UDDI as whole. The topology of this peer network has many variations either a search could be directed first at a private UDDI and then directed to a public UDDI registry, or vice versa, as business requirements and processes dictate. In this scenario, if a UDDI Server is asked for a business entity that implements a particular interface, it would first look in its local repository. Then, if the information is not found there, it could query additional UDDI servers of which it is aware. The key here is that this second lookup and information retrieval is handled entirely by the distributed UDDI lookup software and does not require the developer to use an additional API, or to handle failure cases where the first (or any succeeding) lookup failed prior to finding a matching result on another federated UDDI server. From the client perspective, it appears as if the inofrmation is in the first, or "top-most" UDDI server. The federation behind this server is entirely transparent to the client software. This process of passing requests transparently from one UDDI server to another is shown in Figure 1. Request