<back to all web services
WorkloadManageMove
The following routes are available for this service:POST | /workloadmanage/move | | |
---|
WorkloadManageMove Parameters:Name | Parameter | Data Type | Required | Description |
---|
DatacenterLocationDestination | body | string | No | |
orgNameDestination | body | string | No | |
vdcNameDestination | body | string | No | |
vAppNameDestination | body | string | No | |
WorkloadManageBase Parameters:Name | Parameter | Data Type | Required | Description |
---|
userId | form | string | No | |
orgNameSource | form | string | No | |
vdcNameSource | form | string | No | |
vAppNameSource | form | string | No | |
vmNameSource | form | string | No | |
DataCenterLocationSource | form | string | No | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /workloadmanage/move HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<WorkloadManageMove xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/N3TAPI.Services">
<DataCenterLocationSource>String</DataCenterLocationSource>
<orgNameSource>String</orgNameSource>
<userId>String</userId>
<vAppNameSource>String</vAppNameSource>
<vdcNameSource>String</vdcNameSource>
<vmNameSource>String</vmNameSource>
<DatacenterLocationDestination>String</DatacenterLocationDestination>
<orgNameDestination>String</orgNameDestination>
<vAppNameDestination>String</vAppNameDestination>
<vdcNameDestination>String</vdcNameDestination>
</WorkloadManageMove>