The UDDI Publish API allows you to publish, delete and update
information contained in a UDDI registry. The messages defined in this section
all behave synchronously.
Use the IBM UDDI Version 3 Client for Java (see IBM UDDI Version 3 Client)
to access programmatically all API calls and arguments supported by the UDDI
Version 3 Registry. You can also access the API functions graphically by using
the UDDI user interface, however not all of the functions are available with
this method.
The
UDDI Version 3 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 syntax of the above queries, refer
to the UDDI Version 3 API specification at http://www.uddi.org/pubs/uddi_v3.htm.