5.5.1

6 (Optional) To import a package with the tags that it contains and overwrite existing tag values, use the
tagImportMode parameter in the POST request:
POST http://{vcoHost}:{port}/vco/api/packages/?tagImportMode=ImportAndOverwriteExistingValue
If the POST request is successful, you receive the status code 202.
Export a Package
You can export a package by using the Orchestrator REST API and download the package as a file.
By default, Orchestrator packages are exported with attribute values of configuration elements and global
tags. You can export a package without attribute values or global tags by using parameters in the request.
You can also specify a custom name for the package file that you download.
Procedure
1 In a REST client application, add a request header with the following values.
n
Name: accept
n
Value: application/zip
2 Make a GET request at the URL of the package that you want to export:
GET http://{vcoHost}:{port}/vco/api/packages/{package_name}/
3 (Optional) To set a custom name for the exported package, use the packageName parameter in the GET
request:
GET http://{vcoHost}:{port}/vco/api/packages/{package_name}/?packageName={custom_name}
4 (Optional) To export a package without the attribute values of the configuration elements from the
package, use the exportConfigurationAttributeValues parameter in the GET request:
GET http://{vcoHost}:{port}/vco/api/packages/{package_name}/?
exportConfigurationAttributeValues=false
5 (Optional) To export a package without global tags, use the exportGlobalTags parameter in the GET
request:
GET http://{vcoHost}:{port}/vco/api/packages/{package_name}/?exportGlobalTags=false
If the GET request is successful, you receive the status code 200. The package binary content is available as an
attachment with a default file name package_name.package. You can save the file with a REST client
application.
Import a Resource
You can import a resource by using the Orchestrator REST API.
Depending on the library of your REST client application, you can use custom code that defines the
properties of the resource.
Prerequisites
The resource binary content should be available as multi-part content. For details, see RFC-2387.
Procedure
1 In a REST client application, add request headers to define the properties of the resource that you want
to import.
Developing a Web Services Client for VMware vCenter Orchestrator
36 VMware, Inc.