+

Search Tips   |   Advanced Search

 

Invocation pattern for the UDDI registry

 

To prepare an application to take advantage of a remote Web service that is registered within the UDDI registry by other businesses or entities, prepare that application to use the information found in the registry for the specific service being invoked.

The bindingTemplate data that is obtained from the UDDI registry represents the specific details about an instance of a given interface type, including the location at which a program starts interacting with the service. The calling application or program caches this information and uses it to contact the service at the registered address whenever the calling application needs to communicate with the service instance.

In remote procedure technologies that were previously popular, tools automate the tasks that are associated with caching, or hard coding, location information. However, there are problems when a remote service moves and the callers do not know about the move. There are many reasons why a remote service might move, for example, a server upgrade, disaster recovery, service acquisition, or a change to the business name.

When a call fails using cached information previously obtained from a UDDI registry, the proper behavior is to query the UDDI registry for fresh bindingTemplate information. If the data that is returned is different from the cached information, the service invocation can automatically retry the invocation, using the fresh information. If the result of this retry is successful, the new information replaces the cached information.

By using this pattern with Web services, a business that uses a UDDI registry can automate the recovery of a large number of partners without excessive communication and coordination costs. For example, if a business activates a disaster recovery site, most of the calls from partners would fail when they try to invoke services at the failed site. By updating the UDDI information with the new address for the service, partners who use the invocation pattern automatically locate the new service information and recover without further administrative action.


 

Related tasks


UDDI registry client programming

 

Related Reference


UDDI registry Application Programming Interface

 

Reference topic