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
8 Click a workflow in the hierarchical list to display information about the workflow in the right pane.
9 In the right pane, select whether to run the workflow now or at a later time.
Option Action
Run the workflow now
a Click Start Workflow to run the workflow.
b Provide the required input parameters and click Submit to run the
workflow.
Run the workflow at a later time
a Click Schedule Workflow to run the workflow at a later time.
b Provide the time, date, and recurrence information to set when and how
often to run the workflow and click Next.
c Provide the required input parameters and click Submit to schedule the
workflow.
You can use the weboperator Web view to run workflows on objects in your inventory from a Web browser
rather than from the Orchestrator client.
What to do next
If you only need a Web view to access the inventory and run workflows, the standard weboperator Web view
should meet your requirements. If you require more complex functionality from a Web view, you can use the
Web components and default Web view template that Orchestrator provides to develop custom Web views.
Policies
Policies are event triggers that monitor the activity of the system. Policies respond to predefined events issued
by changes in the status or performance of certain defined objects.
Policies are a series of rules, gauges, thresholds and event filters that run certain workflows or scripts when
specific predefined events occur in Orchestrator or in the technologies that Orchestrator accesses through plug-
ins. Orchestrator constantly evaluates the policy rules as long as the policy is running. For instance, you can
implement policy gauges and thresholds that monitor the behavior of vCenter Server objects of the
VC:HostSystem and VC:VirtualMachine types.
NOTE Policies are deprecated as of Orchestrator 4.1. Policy development is not supported in releases of
Orchestrator later than 4.1.
Orchestrator defines the following types of policy:
Policy Templates
Master policies. Policy templates are not linked to real objects. They are abstract
sets of rules that define the behavior to implement if a certain abstract event
occurs. You can see existing policy templates and create templates in the Policy
Templates view in the Orchestrator client.
Policies
Policies are instances of a template or standalone event triggers that are linked
to real objects, and that are triggered by real-life events. You can see existing
policies and create policies in the Policies view in the Orchestrator client.
You can organize policy templates into folders, for easier navigation.
Chapter 2 The Orchestrator Client
VMware, Inc. 23