5.5.1
Table Of Contents
- Installing and Configuring VMware vCenter Orchestrator
- Contents
- Installing and Configuring VMware vCenter Orchestrator
- Updated Infromation
- Introduction to VMware vCenter Orchestrator
- Orchestrator System Requirements
- Hardware Requirements for Orchestrator
- Hardware Requirements for the Orchestrator Appliance
- Operating Systems Supported by Orchestrator
- Supported Directory Services
- Browsers Supported by Orchestrator
- Orchestrator Database Requirements
- Software Included in the Orchestrator Appliance
- Level of Internationalization Support
- Setting Up Orchestrator Components
- Installing and Upgrading Orchestrator
- Download the vCenter Server Installer
- Install Orchestrator Standalone
- Install the Orchestrator Client on a 32-Bit Machine
- Install the Client Integration Plug-In in the vSphere Web Client
- Download and Deploy the Orchestrator Appliance
- Upgrading Orchestrator 4.0.x Running on a 64-Bit Machine
- Upgrading Orchestrator 4.0.x and Migrating the Configuration Data
- Upgrade Orchestrator Standalone
- Updating Orchestrator Appliance 5.5.x
- Upgrading Orchestrator Appliance 5.1.x and Earlier to 5.5.x
- Upgrade an Orchestrator Cluster
- Uninstall Orchestrator
- Configuring the Orchestrator Server
- Start the Orchestrator Configuration Service
- Log In to the Orchestrator Configuration Interface
- Configure the Network Connection
- Orchestrator Network Ports
- Import the vCenter Server SSL Certificate
- Selecting the Authentication Type
- Configuring the Orchestrator Database Connection
- Server Certificate
- Configure the Orchestrator Plug-Ins
- Importing the vCenter Server License
- Selecting the Orchestrator Server Mode
- Start the Orchestrator Server
- Configuring vCenter Orchestrator in the Orchestrator Appliance
- Configuring Orchestrator by Using the Configuration Plug-In and the REST API
- Configure Network Settings by Using the REST API
- Configuring Authentication Settings by Using the REST API
- Configure the Database Connection by Using the REST API
- Create a Self-Signed Server Certificate by Using the REST API
- Managing SSL Certificates Through the REST API
- Importing Licenses by Using the REST API
- Additional Configuration Options
- Change the Password of the Orchestrator Configuration Interface
- Change the Default Configuration Ports on the Orchestrator Client Side
- Uninstall a Plug-In
- Activate the Service Watchdog Utility
- Export the Orchestrator Configuration
- Import the Orchestrator Configuration
- Configure the Maximum Number of Events and Runs
- Import Licenses for a Plug-In
- Orchestrator Log Files
- Configuration Use Cases and Troubleshooting
- Configuring a Cluster of Orchestrator Server Instances
- Registering Orchestrator with vCenter Single Sign-On in the vCenter Server Appliance
- Setting Up Orchestrator to Work with the vSphere Web Client
- Check Whether Orchestrator Is Successfully Registered as an Extension
- Unregister Orchestrator from vCenter Single Sign-On
- Enable Orchestrator for Remote Workflow Execution
- Changing SSL Certificates
- Back Up the Orchestrator Configuration and Elements
- Unwanted Server Restarts
- Orchestrator Server Fails to Start
- Revert to the Default Password for Orchestrator Configuration
- Setting System Properties
- Disable Access to the Orchestrator Client By Nonadministrators
- Disable Access to Workflows from Web Service Clients
- Setting Server File System Access for 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
- Where to Go From Here
- Index
Orchestrator Configuration Files
When you export the system configuration, a vmo_config_dateReference.vmoconfig file is created locally on
the machine on which the Orchestrator server is installed. It contains all the Orchestrator configuration data.
NOTE Some of the configuration files that are created during the export are empty. For example, the server
configuration data is not exported because the startup options for the Orchestrator server are unique for
each machine where the Orchestrator server is installed. These empty files must be reconfigured, even when
a working configuration was previously imported.
Table 9‑1. Settings Not Saved During Configuration Export
Setting Description
Licenses Manually imported licenses are not exported. They are
stored in the Orchestrator database.
Server The server configuration is reset to Unknown. You must
install the Orchestrator server as a Windows service again.
Table 9‑2. Settings Saved During Configuration Export
Setting Description
passwordencryptor.key The key used to encrypt the sensitive data. If the file is not valid, the sensitive
data hashes stored in the database become unusable.
General The maximum number of completed events and workflows recorded, and the
Web view development and configuration.
Network The IP binding address and the TCP ports used by the different elements of the
Orchestrator server.
Database The database configuration.
Certificate The certificates added as trusted authorities.
LDAP The LDAP server configuration.
Log The log settings information.
Plug-ins The list of disabled plug-ins and the account name.
Mail plug-in The SMTP host, SMTP port, user name, password, sender's name, and sender's
email address.
vCenter Server plug-in The vCenter Server plug-in configuration.
Each vCenter Server plug-in has an ID element , for example <guid>36907986-
d951-4f9a-9542-c561f4b94c3f</guid>, which is used as an identifier of the
vCenter Server instance.
In case you do not use the export for backup purposes, make sure that you
change the unique ID of the vCenter Server plug-in.
License The details about the vCenter Server host on which Orchestrator verifies the
license key.
jssecacerts The certificates added as trusted authorities.
dunes-pk The internal private key generated for each Orchestrator server instance. It is
used as an identifier. The vCenter Server plug-in uses this key to register to the
vCenter Server instances and uses it for logging in to the vCenter Server
instances. If the key changes, the vCenter Server plug-in cannot log in anymore.
Chapter 9 Additional Configuration Options
VMware, Inc. 87