4.1
Table Of Contents
- vCenter Orchestrator Administration Guide
- Contents
- Updated Information
- About This Book
- Introduction to VMware vCenter Orchestrator
- The Orchestrator Client
- Managing Workflows
- Creating Resource Elements
- Using Plug-Ins
- 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
n
Workflow Attributes on page 31
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 31
Workflows receive input parameters and generate output parameters when they run.
n
Workflow Schema on page 32
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 32
You view a workflow schema in the schema tab for that workflow in the Orchestrator client.
n
Workflow Tokens on page 32
A workflow token represents a workflow that is running or has run.
n
Workflow Token States on page 33
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 33
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.
If you do not set any permissions on a workflow, the workflow inherits the permissions from the folder that
contains it. If you do set permissions on a workflow, those permissions override the permissions of the folder
that contains it, even if the permissions of the folder are more restrictive.
vCenter Orchestrator Administration Guide
30 VMware, Inc.