Publish API for the UDDI Version 3 registry

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

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

The UDDI Version 3 registry supports the following Publish API calls:

add_publisherAssertions

Adds one or more publisherAssertions to the assertion collection of an individual publisher.

delete_binding

Deletes one or more instances of bindingTemplate data from the UDDI registry.

delete_business

Removes one or more business registrations and all direct contents from a UDDI registry.

delete_publisherAssertions

Removes one or more publisherAssertion elements from an assertion collection of a publisher.

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 tModel entities 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 to determine the status of current and outstanding publisher assertions that involve any of the business registrations that the individual publisher account manages. A publisher can use this message to see the status of assertions that they have made, and to see assertions that others have made that involve businessEntity structures that the calling publisher account controls.

get_publisherAssertions

Obtains the full set of publisher assertions associated with an individual publisher account. Publisher assertions are used to control publicly visible business relationships.

get_registeredInfo

Obtains 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 or 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 comprehensive changes to the published information for one or more businessEntity elements an individual controls.

save_service

Adds or updates one or more businessService elements that a specified businessEntity exposes.

save_tModel

Adds or updates one or more registered tModel entities.

set_publisherAssertions

Manages all the tracked relationship assertions associated with an individual publisher account.

For full details of the Publish API syntax, refer to the UDDI Version 3 API specification.

Use the UDDI registry user interface

UDDI Version 3 Client

UDDI Version 3.0.2 Specification