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 Database Setup
Orchestrator requires a database to store workflows and actions.
Orchestrator server supports Oracle and Microsoft SQL Server databases and provides experimental support
for MySQL and PostgreSQL. You can use MySQL and PostgreSQL for testing and evaluation purposes.
NOTE The driver for MySQL is not installed with Orchestrator. For details about enabling support for this
database type, see “Enable Support for MySQL Databases on Windows,” on page 18.
The way in which your database is set up can affect Orchestrator performance. Install the database on a virtual
machine other than the one on which Orchestrator is installed. This method avoids the JVM and DB server
having to share CPU, RAM, and IOs.
Storing your database plug-ins in a database separate from the one that Orchestrator uses allows more
modularity when upgrading the system. A dedicated database instance allows you to perform upgrades and
maintenance without impacting other products.
The location of the database is important because almost every activity on the Orchestrator server triggers
operations on the database. To avoid latency in the database connection, connect to the database server that is
closest to your Orchestrator server and that is on the network with the highest bandwidth.
The size of the Orchestrator database varies depending on the setup and how workflow tokens are handled.
Allow for approximately 50K per vCenter Server object and 4KB per workflow run.
CAUTION Make sure that at least 1GB of free disk space is available
n
on the virtual machine where the database is installed
n
on the virtual machine where the Orchestrator server is installed
Insufficient disk storage space might result in unwanted behavior of the Orchestrator server and client.
Enable Support for MySQL Databases on Windows
To use a MySQL database, you must download the driver and copy it to the appropriate locations. The
Orchestrator installer does not install drivers for MySQL databases.
Procedure
1 Download the latest MySQL driver from http://dev.mysql.com/downloads/connector/j/.
2 Extract the downloaded archive.
3 In the extracted folder, locate the mysql-connector-java-
x.x.x
.jar file, where x.x.x is the current
subminor version.
vCenter Orchestrator Installation and Configuration Guide
18 VMware, Inc.