5.5.1

Figure 3‑1. Process for Creating Orchestrator Web Service Applications
Create a VSOWebControl object
to connect to the Web service
HTTP
(Optional) check the connection to
the server using echoWorkflow
(Optional) check for plug-ins using
getAllPlugins
If necessary, find objects to execute workflows upon
Use find to locate an object of a
particular type, that matches a
particular query criterion
Use hasChildrenInRelation and
findRelation to find children of a
particular relation type
Use findForId to Iocate an object
with a particular ID number
Find a workflow
Use getAllWorkflows to list all
workflows
Use getWorkflowsForId to find a
workflow based on its unique ID
Use getWorkflowsWithName to
find workflows with a particular name
(Optional) check whether the current
user has rights to read, execute, or
edit the workflow using hasRights
HTTPS
Define the workflow's
inParameters
Execute the workflow using
executeWorkflow, which creates a
WorkflowToken
Perform different actions while the WorkflowToken executes
Provide runtime input
with
answerWorkflow
Input
Cancel the workflow
using
cancelWorkflow
Send a custom event
using
sendCustomEvent
When the WorkflowToken completes,
check the results with
getWorkflowTokenResult
Display, process, or otherwise act
upon the results of the workflow
Check the status of
the workflow with
getWorkFlowToken
Status
Find other
WorkflowToken
objects using
getWorkFlowToken
ForId
Follow the broad stages of development illustrated to create Orchestrator Web services client applications
that satisfy most of your requirements.
Developing a Web Services Client for VMware vCenter Orchestrator
54 VMware, Inc.