5.1

Table Of Contents
Copy or Move a vApp
The cloneVApp request makes a copy of the vApp referenced in the Source element of the request body. The
request specifies a new name and, optionally, a new description for the copy. The request can optionally include
an IsSourceDelete element whose value specifies whether to delete the source vApp after the copy is complete.
If IsSourceDelete is missing from the request body, or present with a value of false, the source object remains
in place after the copy is complete. Setting IsSourceDelete to true effectively moves the vApp.
NOTE You cannot copy or move a vApp that is deployed.
For more information and an example, see the cloneVApp operation in the schema reference.
Capturing and Importing vApps
You can capture a vApp to create a vApp template from it. If you are a system administrator, you can also
import vApps and vApp templates from vSphere.
Every vDC includes a Link of the following form:
<Link
rel="add"
type="application/vnd.vmware.vcloud.captureVAppParams+xml"
href="https://vcloud.example.com/api/vdc/5/action/captureVApp"/>
You can POST a CaptureVAppParams request to this link to capture an undeployed vApp. The operation returns
a VAppTemplate that you can add to a catalog. Instantiating this template recreates the vApp from which it was
captured. Most elements of a vApp template are read-only, but you can instantiate a template, modify the
resulting vApp, and then capture it to create a modified version of the template.
For more information and an example, see the captureVApp operation in the schema reference.
Importing vApps or vApp Templates from vSphere
A system administrator can import vApps and vApp templates from vSphere. See “Import a Virtual Machine
from vCenter,” on page 228.
Cataloging vApp Templates and Media Images
Catalogs can contain references to vApp templates and media images. A system administrator or a privileged
member of the organization that owns the catalog can create and remove these references.
Although you can retrieve references to vApp templates and media images directly from the vDC to which
they were uploaded, it is common practice to place references to such assets in one of an organization’s catalogs.
When you place the references in a catalog, the assets are easier to discover, because a catalog can include assets
from all vDCs in an organization. You also have more flexible administrative control over them, because you
can restrict access to catalogs and the items in them to specific users and groups. Assets such as vApp templates
are not enabled for most uses until you include them in a catalog. For example, you cannot instantiate a vApp
template that is not included in a catalog. A media image that is not included in a catalog cannot be copied or
inserted by anyone but its owner.
vCloud API Programming Guide
72 VMware, Inc.