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.
vCenter Orchestrator Administration Guide 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.
Contents Updated Information 7 About This Book 9 1 Introduction to VMware vCenter Orchestrator 11 Key Features of the Orchestrator Platform 11 Orchestrator User Roles and Related Tasks 12 Orchestrator Architecture 13 2 The Orchestrator Client 15 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 Vie
vCenter Orchestrator Administration Guide Respond to a Request for a User Interaction 35 Scheduling Workflows 35 Schedule a Workflow 35 Edit the Workflow Recurrence Pattern 36 4 Creating Resource Elements 37 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 5 Using Pl
Contents Set JavaScript Access to Java Classes 67 Set Custom Timeout Property 68 Modify the Number of Objects a Plug-In Search Obtains 68 9 Maintenance and Recovery 71 Orchestrator Server Fails to Start 72 Revert to the Default Password for Orchestrator Configuration 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 Da
vCenter Orchestrator Administration Guide 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 jsio-conf file in “Set JavaScript Access to Operating System Commands,” on page 66.
vCenter Orchestrator Administration Guide 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.
vCenter Orchestrator Administration Guide 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. 10 Support Offerings To find out how VMware support offerings can help meet your business needs, go to http://www.vmware.com/support/services.
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.
vCenter Orchestrator Administration Guide Scripting engine Workflow engine 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.
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 This role has full access to all of the Orchestrator platform capabilities.
vCenter Orchestrator Administration Guide 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.
vCenter Orchestrator Administration Guide Procedure 1 2 Select Start > Programs > VMware > vCenter Orchestrator Client or run the vCenter Orchestrator Client.exe file that is located in install_directory\Orchestrator\apps. 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.
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.
vCenter Orchestrator Administration Guide 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.
Chapter 2 The Orchestrator Client 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. General Displays general information about the package, including its name, its legal owner, and a description.
vCenter Orchestrator Administration Guide 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.
Chapter 2 The Orchestrator Client The Actions view presents the following tabs. General Displays general information about the action, including its name, its version number, the operations the user is allowed to perform, and a description. Scripting Displays the action’s return type, input parameters, and the JavaScript code that defines the action's function. Events Displays all of the events associated with this action.
vCenter Orchestrator Administration Guide 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.
Chapter 2 The Orchestrator Client 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.
vCenter Orchestrator Administration Guide 24 VMware, Inc.
Managing Workflows 3 A workflow is a succession of actions and decisions that are run sequentially until they arrive at a specific result. Orchestrator provides a library of workflows that perform common management tasks according to best practices. Orchestrator also provides libraries of the individual actions that the workflows perform. Workflows combine actions, decisions, and results that, when performed in a particular order, complete a specific task or a specific process in a virtual environment.
vCenter Orchestrator Administration Guide The contents of the workflow library is accessible through the Workflows view in the Orchestrator client. The workflow library provides workflows in the following categories. JDBC Test the communication between a workflow and a database by using the JDBC (Java Database Connectivity) plug-in shipped with Orchestrator. Locking Demonstrates the locking mechanism for automated processes, that allows workflows to lock the resources they use.
Chapter 3 Managing Workflows Custom Attribute Workflows You access these workflows from Library > vCenter > Custom Attributes. Add custom attribute to a virtual machine Adds a custom attribute to a given virtual machine. Add custom attribute to multiple virtual machines Adds a custom attribute to a selection of virtual machines. Datastore and Files Workflows You access these workflows from Library > vCenter > Datastore and Files.
vCenter Orchestrator Administration Guide Linked Clone Workflows You access these workflows from Library > vCenter > Virtual Machine Management > Clone > Linked Clone. Linked clone, Linux with multiple NICs Creates a linked clone of a Linux virtual machine, performs the guest operating system customization, and configures up to four virtual network cards.
Chapter 3 Managing Workflows Other Workflows You access these workflows from Library > vCenter > Virtual Machine Management > Others. Find orphaned virtual machines Lists all virtual machines in an orphaned state in the Orchestrator inventory. Lists the VMDK and VMTX files for all datastores in the Orchestrator inventory that have no association with any virtual machines in the Orchestrator inventory. Sends the lists by email (optional).
vCenter Orchestrator Administration Guide 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 category that contains it.
Chapter 3 Managing Workflows Workflow Parameters Workflows receive input parameters and generate output parameters when they run. Input Parameters An input parameter is a runtime argument that you, an application, or another workflow or action passes to a workflow or action for it to process when it starts.
vCenter Orchestrator Administration Guide Workflow Tokens A workflow token represents a workflow that is running or has run. A workflow is an abstract description of a process that defines a generic sequence of steps and a generic set of required input parameters. When you run a workflow with a set of real input parameters, you receive an instance of this abstract workflow that behaves according to the specific input parameters you give it.
Chapter 3 Managing Workflows Locking Mechanism You can modify a workflow schema while it is running. This ability is useful in testing or debugging but not in production environment. Orchestrator features a mechanism that allows you to lock the workflow and prevent other users from editing it while it is running. To make actions, workflows, or whole packages read-only, use the contextual menus in the Actions, Workflows, and Packages views of the Orchestrator client.
vCenter Orchestrator Administration Guide 3 Right-click the Create simple virtual machine workflow and select Execute workflow. 4 Provide the following information into the Execute workflow input parameters dialog box to create a virtual machine in a vCenter Server connected to Orchestrator. Option Action Virtual machine name Name the virtual machine orchestrator-test. Virtual machine folder a b Click Not set for the Virtual machine folder value. Select a virtual machine folder from the inventory.
Chapter 3 Managing Workflows Respond to a Request for a User Interaction Workflows that require interactions from users during their run suspend their run either until the user provides the required information or until the workflow times out. Workflows that require user interactions define which users can provide the required information and direct the requests for interaction. Prerequisites Log in to the Orchestrator client. At least one workflow in Waiting for User Interaction state.
vCenter Orchestrator Administration Guide 9 (Optional) Click the Recurrence end date value’s Not Set button and set an end time and date for the workflow. 10 Provide the necessary information in the input parameters dialog box. 11 Click Submit to schedule the workflow. The scheduled workflow is listed on the Scheduler view. What to do next You can monitor the scheduled workflow and delete it from the Scheduler view when it is complete.
Creating Resource Elements 4 Workflows and Web views can require as attributes objects that you create independently of Orchestrator. To use external objects as attributes in workflows or Web views, you import them into the Orchestrator server as resource elements. Objects that workflows and Web views can use as resource elements include image files, scripts, XML templates, HTML files, and so on.
vCenter Orchestrator Administration Guide What to do next Import and edit a resource element. Import an External Object to Use as a Resource Element Workflows and Web views can require as attributes objects that you create independently of Orchestrator. To use external objects as attributes in workflows or Web views, you import them to the Orchestrator server as resource elements. Prerequisites An image file, script, XML template, HTML file, or other type of object to import.
Chapter 4 Creating Resource Elements What to do next Save the resource element to a file to update it, or add the resource element to a workflow or Web view. Save a Resource Element to a File You can save a resource element to a file on your local system. Saving the resource element as a file allows you to edit it. For example, if the resource element is an XML configuration file or a script, you must save it locally to modify it. You cannot edit a resource element in the Orchestrator client.
vCenter Orchestrator Administration Guide Add a Resource Element to a Workflow Resource elements are external objects that you can import to the Orchestrator server for workflows to use as attributes when they run. For example, a workflow can use an imported XML file that defines a map to convert one type of data to another, or a script that defines a function, when it runs.
Chapter 4 Creating Resource Elements Procedure 1 In the Orchestrator client, click the Web views view. 2 If the Web view is running, right-click the Web view to which to add the resource element and select Unpublish. 3 Right-click the Web view and select Edit. 4 Click the Attributes tab. 5 Right-click in the Attributes tab and select Add attribute. 6 Click the attribute name and type a new name for the attribute. 7 Click Type to set the attribute type.
vCenter Orchestrator Administration Guide 42 VMware, Inc.
Using Plug-Ins 5 Plug-ins allow you to use Orchestrator to access and control external technologies and applications. Exposing an external technology in an Orchestrator plug-in allows you to incorporate objects and functions in workflows that access the objects and functions of that external technology. The external technologies that you can access by using plug-ins can include virtualization management tools, email systems, databases, directory services, and remote control interfaces.
vCenter Orchestrator Administration Guide Default Orchestrator Plug-Ins Orchestrator includes a collection of plug-ins. Each plug-in exposes an external product API to the Orchestrator platform. Plug-ins provide inventory classes, extend the scripting engine with new object types, and publish notification events from the external system. Each plug-in also provides a library of workflows that represents the typical use cases of the integrated product in an automated fashion. Table 5-1.
Chapter 5 Using Plug-Ins Table 5-1. Plug-Ins Installed with Orchestrator by Default (Continued) Plug-In Purpose Configuration Input Types Scripting Objects Inventory Enumeration Allows the creation of common enumerated types. None Enumeration None Stores nothing in the inventory. Net Wrapper to Jakarta Apache Commons Net Library. Provides implementation of Telnet, FTP, and POP3. The POP3 part allows reading email.
vCenter Orchestrator Administration Guide Table 5-2. Add-ons and Separate Downloads Plug-In Remark Purpose Configuration Inventory Microsoft An experimental feature available as a separate download. Provides access to Windows Management Instrumentation (WMI) and reading and writing to Microsoft Active Directory. In Orchestrator configuration interface, import settings from the LDAP tab or use different LDAP settings for WMI.
Chapter 5 Using Plug-Ins Change the Key Pair Passphrase You can run a workflow from the Orchestrator client to change the passphrase for the key pair that you generated last. Prerequisites n The SSH plug-in must be enabled and configured in the Orchestrator configuration interface. n You must be logged in to the Orchestrator client as a user who can run SSH workflows. Procedure 1 Click the Workflows view in the Orchestrator client.
vCenter Orchestrator Administration Guide Run an SSH Command You can run a workflow from the Orchestrator client to run SSH commands on a remote ESX host. Prerequisites n The SSH plug-in must be enabled and configured in the Orchestrator configuration interface. n You must be logged in to the Orchestrator client as a user who can run SSH workflows. Procedure 1 Click the Workflows view in the Orchestrator client.
Chapter 5 Using Plug-Ins Copy a File to an SSH Host You can run a workflow from the Orchestrator client to copy files from the Orchestrator server to an SSH host. Prerequisites n The SSH plug-in must be enabled and configured in the Orchestrator configuration interface. n You must be logged in to the Orchestrator client as a user who can run SSH workflows. Procedure 1 Click the Workflows view in the Orchestrator client.
vCenter Orchestrator Administration Guide Create a Simple XML Document You can run a workflow from the Orchestrator client to create a simple XML document for testing purposes. Prerequisites n The XML plug-in must be enabled from the Orchestrator configuration interface. n You must be logged in to the Orchestrator client as a user who can run XML workflows. n Verify that you created the c:/orchestrator folder at the root of the Orchestrator server system or set access rights to another folder.
Chapter 5 Using Plug-Ins Modify an XML Document You can run a workflow from the Orchestrator client to modify the XML that the Create a simple XML document workflow creates. Prerequisites n The XML plug-in must be enabled from the Orchestrator configuration interface. n You must be logged in to the Orchestrator client as a user who can run XML workflows. n Verify that you created the c:/orchestrator folder at the root of the Orchestrator server system or set access rights to another folder.
vCenter Orchestrator Administration Guide 52 VMware, Inc.
Managing Actions 6 Actions represent individual functions that you use as building blocks in workflows, Web views, and scripts. Actions are JavaScript functions that take multiple input parameters and have a single return value. Actions can call on any object or method in the Orchestrator API, or on objects in any API that you import into Orchestrator by using a plug-in. When a workflow runs, an action takes its input parameters from the workflow's attributes.
vCenter Orchestrator Administration Guide 8 Add the action input parameters by clicking the arrow icon. 9 Write the action script. 10 Set the action permissions. 11 Click Save and close. You created a custom action and added the action input parameters. What to do next You can use the new custom action in a workflow. Duplicate an Action The predefined library of actions is read-only. To customize a standard action, you must create a duplicate of that action.
Chapter 6 Managing Actions What to do next You can import the action on a different Orchestrator server and use it in workflows and scripts. Import an Action You can import actions and use them as building blocks in workflows, Web views, and scripts. Procedure 1 In the Orchestrator client, click the Actions view. 2 Expand the root of the actions hierarchical list and navigate to the module in which you want to import the action. 3 Right-click the module and select Import action.
vCenter Orchestrator Administration Guide Procedure 1 In the Orchestrator client, click the Actions view. 2 Expand the nodes of the actions hierarchical list to navigate to a given action. 3 Right-click the action and select Find Elements that Use this Element. A dialog box shows all of the elements, such as workflows or packages, that implement this action. 4 Double-click an element in the list of results to show that element in the Orchestrator client.
Using Packages 7 Packages are the vehicle for transporting content from one Orchestrator server to another. Packages can contain workflows, actions, policies, Web views, configurations, and resources. When you add an element to a package, Orchestrator checks for dependencies and adds any dependent elements to the package. For example, if you add a workflow that uses actions or other workflows, Orchestrator adds those actions and workflows to the package.
vCenter Orchestrator Administration Guide 3 Name the new package and click OK. The syntax for package names is domain.your_company.folder.package_name. For example, com.vmware.myfolder.mypackage. 4 Right-click the package and select Edit. The package editor opens. 5 Add a description for the package in the General tab. 6 Click the Workflows tab to add workflows to the package. 7 n Click Insert Workflows (list search) to search for and select workflows in a selection dialog box.
Chapter 7 Using Packages 6 Check the appropriate check boxes to set the level of permissions for this user and click OK. To allow a user to view the elements, inspect the schema and scripting, run and edit the elements, and change the permissions, you must check all check boxes. 7 Click Save and Close to exit the package editor. You created a package and set the appropriate user permissions. Export a Package You can export a package and reuse its content on another Orchestrator server.
vCenter Orchestrator Administration Guide Import a Package To reuse workflows, actions, policies, Web views, and configuration elements from one Orchestrator server on another server, you can import them as a package. IMPORTANT Packages that Orchestrator 3.2 generates are upwardly compatible with Orchestrator 4.0. You can import a package from an Orchestrator 3.2 server to an Orchestrator 4.0 server. Packages from Orchestrator 4.0 are not backwards compatible with Orchestrator 3.2.
Chapter 7 Using Packages 3 Log in to the remote server. The Orchestrator Synchronization dialog box opens. It displays the differences between the package elements. To view only elements that are different on the local and remote server, select Hide identical from the drop-down menu. 4 View the comparison between the local and remote package elements, click Synchronize and select an option. Option Description none Local and remote elements have the same version number. No synchronization is required.
vCenter Orchestrator Administration Guide 62 VMware, Inc.
Setting System Properties 8 You can set system properties to change the default Orchestrator behavior.
vCenter Orchestrator Administration Guide 3 Add the following line to the vmo.properties configuration file. #Disable Orchestrator client connection com.vmware.o11n.smart-client-disabled = true 4 Save the vmo.properties file. 5 Restart the Orchestrator server. You disabled access to the Orchestrator client to all users other than members of the Orchestrator administrator LDAP group.
Chapter 8 Setting System Properties Each line of the js-io-rights.conf file must contain the following information. n A plus (+) or minus (-) sign to indicate whether rights are permitted or denied n The read (r), write (w), and execute (x) levels of rights n The path on which to apply the rights Orchestrator resolves access rights in the order they appear in the js-io-rights.conf file. Each line can override the previous lines.
vCenter Orchestrator Administration Guide 3 Open the js-io-rights.conf configuration file in a text editor. The following code extract shows the default content of the js-io-rights.conf configuration file: -rwx c:/ +rwx c:/orchestrator +rx ../../configuration/jetty/logs/ +rx ../server/vmo/log/ +rx ../bin/ +rx ./boot.properties +rx ../server/vmo/conf/ +rx ../server/vmo/conf/plugins/ +rx ../server/vmo/deploy/vmo-server/vmo-ds.xml +rx ../../apps/ +r ../../version.
Chapter 8 Setting System Properties You granted permissions to Orchestrator applications to run local commands in the Orchestrator server host operating system. NOTE By setting the com.vmware.js.allow-local-process system property to true, you allow the Command scripting class to write anywhere in the file system. This property overrides any file system access permissions that you set in the js-io-rights.conf file for the Command scripting class only.
vCenter Orchestrator Administration Guide Set Custom Timeout Property When vCenter is overloaded, it takes more time to return the response to the Orchestrator server than the 20000 milliseconds set by default. To prevent this situation, you must modify the Orchestrator configuration file to increase the default timeout period. If the default timeout period expires before the completion of certain operations, the Orchestrator server log contains errors.
Chapter 8 Setting System Properties Procedure 1 Navigate to the plug-in configuration folder on the Orchestrator server system. This folder contains an XML configuration file for each plug-in you have installed in the Orchestrator server. Option Action If you installed Orchestrator with the vCenter Server installer Go to If you installed the standalone version of Orchestrator Go to install_directory\VMware\Orchestrator\appserver\server\vmo\conf\plugins. install_directory\VMware\Infrastructure\Orches
vCenter Orchestrator Administration Guide 70 VMware, Inc.
Maintenance and Recovery 9 The Troubleshooting tab in the Orchestrator configuration interface allows you to perform several bulk operations related to workflows and tasks. You can use the Troubleshooting tab to globally reset the server and remove all traces of previous runs. NOTE Before you click a troubleshooting option, make sure that the Orchestrator server is stopped. Table 9-1.
vCenter Orchestrator Administration Guide Orchestrator Server Fails to Start The VMware vCenter Orchestrator Server service might fail to start when not enough RAM is available for the JVM to start the server. Problem The server status appears as Starting in the configuration interface and it is not updated when you refresh the page. When you select My Computer > Services and Applications > Services, the server fails to start and you receive a timeout error.
Chapter 9 Maintenance and Recovery 5 Save the password.properties file. 6 Restart the Orchestrator Configuration service. You can log in to the Orchestrator configuration interface with the default credentials. n User name: vmware n Password: vmware Change the Web View SSL Certificate Orchestrator provides an SSL certificate that controls user access to Web views. You can configure Orchestrator to use a different SSL certificate to control access to Web views.
vCenter Orchestrator Administration Guide Orchestrator Log Files VMware Technical Support routinely requests diagnostic information from you when a support request is handled. This diagnostic information contains product-specific logs and configuration files from the host on which the product is run. The information is gathered by using a specific script tool for each product. Table 9-2. Orchestrator Log Files Filename Location Description boot.log install_directory\appserver\server\vmo\log Provides d
Chapter 9 Maintenance and Recovery Table 9-2. Orchestrator Log Files (Continued) Filename Location Description yyyy-mm-dd.request.log install_directory\configuratio n\jetty\logs This log lists the elements that are needed to load and display the pages of the vCO configuration interface. It keeps a history of the actions that were taken during the configuration of vCO and the time when they were completed. Use this log to identify changes in the behavior of the vCO server after a restart.
vCenter Orchestrator Administration Guide Define the Server Log Level In the Orchestrator configuration interface, you can set the level of server log that you require. The default server log level is INFO. Changing the log level affects any new messages that the server writes to the server log and the number of active connections to the database. CAUTION Only set the log level to DEBUG or ALL to debug a problem.
Chapter 9 Maintenance and Recovery Change the Size of Server Logs If a server log regenerates multiple times a day, it becomes difficult to determine what causes problems. To prevent this, you can change the default size of the server log. The default size of the server log is 5MB. Procedure 1 2 Navigate to the following folder on the Orchestrator server system.
vCenter Orchestrator Administration Guide Procedure 1 Click the Workflows view in the Orchestrator client. 2 In the workflows hierarchical list, open Library > Troubleshooting and navigate to the Export logs and application settings workflow. 3 Right-click the Export logs and application settings workflow and select Start workflow. 4 (Optional) Type the path to the folder on the vCO server in which to store the output ZIP archive.
Index A L actions adding 53 creating 53 duplicating 54 encrypting 54 exporting 54 finding elements that implement 55 importing 55 moving 55 referencing 55 relocating 55 Actions view 20 API Explorer, accessing 16 attributes 29, 30 logs non-persistent logs 75 persistent logs 75 B batch operations workflows 26 C check-pointing 11 Command scripting class 66 configuration elements 30 Configurations view 18 contextual menu in inventory 21 D database maintenance 78 default password 72 disable access to Orch
vCenter Orchestrator Administration Guide policy engine 11 policy templates 23 R read-only resources 33 recurrent workflows 36 resource elements adding to Web views 40 adding to workflows 40 editing 38 importing 38 save to file 39 updating 39 viewing 37 resource locking 33 S Scheduler view 19 scheduling 35 schema 29, 31 scripting access to Java classes 67 accessing operating system commands 66 shutter system property 67 scripting engine 11 security 11 server log exporting 76 log level 76 SSH commands, ru
