4.1
Table Of Contents
- vCenter Orchestrator Installation and Configuration Guide
- Contents
- Updated Information
- About This Book
- Introduction to VMware vCenter Orchestrator
- Orchestrator System Requirements
- Orchestrator Components Setup Guidelines
- Installing and Upgrading Orchestrator
- Upgrading to Orchestrator 4.1 and Migrating the Orchestrator Data
- Uninstall Orchestrator
- Configuring Orchestrator
- Start the Orchestrator Configuration Service
- Log In to the Orchestrator Configuration Interface
- Change the Default Password
- Revert to the Default Password for Orchestrator Configuration
- Configure the Network Connection
- Change the Default Configuration Ports on the Orchestrator Client Side
- Import the vCenter Server SSL Certificate
- Configuring LDAP Settings
- Password Encryption and Hashing Mechanism
- Configure the Database Connection
- Server Certificate
- Configure the Default Plug-Ins
- Access Rights to Orchestrator Server
- Import the vCenter Server License
- Start the Orchestrator Server
- Export the Orchestrator Configuration
- Import the Orchestrator Configuration
- Configure the Maximum Number of Events and Runs
- Install an Application
- Import the Plug-In Licenses
- Change the Web View SSL Certificate
- Define the Server Log Level
- Where to Go From Here
- Index
Orchestrator Components Setup
Guidelines 3
To enhance the availability and scalability of your Orchestrator setup, install Orchestrator on a server different
from the server on which vCenter Server runs. Separating Orchestrator from vCenter Server makes it possible
to adjust the operating system to meet the specific recommendations for each service.
This chapter includes the following topics:
n
“Orchestrator Configuration Maximums,” on page 17
n
“vCenter Server Setup,” on page 17
n
“Directory Services Setup,” on page 18
n
“Orchestrator Database Setup,” on page 18
Orchestrator Configuration Maximums
When you configure Orchestrator, verify that you stay at or below the supported maximums.
Table 3-1. Orchestrator Configuration Maximums
Item Maximum
Connected vCenter Server systems 10
Connected ESX/ESXi servers 300
Connected virtual machines spread over vCenter Server systems 15000
Concurrent running workflows 300
vCenter Server Setup
Increasing the number of vCenter Server instances in your Orchestrator setup causes Orchestrator to manage
more sessions. Each active session results in activity on the corresponding vCenter Server, and too many active
sessions can cause Orchestrator to experience timeouts when more than 10 vCenter Server connections occur.
For a list of the supported versions of vCenter Server, see VMware Product Interoperability Matrix.
NOTE You can run multiple vCenter Server instances on different virtual machines in your Orchestrator setup
if your network has sufficient bandwidth and latency. If you are using LAN to improve the communication
between Orchestrator and vCenter Server, a 100Mb line is mandatory.
VMware, Inc.
17