17.12.5. UDDI API Calls
This section describes the Virtuoso UDDI-related messages. These messages are divided into APIs for authentication, inquiry, and publication.
Inquiry API Functions
The inquiry API messages
find_service , and
find_tModel all accept an optional
findQualifiers . This argument
provides a means to allow the caller to override default search
The messages in this section represent inquiries that anyone can make of any UDDI-enabled server at any time. These messages all behave synchronously and are required to be exposed via HTTP POST only. Other synchronous or asynchronous mechanisms may be provided at the discretion of the individual UDDI-enabled server or compatible registry.
The publicly accessible queries are:
find_binding: Used to locate specific bindings within a registered
businessService. Returns a
find_business: Used to locate information about one or more businesses. Returns a
find_service: Used to locate specific services within a registered
businessEntity. Returns a
find_tModel: Used to locate one or more
tModelinformation structures. Returns a
get_bindingDetail: Used to get full
bindingTemplateinformation suitable for making one or more service requests. Returns a
get_businessDetail: Used to get the full
businessEntityinformation for a one or more businesses. Returns a
get_businessDetailExt: Used to get extended
businessEntityinformation. Returns a
get_serviceDetail: Used to get full details for a given set of registered
businessServicedate. Returns a
get_tModelDetail: Used to get full details for a given set of registered
tModeldata. Returns a
Publishing API Functions
The messages in this section represent inquiries that require authenticated access to an operator site. Each business should initially select one UDDI-enabled server to host their information. Once chosen, information can only be updated at the site originally selected.
The messages defined in this section all behave synchronously and are only callable via HTTP-POST. HTTPS is used exclusively for all the calls defined in this publisher's API.
save_binding: Used to register new
bindingTemplateinformation or update existing
bindingTemplateinformation. Use this to control information about technical capabilities exposed by a registered business.
save_business: Used to register new
businessEntityinformation or update existing
businessEntityinformation. Use this to control the overall information about the entire business. Of all the save messages, this one has the broadest effect.
save_service: Used to register or update complete information about a
businessServiceexposed by a specified
save_tModel: Used to register or update complete information about a
delete_binding: Used to remove an existing
bindingTemplatefrom the bindingTemplates collection that is part of a specified
delete_business: Used to delete registered
businessEntityinformation from the registry.
delete_service: Used to delete an existing
businessServicefrom the businessServices collection that is part of a specified
delete_tModel: Used to delete registered information about a
tModel. If there are any references to a
tModelwhen this call is made, the
tModelwill be marked deleted instead of being physically removed.