WAS v8.5 > Reference > Developer detailed usage informationCustody 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 v3 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. To access the API functions graphically, we 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 transfer takes place. Instead, the relinquishing publisher uses this API to obtain permission from the custodial node, in the form of a transferToken, to undertake the transfer. The relinquishing publisher gives the transferToken to the recipient publisher, who must invoke the transfer_entities API to transfer the entities.
- transfer_entities
- Performs the 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 v3 API specification.
Related
Use the UDDI registry user interface
Reference:
UDDI v3 Client
Related information: