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
Start the Orchestrator Server
You can install the Orchestrator server as a service on the Startup Options tab. When you do this, you can
start, stop, and restart the service from the Configuration interface. This process is reversible as you can always
use the Uninstall vCO server from service option.
Prerequisites
n
If you installed Orchestrator silently with vCenter Server, verify that your system has at least 4GB of RAM
and that the database is running on a dedicated server. The Orchestrator server might not start if your
system does not meet this requirement.
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
All of the status indicators must 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 Click Install vCO server as service.
The Orchestrator server is installed as a Windows service.
4 Click Start service.
The Orchestrator server status appears as Service is starting. The first boot can take around 5-10
minutes because it is building the database tables.
A message states that the service is started successfully. The Orchestrator server status appears at the bottom
of each configuration tab and is one of the following:
n
Running
n
Not available
n
Stopped
To see the Orchestrator server status, update the page by clicking the Refresh link.
What to do next
You can save and export the Orchestrator configuration file so that it can be imported later if needed. See
“Export the Orchestrator Configuration,” on page 56.
Activate the Service Watchdog Utility
Orchestrator provides a watchdog utility that checks for the activity of the Orchestrator server service. The
utility pings the Orchestrator server service periodically, and restarts it if a certain timeout period is exceeded.
By default, the timeout period is set to zero (0), which means that the watchdog utility is deactivated.
You can activate the service watchdog utility by setting the timeout period for the service's response to the
ping from the utility. You can set the timeout period for the response from the Orchestrator server service in
the wrapper.conf configuration file. The wrapper.conf file defines the wrapping of the Orchestrator server in
the host system.
Prerequisites
The Orchestrator server must be running as a Windows service.
Chapter 9 Configuring Orchestrator
VMware, Inc. 55