VMware vCenter Orchestrator - 4.0.4, vCenter Orchestrator - 4.0.2, vCenter Orchestrator - 4.0.3, vCenter Orchestrator - 4.0.1, vCenter Orchestrator - 4.0 Administrator’s Guide

vCenter Orchestrator Administration
Guide
vCenter Orchestrator 4.0.1
This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
EN-000226-05
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2008–2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
2 VMware, Inc.

Contents

Updated Information 7
About This Book 9
Introduction to VMware vCenter Orchestrator 11
1
Key Features of the Orchestrator Platform 11
Orchestrator User Roles and Related Tasks 12
Orchestrator Architecture 13
The Orchestrator Client 15
2
Log in to the Orchestrator Client 15
Access the Orchestrator API Explorer 16
User Preferences 16
My Orchestrator View 18
Configurations View 18
Packages View 19
Scheduler View 19
Workflows View 20
Components of the Workflows View 20
Actions View 20
Resources View 21
Inventory View 21
Web Views View 21
Weboperator Web View 22
Start the Weboperator Web View 22
Policies 23
VMware, Inc.
Managing Workflows 25
3
Standard Workflows in the Workflow Library 25
Workflow Library Additions 26
Key Concepts of Workflows 29
Workflow User Permissions 29
Workflow Credentials 30
Workflow Attributes 30
Workflow Parameters 31
Workflow Schema 31
View Workflow Schema 31
Workflow Tokens 32
Workflow Token States 32
Locking Mechanism 33
Set User Permissions on a Workflow 33
Run a Workflow 33
3
Respond to a Request for a User Interaction 35
Scheduling Workflows 35
Schedule a Workflow 35
Edit the Workflow Recurrence Pattern 36
Creating Resource Elements 37
4
View a Resource Element 37
Import an External Object to Use as a Resource Element 38
Edit the Resource Element Information and Access Rights 38
Save a Resource Element to a File 39
Update a Resource Element 39
Add a Resource Element to a Workflow 40
Add a Resource Element to a Web View 40
Using Plug-Ins 43
5
Default Orchestrator Plug-Ins 44
Using the SSH Plug-In 46
Generate a Key Pair 46
Change the Key Pair Passphrase 47
Register an Orchestrator Public Key on an SSH Host 47
Run an SSH Command 48
Copy a File from an SSH Host 48
Copy a File to an SSH Host 49
Using the XML Plug-In 49
Running the XML Plug-In Sample Workflows 49
Managing Actions 53
6
Create an Action 53
Duplicate an Action 54
Export an Action 54
Import an Action 55
Move an Action 55
Find Elements That Implement an Action 55
Using Packages 57
7
Create a Package 57
Set User Permissions on a Package 58
Export a Package 59
Import a Package 60
Get and Synchronize a Remote Package 60
Remove a Package 61
Setting System Properties 63
8
Disable Access to the Orchestrator Client By Nonadministrators 63
Disable Access to Workflows from Web Service Clients 64
Setting Server File System Access from Workflows and JavaScript 64
Set Server File System Access for Workflows and JavaScript 65
Set JavaScript Access to Operating System Commands 66
4 VMware, Inc.
Set JavaScript Access to Java Classes 67
Set Custom Timeout Property 68
Modify the Number of Objects a Plug-In Search Obtains 68
Contents
Maintenance and Recovery 71
9
Orchestrator Server Fails to Start 72
Revert to the Default Password for Orchestrator Configuration 72
Change the Web View SSL Certificate 73
Orchestrator Log Files 74
Logging Persistence 75
Define the Server Log Level 76
Change the Size of Server Logs 77
Export Orchestrator Log Files 77
Loss of Server Logs 78
Maintaining the Orchestrator Database 78
Index 79
VMware, Inc. 5
6 VMware, Inc.

Updated Information

This vCenter Orchestrator Administration Guide is updated with each release of the product or when necessary.
This table provides the update history of the vCenter Orchestrator Administration Guide.
Revision Description
EN-000226-05 Clarified the relation between the com.vmware.js.allow-local-process system property and the js-
io-conf file in “Set JavaScript Access to Operating System Commands,” on page 66.
EN-000226-04
EN-000226-03
EN-000226-02
EN-000226-01
EN-000226-00 Updates for the release of Orchestrator 4.0.1:
EN-000127-00 Initial release of Orchestrator 4.0.
n
Added troubleshooting information in “Orchestrator Server Fails to Start,” on page 72.
n
Added instructions about changing the server log level in “Define the Server Log Level,” on page 76.
n
Updated section “Workflow Credentials,” on page 30.
n
Updated Chapter 6, “Managing Actions,” on page 53.
n
Corrected description of Execute permission in “Set User Permissions on a Package,” on page 58.
n
Removed cross-references before tables and figures.
n
Added information about using Orchestrator administrative tools and defining user preferences in
Chapter 2, “The Orchestrator Client,” on page 15.
n
Added a new section, Chapter 5, “Using Plug-Ins,” on page 43.
n
Added a new section, “Orchestrator Log Files,” on page 74.
n
Added instructions about responding to a user interaction request in “Respond to a Request for a User
Interaction,” on page 35.
n
Added a procedure about restoring the default Orchestrator password in “Revert to the Default
Password for Orchestrator Configuration,” on page 72.
n
Added instructions about changing the SSL certificate for Web views in “Change the Web View SSL
Certificate,” on page 73.
n
Added a new section, Chapter 4, “Creating Resource Elements,” on page 37.
n
Added information about new workflows in the Orchestrator library in “Workflow Library
Additions,” on page 26.
n
Added a new section, Chapter 8, “Setting System Properties,” on page 63.
n
Added information about workflow user permissions and credentials in “Workflow User
Permissions,” on page 29 and “Workflow Credentials,” on page 30.
n
Described the workflow locking mechanism in “Locking Mechanism,” on page 33.
n
Added a new section, “Scheduling Workflows,” on page 35.
n
Added information about the sample Orchestrator Web view in “Weboperator Web View,” on page 22.
n
Added a procedure about removing packages in “Remove a Package,” on page 61.
VMware, Inc. 7
8 VMware, Inc.

About This Book

The VMware vCenter Orchestrator Administration Guide provides information and instructions about using and maintaining VMware® vCenter Orchestrator. It also describes how to manage workflows, plug-ins, packages, inventory and policies.
Intended Audience
This book is intended for advanced vCenter administrators and experienced system administrators who are familiar with virtual machine technology and datacenter operations, as well as anyone who wants to:
n
Automate frequently repeated processes related to the management of the virtual environment.
n
Manage multiple automated processes across and among heterogeneous systems.
n
Provide transparency in IT processes by centralizing automated scripts.
n
React faster to unplanned changes in the virtual environment.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions of the terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
Document Feedback
VMware welcomes your suggestions for improving our documentation. If you have comments, send your feedback to docfeedback@vmware.com.
Technical Support and Education Resources
The following technical support resources are available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs.
Online and Telephone Support
VMware, Inc. 9
To use online support to submit technical support requests, view your product and contract information, and register your products, go to
http://www.vmware.com/support.
Customers with appropriate support contracts should use telephone support for the fastest response on priority 1 issues. Go to
http://www.vmware.com/support/phone_support.html.
Support Offerings
VMware Professional Services
To find out how VMware support offerings can help meet your business needs, go to http://www.vmware.com/support/services.
VMware Education Services courses offer extensive hands-on labs, case study examples, and course materials designed to be used as on-the-job reference tools. Courses are available onsite, in the classroom, and live online. For onsite pilot programs and implementation best practices, VMware Consulting Services provides offerings to help you assess, plan, build, and manage your virtual environment. To access information about education classes, certification programs, and consulting services, go to
http://www.vmware.com/services.
10 VMware, Inc.
Introduction to VMware vCenter
Orchestrator 1
VMware vCenter Orchestrator is a development and process-automation platform that provides a library of extensible workflows to allow you to create and run automated, configurable processes to manage the VMware vCenter infrastructure as well as other VMware and third-party technologies.
Orchestrator exposes every operation in the vCenter Server API, allowing you to integrate all of these operations into your automated processes. Orchestrator also allows you to integrate with other management and administration solutions through its open plug-in architecture.
This chapter includes the following topics:
n
“Key Features of the Orchestrator Platform,” on page 11
n
“Orchestrator User Roles and Related Tasks,” on page 12
n
“Orchestrator Architecture,” on page 13

Key Features of the Orchestrator Platform

Orchestrator is composed of three distinct layers: an orchestration platform that provides the common features required for an orchestration tool, a plug-in architecture to integrate control of subsystems, and a library of workflows. Orchestrator is an open platform that can be extended with new plug-ins and libraries, and can be integrated into larger architectures through a SOAP API.
The following list presents the key Orchestrator features.
Persistence
Central management
Check-pointing
Versioning
VMware, Inc. 11
Production grade external databases are used to store relevant information, such as processes, workflow states, and configuration information.
Orchestrator provides a central way to manage your processes. The application server-based platform, with full version history, allows you to have scripts and process-related primitives in one place. This way, you can avoid scripts without versioning and proper change control spread on your servers.
Every step of a workflow is saved in the database, which allows you to restart the server without losing state and context. This feature is especially useful for long-running processes.
All Orchestrator Platform objects have an associated version history. This feature allows basic change management when distributing processes to different project stages or locations.
Scripting engine
Workflow engine
Policy engine
Web 2.0 front end
The Mozilla Rhino JavaScript engine provides a way to create new building blocks for Orchestrator Platform. The scripting engine is enhanced with basic version control, variable type checking, name space management and exception handling. It can be used in the following building blocks:
n
Actions
n
Workflows
n
Policies
The workflow engine allows you to capture business processes. It uses the following objects to create a step-by-step process automation in workflows:
n
Workflows and actions that Orchestrator provides.
n
Custom building blocks created by the customer
n
Objects that plug-ins add to Orchestrator
Users, other workflows, a schedule, or a policy can start workflows.
The policy engine allows monitoring and event generation to react to changing conditions in the Orchestrator server or plugged-in technology. Policies can aggregate events from the platform or any of the plug-ins, which allows you to handle changing conditions on any of the integrated technologies.
The Web 2.0 front end allows you to integrate Orchestrator functions into Web­based interfaces, using Web views. For example, you can create Web views that add buttons to start workflows from a page in your company's Intranet. It provides a library of user customizable components to access vCO orchestrated objects and uses Ajax technology to dynamically update content without reloading complete pages.
Security
Orchestrator provides the following advanced security functions:
n
Public Key Infrastructure (PKI) to sign and encrypt content imported and exported between servers
n
Digital Rights Management (DRM) to control how exported content might be viewed, edited and redistributed
n
Secure Sockets Layer (SSL) encrypted communications between the desktop client and the server and HTTPS access to the Web front end.
n
Advanced access rights management to provide control over access to processes and the objects manipulated by these processes.

Orchestrator User Roles and Related Tasks

vCenter Orchestrator provides different tools and interfaces based on the specific responsibilities of the two global user roles: Administrators and End Users.
Administrators
This role has full access to all of the Orchestrator platform capabilities. Basic administrative tasks include the following items:
n
Installing and configuring Orchestrator
n
Managing access rights for Orchestrator and applications
n
Importing and exporting packages
n
Enabling and disabling Web views
12 VMware, Inc.
Orchestrator
database
vCenter
Orchestrator
Client application
vCenter
Server
browser access web service
workflow library
vCenter VI3 WMI XML SSH JDBC SMTP
3rd-party
plug-in
directory
services
workflow engine
Chapter 1 Introduction to VMware vCenter Orchestrator
n
Running workflows and scheduling tasks
n
Managing version control of imported elements
n
Creating new workflows and plug-ins
Developers
This role has full access to all of the Orchestrator platform capabilities. Developers are granted access to the Orchestrator client interface and have the following responsibilities:
n
n
n
End Users
Users in this role are granted access to only the Web front end. They can run and schedule workflows and policies that you make available in a browser by using Web views.

Orchestrator Architecture

Orchestrator contains a workflow library and workflow engine to allow you to create and run workflows that automate orchestration processes. You run workflows on the objects of different technologies that Orchestrator accesses through a series of plug-ins.
Orchestrator provides a standard set of plug-ins, including a plug-in to VMware vCenter Server, to allow you to orchestrate tasks in the different environments that the plug-ins expose.
Orchestrator also presents an open architecture to allow you to plug in external third-party applications to the orchestration platform. You can run workflows on the objects of the plugged-in technologies that you define yourself. Orchestrator connects to a directory services server to manage user accounts, and to a database to store information from the workflows that it runs. You can access Orchestrator and the workflows and objects it exposes through the Orchestrator client interface, through a Web browser, or through Web services.
Creating applications to extend the Orchestrator platform functionality
Automating processes by customizing existing workflows and creating new workflows and plug-ins
Customizing Web front ends for these processes, using Web 2.0
Figure 1-1 shows the architecture of Orchestrator.
Figure 1-1. VMware vCenter Orchestrator Architecture
NOTE The VMware Infrastructure 3 and Microsoft plug-ins are not installed by default.
VMware, Inc. 13
14 VMware, Inc.

The Orchestrator Client 2

The Orchestrator client is an easy-to-use desktop application that allows you to perform daily administration tasks such as importing packages, running and scheduling workflows, and managing user permissions. The Orchestrator client also serves as an IDE for creating or customizing workflows.
This chapter includes the following topics:
n
“Log in to the Orchestrator Client,” on page 15
n
“Access the Orchestrator API Explorer,” on page 16
n
“User Preferences,” on page 16
n
“My Orchestrator View,” on page 18
n
“Configurations View,” on page 18
n
“Packages View,” on page 19
n
“Scheduler View,” on page 19
n
“Workflows View,” on page 20
n
“Actions View,” on page 20
n
“Resources View,” on page 21
n
“Inventory View,” on page 21
n
“Web Views View,” on page 21
n
“Weboperator Web View,” on page 22
n
“Policies,” on page 23

Log in to the Orchestrator Client

To perform general administration tasks or to edit and create workflows, you must log in to the Orchestrator client interface.
Prerequisites
All components of the Orchestrator server must be configured and the VMware vCenter Orchestrator Server service must be running.
VMware, Inc.
15
Procedure
1 Select Start > Programs > VMware > vCenter Orchestrator Client or run the
vCenter Orchestrator Client.exe file that is located in
2 In the Host name field, type the IP address to which Orchestrator server is bound.
To check the IP address, log in to the Orchestrator configuration interface and check the Network tab.
3 Log in using the Orchestrator user name and password.
To check the credentials, log in to the Orchestrator configuration interface and check the LDAP tab.
The My Orchestrator view appears. This view summarizes the recent activities on the server, shows pending and running workflows, running policies, scheduled tasks, completed workflows, and elements you recently edited.
What to do next
You can import a package, start a workflow, or set root access rights on the system.

Access the Orchestrator API Explorer

Orchestrator provides an API Explorer to allow you to search the Orchestrator API and see the documentation of JavaScript objects that you can use in scripted elements.
install_directory
\Orchestrator\apps.
Procedure
u
You can access the API Explorer from either the Orchestrator client or from the Scripting tabs of the workflow, policy, and action editors.
n
To access the API Explorer from the Orchestrator client, click Tools > API Explorer in the Orchestrator client tool bar.
n
To access the API Explorer from the Scripting tabs of the workflow, policy, and action editors, click Search API on the left.
The API Explorer appears, allowing you to search all the objects and functions of the Orchestrator API.
What to do next
Use the API Explorer to write scripts for scriptable elements.

User Preferences

You can customize aspects of Orchestrator by using the User preferences tool in the Orchestrator client.
Your preferences are saved on the client side in the C:\Documents and
Settings\
a running Orchestrator server.
To access User preferences, selectTools > User preferences in the Orchestrator client tool bar.
The User preferences tool presents the following tabs.
Current_User
\.vmware\vmware-vmo.cfg file. The .vmware folder is created when you first connect to
General Tab
Table 2-1 lists the general customization options for the Orchestrator client.
16 VMware, Inc.
Chapter 2 The Orchestrator Client
Table 2-1. General Preferences
Option Description
Auto-edit new inserted The new elements that you add automatically open in an editor.
Script compilation delay The frequency of the background task that compiles the script and reports
errors in edit mode.
Show decision scripts You can see the decision script of the implemented decision function.
Delete non empty folder permitted You can delete a folder together with its subfolders and contents.
Size of run logs (number of lines) The maximum number of lines in the system log that the application
displays when you select a workflow run in the Orchestrator client and click Logs on the Schema tab.
The value must be greater than 0.
Server log fetch limit The maximum number of lines in the server logs that the application
fetches from the database and displays when you click any of the Events tabs in the Orchestrator client.
The value must be greater than 0.
Finder maximum size The maximum number of results that the searches return when you search
for elements such as actions or workflows. The value must be greater than 0.
Check usage when deleting an element The application checks if the element you are trying to delete is referenced
by other elements. If the element is used by another workflow, policy, or action, a warning message appears.
Check OGNL expression The application validates the OGNL expressions in the workflow
presentations.
Workflows Tab
Table 2-2 lists the customization options for the workflow editor and the Validate workflow action.
Table 2-2. Workflow Preferences
Option Description
Check task/decision IN/OUT parameters The application checks if the input and output parameters of an activity
are correctly bound to the corresponding input or output attribute of the workflow.
Check error in task's scripts The application validates the script in scriptable task elements.
Check workflow termination The application checks if each terminal transition of a workflow with
different possible outcomes is connected to an End Workflow schema element.
Check unreachable items The application checks if all activities are reachable.
Check unused workflow's parameters/attributes
Check unknown types from plug-ins The application checks if all parameters and attributes of a workflow are
Check for legacy 'Action' scripting call (slow) The application detects legacy actions calls and displays a warning
Use direct lines as workflow diagram links The connector tool uses direct lines to link the workflow schema elements.
Choose workflow in tree view The workflow selector displays a hierarchical tree viewer instead of the
Validate workflow before running it The application validates each workflow before allowing it to run.
The application checks if all parameters and attributes of a workflow are used.
of a known type.
message.
default list panel.
VMware, Inc. 17
Inventory Tab
You can enable the Use contextual menu in inventory option to display the workflows that are available for an inventory object. When the option is enabled and you right-click an object in the Orchestrator inventory, all available workflows for the object are displayed.
Script Editor Tab
You can customize the scripting engine from the Script Editor tab of the User preferences menu. You can disable automatic completion of lines, and change the default code formatting options.

My Orchestrator View

The My Orchestrator view in the Orchestrator client interface summarizes the most recent activities on the Orchestrator server, such as recently modified elements, pending and running workflows, running policies, completed workflows, and workflows that are waiting for user interaction.
From the My Orchestrator view you can perform common administrative tasks, such as running a workflow, importing a package, and setting root access rights.
The My Orchestrator view presents the following tabs.
Today
Executions
Waiting for Input
Tasks
Permissions

Configurations View

The Configurations view in the Orchestrator client allows you to create configuration elements. Creating configuration elements allows you to define common attributes across an Orchestrator server.
The Configurations view consists of a set of tabs that show information about a particular configuration element.
General
Displays the most recent workflow runs and modified elements.
Provides details about the different workflow runs. This information includes the workflow's running status, the user who started it, and the time and date when the workflow started and ended.
Displays a list of the workflows that are waiting for user inputs that you or members of your user group have permission to provide.
Displays information about the scheduled workflows, including name, running state, last run, and next run.
Displays the users and user groups who have root access rights to all published Web views and the workflows in the Orchestrator library. The possible permissions are View, Execute, Inspect, Edit, and Admin.
Displays general information about the configuration element, including its name and description, its version number, and the user permissions.
Attributes
Events
Permissions
18 VMware, Inc.
Displays the attributes that are added to the configuration element. All elements that are running in the server can call on the attributes that are set in a configuration element.
Displays all the events that are associated with this configuration element.
Displays which users and user groups have permission to access the configuration element.

Packages View

The Packages view in the Orchestrator client interface allows you to add, import, export, and synchronize packages.
The Packages view consists of a set of tabs that show different types of information about a particular package. In Edit Package mode, you can insert and remove elements on each tab.
Chapter 2 The Orchestrator Client
General
Workflows
Policies
Actions
Web View
Configurations
Resources
Used Plug-Ins
Permissions

Scheduler View

The Scheduler view in the Orchestrator client displays a list of all scheduled workflows in the system. The workflows are sorted by name or date, together with their status. You can use the Scheduler view to create, edit, suspend, resume, and cancel scheduled workflows.
Displays general information about the package, including its name, its legal owner, and a description.
Displays all the workflows that the selected package contains.
Displays the policy templates that the selected package contains.
Displays the actions that the selected package contains.
Displays the Web views that the selected package contains.
Displays the configuration elements that the selected package contains.
Displays the external resources embedded in the selected package.
Displays information about the plug-ins associated with the selected package. Plug-ins can have one or more packages associated with them.
Displays the permissions accorded to users or groups of users to interact with the package. The possible permissions are View, Execute, Inspect, Edit, and Admin.
When you select a scheduled workflow in the list, the Scheduler view presents the following tabs that display details about a particular workflow.
General
Recurrence
Executions
Permissions
Displays general information about the scheduled workflow, including name, start behavior, description, start date, startup user, the name of the scheduled workflow, and a list of the input values for the workflow.
Displays details about the recurrence pattern of the scheduled workflow.
Displays details about the different runs of a particular scheduled workflow. This information includes the workflow's running status, start and end date, and the user who started it. When you cancel a scheduled workflow, its log information is removed from the system. When you suspend a workflow, the log information is kept.
Displays the permissions accorded to users or groups of users to interact with the workflow. The possible permissions are View, Execute, Inspect, Edit, and Admin.
VMware, Inc. 19

Workflows View

The Orchestrator client interface features a Workflows view that provides access to the Orchestrator libraries of workflows.
The Workflows view allows you to view information about each workflow, create, edit, run workflows, and interact with the workflows.
The Orchestrator client uses the following icon to identify workflows:

Components of the Workflows View

The Workflows view consists of a set of tabs that show information about the selected workflow.
General
Inputs
Outputs
Schema
Presentation
Parameters Reference
Executions
Events
Displays general information about the workflow, including its name, its version number, the permissions, a description, and a list of the workflow's global attributes.
Lists all the input parameters that the workflow needs when it runs.
Lists the parameters that the workflow returns when it runs.
Shows a graphical representation of the workflow. Clicking an element in the schema shows information about that element in the bottom half of the Workflows view.
Constructs the input parameters dialog box that users see when they run a workflow. You define the groups in which the input parameters appear in the dialog box and provide descriptions to help users provide the correct parameters. You also define any parameter properties or constraints.
Shows all the input and output parameters in a single view. The tab also identifies the schema element that consumes or generates a parameter. You can optionally view the workflow attributes in this tab by clicking Show
Attributes. When you right-click an attribute or a parameter and select Show in schema, the corresponding schema element is highlighted.
Provides details about the different runs of the selected workflow. This information includes the workflow's running status, the user who started it, and the time and date when the workflow started and ended.
Provides information about each event that occurs while the workflow is running. This information includes the event's running status, the user who started it, and the time and date when the event was issued. The information is stored in the VMO_LogEvent table in the Orchestrator database.
Permissions
Lists the permissions accorded to users or groups of users to interact with the workflow. The possible permissions are View, Execute, Inspect, Edit, and Admin.

Actions View

The Actions view in the Orchestrator client interface allows you to access the libraries of predefined actions. In the Actions view, you can duplicate actions, export them to a file, or move them to a different module in the actions hierarchical list.
By expanding the nodes of the actions hierarchical list, you can browse available actions. When you select an action in the list, the right pane displays details about that action.
20 VMware, Inc.
The Actions view presents the following tabs.
Chapter 2 The Orchestrator Client
General
Scripting
Events
Permissions

Resources View

The Resources view in the Orchestrator client allows you to import external objects such as images, sysprep files, custom scripts, and HTML and XML templates and use them as resource elements in workflows and Web views.
The Resources view consists of a set of tabs that show information about a particular resource element.
General
Viewer
Events
Permissions
Displays general information about the action, including its name, its version number, the operations the user is allowed to perform, and a description.
Displays the action’s return type, input parameters, and the JavaScript code that defines the action's function.
Displays all of the events associated with this action.
Displays which users and user groups have permission to access the action.
Displays general information about the resource element, including its name, MIME type, description, version number, and the user permissions.
Displays the contents of the resource element.
Displays all of the events that are associated with this resource element.
Displays which users and user groups have permission to access the resource element.

Inventory View

The Inventory view in the Orchestrator client interface displays the objects of the plugged-in applications that are enabled in Orchestrator. You can use the Inventory view to run workflows on an inventory object.
If the Use contextual menu in inventory option is enabled, all of the workflows that you can run on the selected inventory object appear in a contextual menu.

Web Views View

The Web Views view in the Orchestrator client allows you to create, publish, and export Web views to a working folder or as templates. You can use Web views to access Orchestrator functions from a Web browser.
The Web Views view consists of a set of tabs that show information about a particular Web view.
General
Elements
Attributes
Events
Displays general information about the Web view, including its name, description, version number, the URL on which the Web view is published, and the user permissions.
Displays the HTML files and Web view components associated with the selected Web view.
Displays the attributes that direct the Web view to the objects in the Orchestrator server on which it performs tasks.
Displays all of the events that are associated with the Web view.
VMware, Inc. 21

Weboperator Web View

Orchestrator provides a standard Web view called weboperator that allows users to run workflows from a browser.
The weboperator Web view provides an example of the orchestration functions that Web views can provide to end users in browsers, without requiring that those users use the Orchestrator client.

Start the Weboperator Web View

You start the weboperator Web view from the Orchestrator client.
Procedure
1 Click the Web Views view in the Orchestrator client.
The weboperator Web view and any other Web views that you have imported into Orchestrator appear.
2 Right-click weboperator and select Publish.
3 Open a browser and go to http://
orchestrator_server
:8280.
In the URL, orchestrator_server is the DNS name or IP address of the Orchestrator server, and 8280 is the default port number where Orchestrator publishes Web views.
4 On the Orchestrator home page, click Web View List.
5 Click weboperator.
6 Log in using your Orchestrator user name and password.
7 Expand the hierarchical list of workflows to navigate through the workflows in the Orchestrator library.
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
Run the workflow at a later time
a Click Execute Workflow to run the workflow.
b Provide the required input parameters and click Submit to run the
workflow.
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.
22 VMware, Inc.

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. 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.
Orchestrator defines the following types of policy:
Chapter 2 The Orchestrator Client
Policy Templates
Policies
You can organize policy templates into categories, for easier navigation.
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 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 also create policies without using a template. You can see existing policies and create policies in the Policies view in the Orchestrator client.
VMware, Inc. 23
24 VMware, Inc.
Loading...
+ 56 hidden pages