5.5.1

Prerequisites
The workflow 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 workflow that you
want to import.
2 Make a POST request at the URL of the workflow objects:
POST http://{vcoHost}:{port}/vco/api/workflows/
If the POST request is successful, you receive the status code 202.
Export a Workflow
You can export a workflow by using the Orchestrator REST API and download the workflow as a file.
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 workflow that you want to export:
GET http://{vcoHost}:{port}/vco/api/workflows/{workflowID}/
If the GET request is successful, you receive the status code 200. The workflow binary content is available as
an attachment with a default file name workflow_name.workflow. You can save the file with a REST client
application.
Import an Action
You can import an action 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 action.
Prerequisites
The action 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 action that you want to
import.
2 Make a POST request at the URL of the action objects:
POST http://{vcoHost}:{port}/vco/api/actions/
If the POST request is successful, you receive the status code 202.
Developing a Web Services Client for VMware vCenter Orchestrator
34 VMware, Inc.