The UDDI Publishing API
Organizations use the Publishing API to add, change, and delete information in a UDDI registry. This API allows organizations to save their own businessEntity, businessService, bindingTemplate, tModel, and publisherAssertion data structures in a UDDI registry, and to remove them when necessary.
Like the Inquiry API, the Publishing API is a full-fledged Web service based on SOAP's Document/Literal mode of messaging, and is described by a WSDL document. Unlike the Inquiry API, the Publishing API requires that UDDI operators use HTTPS (HTTP with SSL 3.0) for confidentiality and some form of authentication. In addition, every message—except for the login—must include an authorization token that is automatically issued by the UDDI registry at the start of a session. Each session will have a unique authentication token, which is good only for the life of the session.
The SOAP messages used in the Publishing API are not complicated and are defined in detail in the following sections. The API supports four kinds of operations: authorization operations, save operations, delete operations, and get operations. The authorization operations allow you to authenticate yourself, obtain an authorization token, and terminate a session and its authentication token. The save operations let you add or update the primary data structures. The delete operations let you remove primary data structures. The get operations let you view publisherAssertions and a summary of registered information.