Publish API for the UDDI V3 registry

Use the UDDI publish API to publish, delete, and update information that is contained in a UDDI registry. The messages that are defined in this section all behave synchronously.

To access all API calls and arguments that are supported by the UDDI V3 registry programmatically, use the UDDI V3 Client for Java (see UDDI V3 Client). To access the API functions graphically, you can use the UDDI user interface, but not all functions are available with this method.

The UDDI V3 registry supports the following Publication API calls:

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.

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_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 query syntax, refer to the UDDI V3 API specification at http://www.uddi.org/pubs/uddi_v3.htm.

Related tasks

Related Reference

Reference topic