<uddi_save_business generic="1.0" xmlns="urn:uddi-org:api" > <authInfo/> <businessEntity/> [<businessEntity/>...] | <uploadRegister/> [<uploadRegister/>...] </uddi_save_business>
The uddi_save_business message is used to save or update information about a complete businessEntity structure. This message has the broadest scope of all of the save calls in the publisher's API, and can be used to make sweeping changes to the published information for one or more businessEntity structures controlled by an identity.
Either businessEntity arguments or uploadRegister arguments may be passed in a given uddi_save_business message, but not both. Any number of businessEntity or uploadRegister values can be passed in a single save (up to a server-imposed limit), but the two types of parameters may not be mixed.
To make this call perform an update to existing registered data, the keyed entities (businessEntity, businessService, bindingTemplate or tModel) should have uuid_key values that correspond to the registered data.
Data can be deleted with this call when registered information is different from the new information provided. Any businessService or bindingTemplate structures that are found in the controlling server but that are missing from the businessEntity information provided in or referenced by this call will be deleted from the registry after processing this call.
Data contained within one or more businessEntity structures can be rearranged with this function when data passed to this function redefines parent container relationships for other registered information. For instance, if a new businessEntity is saved with information about a businessService that is registered already as part of a separate businessEntity, the businessService is moved from its current container to the new businessEntity. This only applies if the entity controlling the data referenced is the same entity identified in the uddi_save_business message.
If the file located by the uploadRegister URL is an extended business entity (businessEntityExt) structure, only the businessEntity data found within that structure will be registered.
If a businessEntity element is used to save data, then the UDDI-enabled server will create a URL specific to that server. This URL can be used to retrieve via HTTP-GET the businessEntity structure being registered. This information will be added - if not already present - to the discoveryURL's collection automatically with a useType value of businessEntity.
This message returns a businessDetail message that reflects the new registered information for the businessEntity information provided.
If an error occurs in processing this message, a dispositionReport structure will be returned to the caller in a SOAP Fault. The following error information will be relevant: