4.2.1
Table Of Contents
- Administering VMware vCenter Orchestrator
- Contents
- Administering VMware vCenter Orchestrator
- Updated Information
- The Orchestrator Client
- Managing Workflows
- Creating Resource Elements
- Managing Actions
- Using Packages
- Setting System Properties
- Disable Access to the Orchestrator Client By Nonadministrators
- Disable Access to Workflows from Web Service Clients
- Setting Server File System Access from Workflows and JavaScript
- Set JavaScript Access to Operating System Commands
- Set JavaScript Access to Java Classes
- Set Custom Timeout Property
- Modify the Number of Objects a Plug-In Search Obtains
- Modify the Number of Concurrent and Delayed Workflows
- Maintenance and Recovery
- Index
Key Concepts of Workflows
Workflows consist of actions, attributes, parameters, and schema. Orchestrator saves a workflow token every
time a workflow runs, recording the details of that specific run of the workflow.
n
Workflow User Permissions on page 23
Orchestrator defines levels of permissions that you can apply to users or groups to allow or deny them
access to workflows.
n
Workflow Credentials on page 24
Each workflow has a default running credential that the workflow starter issues. The credentials with
which a workflow runs depend on the manner in which the workflow is started.
n
Workflow Attributes on page 24
Workflow attributes act as global constants and global variables throughout a workflow. Workflow
elements process data that they receive as input parameters, and set the resulting output as workflow
attributes or output parameters.
n
Workflow Parameters on page 24
Workflows receive input parameters and generate output parameters when they run.
n
Workflow Schema on page 25
A workflow schema is a graphical representation of a workflow that shows the workflow as a flow
diagram of interconnected workflow elements.
n
View Workflow Schema on page 25
You view a workflow schema in the schema tab for that workflow in the Orchestrator client.
n
Workflow Tokens on page 25
A workflow token represents a workflow that is running or has run.
n
Workflow Token States on page 26
Each time you run a workflow, a workflow token appears under that workflow as a new leaf node in the
workflows hierarchical list. Clicking a workflow token in the hierarchical list shows tabs in the right pane
that show information about the workflow token.
n
Locking Mechanism on page 26
You can modify a workflow schema while it is running. This ability is useful in testing or debugging but
not in production environment.
Workflow User Permissions
Orchestrator defines levels of permissions that you can apply to users or groups to allow or deny them access
to workflows.
View
The user can view the elements in the workflow, but cannot view the schema
or scripting.
Inspect
The user can view the elements in the workflow, including the schema and
scripting.
Execute
The user can run the workflow.
Edit
The user can edit the workflow.
Admin
The user can set permissions on the workflow.
Permissions are not cumulative. For example, to grant a user full permissions, you must set all the permissions,
not just Admin. All the permissions require the View permission.
Chapter 2 Managing Workflows
VMware, Inc. 23