4.0
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 Orchestrator
- Upgrade Orchestrator with vCenter Server
- Upgrade Orchestrator Standalone
- Upgrading Orchestrator Applications After Upgrading vCenter Server
- 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 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
- Start a Published Web View
- 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
“vCenter Server Setup,” on page 17
n
“Directory Services Setup,” on page 17
n
“Orchestrator Database Setup,” on page 18
n
“Orchestrator Configuration Maximums,” on page 19
vCenter Server Setup
Increasing the number of vCenter Server instances causes Orchestrator to manage more sessions. Each active
session implies activity on the corresponding vCenter and too many active sessions can cause Orchestrator to
experience timeouts when more than 10 vCenter connections occur.
NOTE Run only one vCenter Server on a virtual machine. You can run multiple vCenter 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, a 100Mb line is mandatory.
Directory Services Setup
Orchestrator requires a connection to an LDAP server on your infrastructure.
The supported directory service types are: Active Directory, eDirectory, and Sun Java System Directory Server.
OpenLDAP is not supported and can only be used for testing and evaluation purposes.
Connect your system to the LDAP server that is physically closest to your Orchestrator server and avoid
connections to remote LDAP servers. Long response times for LDAP queries can lead to slower performance
of the whole system.
To improve the performance of the LDAP queries, keep the user and group lookup base as narrow as possible.
Try to limit the users to targeted groups that are going to need access, rather than to whole organizations with
many users who are not going to need access. Depending on the combination of database and directory service
you choose, the resources you need can vary. For recommendations, see third-party documentation.
VMware, Inc.
17