4.0

Find Workflows in the Orchestrator Server
When you have found the objects with which to interact, you must find the workflows that perform these
interactions.
The Orchestrator Web service API includes the following operations to find all the workflows running in a
given environment, to find a workflow with a particular name, or to find workflows with a particular ID.
n
getAllWorkflows
n
getWorkflowsWithName
n
getWorkflowForID
Find Workflows by Using the getAllWorkflows Operation
The getAllWorkflows operation lists all workflows that a user can access as an array of Workflow objects.
Because the getAllWorkflows operation returns Workflow objects that contain all the information about a
workflow, it is useful for applications that require full information about workflows, such as the workflow's
name, ID, description, parameters, and attributes.
Prerequisites
You must have implemented Web service operations in your client application to find objects in the
Orchestrator server.
Procedure
u
Create an array of Workflow objects by calling the getAllWorkflows operation.
Workflow[] workflows = vsoWebControl.getAllWorkflows(username, password);
The preceding code example calls getAllWorkflows to get an array of Workflow objects that the Web service
client can run.
You found workflows in the Orchestrator server that the Web service client can run on objects.
What to do next
Implement operations in the Web services client to run the workflows it finds.
Find Workflows by Using the getWorkflowsWithName Operation
If you know the name of a particular workflow, as it is defined in the Orchestrator client, the Web service
application can obtain this workflow using its name or part of its name.
The getWorkflowsWithName operation returns an array of workflows, so you can use it to match several
workflows by using wildcards.
Prerequisites
You must have implemented Web service operations in your client application to find objects in the
Orchestrator server.
vCenter Orchestrator Developer's Guide
256 VMware, Inc.