5.5.2
Table Of Contents
- Installing and Configuring VMware vCenter Orchestrator
- Contents
- Installing and Configuring VMware vCenter Orchestrator
- 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 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
- 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 Expiration Period of Events and the Maximum Number of 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
4 (Optional) Provide values for the Cluster mode settings and click Apply changes.
Option Description
Number of active nodes
The maximum number of active Orchestrator server instances in the
cluster.
Active nodes are the Orchestrator server instances that run workflows and
respond to client requests. If an active Orchestrator node stops responding,
it is replaced by one of the inactive Orchestrator server instances.
The default number of active Orchestrator nodes in a cluster is one.
Heartbeat interval (milliseconds)
The time interval, in milliseconds, between two network heartbeats that an
Orchestrator node sends to show that it is running.
The default value is 5000 milliseconds.
Number of failover heartbeats
The number of heartbeats that can be missed before an Orchestrator node
is considered failed.
The default value is 12 heartbeats.
The default failover timeout is 1 minute and is equal to the value of the default heartbeat interval
multiplied by the number of the default failover heartbeats.
5 Log in to the Orchestrator configuration interface of the second Orchestrator server as vmware.
6 Repeat Step 3 and Step 4.
You have set up an Orchestrator cluster.
What to do next
You can add more Orchestrator cluster nodes.
IMPORTANT When you configure Orchestrator to work in cluster mode, you must first start one of the
Orchestrator servers and wait until it starts and initializes the database. A cluster node is considered
running when on the Server Availability tab, the node appears under Started cluster nodes with a Running
status. If you start more than one Orchestrator servers at the same time, concurrency issues occur as all of
the started Orchestrator servers try to initialize the database.
Start the Orchestrator Server
To work with Orchestrator, ensure that the Orchestrator server service has started.
Prerequisites
n
If you installed Orchestrator standalone, verify that your system has at least 2GB of RAM. The
Orchestrator server might not start if your system does not meet this requirement.
n
Verify that all the status indicators display a green circle. You cannot start the Orchestrator server if any
of the components is not configured properly.
Procedure
1 Log in to the Orchestrator configuration interface as vmware.
2 Click Startup Options.
3 If the Orchestrator server has stopped, click Start service.
The Orchestrator server status appears as Service is starting. The first boot can take 5-10 minutes
because the server is installing the Orchestrator plug-ins content in the database tables.
A message states that the service has started successfully.
Chapter 5 Configuring the Orchestrator Server
VMware, Inc. 65