Custody and Ownership Transfer API for the UDDI V3 registry

 

Use the UDDI Custody and Ownership Transfer API to transfer custody or ownership of one or more entities that are contained in a UDDI Version 3 registry. The UDDI V3 registry supports only intra-node ownership transfer; it does not support inter-node custody transfer.

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 Custody and Ownership Transfer API calls:

discard_transferToken

Discards a transferToken that is obtained through the get_transferToken API.

get_transferToken

Initiates the transfer of ownership of one or more businessEntity or tModel entities from one publisher to another. When the API is invoked, no actual transfer takes place. Instead, the relinquishing publisher uses this API to obtain permission from the custodial node, in the form of a transferToken, to perform the transfer. The relinquishing publisher gives the transferToken to the recipient publisher, who must invoke the transfer_entities API to actually transfer the entities.

transfer_entities

Performs the actual transfer of entities when called by the recipient publisher. The recipient publisher must specify an unexpired transferToken on the call.

For details of the query syntax, refer to the UDDI Version 3 API specification at http://www.uddi.org/pubs/uddi_v3.htm.

---

 

Related tasks

UDDI registry client programming

 

Related Reference

UDDI registry Application Programming Interface

 

Reference topic