4.2

Table Of Contents
Orchestrator Components Setup 3
To enhance the availability and scalability of your Orchestrator setup, install Orchestrator on a computer
different from the computer on which vCenter Server runs. With such separation, you can adjust the operating
system to meet the specific recommendations for each service.
This chapter includes the following topics:
n
“Orchestrator Configuration Maximums,” on page 19
n
“vCenter Server Setup,” on page 19
n
“Directory Services Setup,” on page 20
n
“Orchestrator Database Setup,” on page 20
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 150
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.
19