To work with Orchestrator, ensure that the Orchestrator server service has started.
When you install Orchestrator separately from vCenter Server, you must first install the Orchestrator server as a service. You can install the Orchestrator server as a service from the Startup Options tab of the Orchestrator configuration interface. When you do this, you can start, stop, and restart the service from the Orchestrator configuration interface.
Prerequisites
■
|
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.
|
■
|
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 | (Optional) 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 5-10 minutes because it is installing the Orchestrator plug-ins content in 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:
■
|
Running
|
■
|
Not available
|
■
|
Stopped
|
|
5 | (Optional) To see the Orchestrator server status, update the page by clicking the Refresh link. |
What to do next
Log in to the Orchestrator client, run, and schedule workflows on
the vCenter Server inventory objects or other objects that
Orchestrator accesses through its plug-ins. If you installed Orchestrator together with vCenter Server, log in as a user from the vCenter Server administrator group. Any user from the vCenter Server administrator group that you have provided during the vCenter Server installation, is an Orchestrator administrator.