Web Services Essentials

The UDDI Publishing API

Publishing to UDDI usually takes place via a web-based interface. Nonetheless, there are certain instances when you may want direct access to the publishing API. For example, you may be building web services software that automatically registers new web services, or you may need an automatic method of updating binding access URLs, in the event of disaster recovery.

Publishing requests must be sent to a secure URL that is distinct from the Inquiry API URL. To publish to the test registries, use the following URLs:

• Microsoft: https://test.uddi.microsoft.com/publish

• IBM: https://www.ibm.com/services/uddi/testregistry/protect/publish

To publish to the production registries, use these URLs:

• Microsoft: https://uddi.microsoft.com/publish

• IBM: https://www.ibm.com/services/uddi/protect/publish

Table 7-8 provides an overview of the main UDDI publishing functions. The publishing API is divided into three main subsections: authenticating users, saving data, and deleting data. In the sections that follow, we will see examples from each of the three subsections.

Table 7-8. Main functions of the UDDI publishing API

Function name	Description
Authentication functions
get_authToken	Requests an authentication token from the operator site. An authentication token is required for all subsequent save_xxx and delete_xxx functions.
discard_authToken	Requests that the specified authentication token be discarded and invalidated.
save_xxx functions
save_binding ...