Publish API for the UDDI Registry
The messages in this section represent commands that are used to publish, delete and update information contained in a UDDI registry. The messages defined in this section all behave synchronously.
The Publishing API calls defined that UDDI operators support are:
- add_publisherAssertions
- Causes one or more publisherAssertions to be added to an individual publisher's assertion collection.
- delete_binding
- Causes one or more instances of bindingTemplate data to be deleted from the UDDI registry.
- delete_business
- Removes one or more business registrations and all direct contents from a UDDI registry.
- delete_publisherAssertions
- Causes one or more publisherAssertion elements to be removed from a publisher's assertion collection.
- delete_service
- Removes one or more businessService elements from the UDDI registry and from its containing businessEntity parent.
- delete_tModel
- Logically deletes one or more tModel structures. Logical deletion hides the deleted tModels from find_tModel result sets but does not physically delete them, so they are returned on a get_registeredInfo request.
- discard_authToken
- Informs an operator site that the authentication token is to be discarded, effectively ending the session. Subsequent calls that use the same authToken will be rejected. This message is optional for operator sites that do not manage session state or that do not support the get_authToken message.
- get_assertionStatusReport
- Provides administrative support for determining the status of current and outstanding publisher assertions that involve any of the business registrations managed by the individual publisher account. Using this message, a publisher can see the status of assertions that they have made, as well as see assertions that others have made that involve businessEntity structures controlled by the calling publisher account.
- get_authToken
- Obtains an authentication token.Authentication tokens are opaque values that are required for all other publisher API calls. This message is not required for operator sites that have an external mechanism defined for users to get an authentication token. This API is provided for implementations that do not have some other method of obtaining an authentication token or certificate, or that choose to use userid and password based authentication.
- get_publisherAssertions
- Obtains the full set of publisher assertions that are associated with an individual publisher account. Publisher assertions are used to control publicly visible business relationships.
- get_registeredInfo
- Gets an abbreviated list of all businessEntity and tModel data that are controlled by the individual associated with the credentials passed.
- save_binding
- Saves or updates a complete bindingTemplate element. this message can be used to add or update one or more bindingTemplate elements as well as the container/contained relationship that each bindingTemplate has with one or more existing businessService elements.
- save_business
- Saves or updates information about a complete businessEntity element. This API has the broadest scope of all the save_xx API calls in the publisher API, and can be used to make sweeping changes to the published information for one or more businessEntity elements controlled by an individual.
- save_service
- Adds or updates one or more businessService elements exposed by a specified businessEntity.
- save_tModel
- Adds or updates one or more registered tModel elements.
- set_publisherAssertions
- Manages all of the tracked relationship assertions associated with an individual publisher account.
For full details of the syntax of the above queries, refer to the API specification at http://www.uddi.org/pubs/ProgrammersAPI_v2.pdf.
UDDI Registry Application Programming Interface