After vCloud Director software is installed on the server, the installer prompts you to run a script that configures the server's network and database connections.

You must install vCloud Director software on the server before you can run the configuration script. The installer prompts you to run the script after installation is complete, but you can run it later. To run the script as a separate operation after the vCloud Director software is installed, log in as root, open a console, shell, or terminal window, and type:


The configuration script creates network and database connections for a single vCloud Director server. The script also creates a response file that preserves database connection information for use in subsequent server installations.

Verify that a database of a supported type is accessible from the vCloud Director server. See Installing and Configuring a vCloud Director Database and vCloud Director Hardware and Software Requirements.

Have the following information available:

Location and password of the keystore file that includes the SSL certificates for this server. See Create and Import a Signed SSL Certificate. The configuration script does not run with a privileged identity, so the keystore file and the directory in which it is stored must be readable by any user.

Password for each SSL certificate.

Hostname or IP address of the database server.

Database name and connection port.

Database user credentials (user name and password). This user must have specific database privileges. See Installing and Configuring a vCloud Director Database.


Specify the IP addresses to use for the HTTP and console proxy services running on this host.

Each member of a server group requires two IP addresses, so that it can support two different SSL connections: one for the HTTP service an another for the console proxy service. To begin the configuration process, choose which of the IP addresses discovered by the script should be used for each service.

Please indicate which IP address available on this machine should be used 
for the HTTP service and which IP address should be used for the remote console proxy.

The HTTP service IP address is used for accessing the user interface and the REST API.
The remote console proxy IP address is used for all remote console (VMRC) connections
and traffic.
Please enter your choice for the HTTP service IP address:
Choice [default=1]:2
Please enter your choice for the remote console proxy IP address
    Choice [default=1]:

Specify the full path to the Java keystore file.

Please enter the path to the Java keystore containing your SSL certificates and
private keys:/opt/keystore/certificates.ks

Type the keystore and certificate passwords.

Please enter the password for the keystore:
Please enter the private key password for the 'http' SSL certificate:
Please enter the private key password for the 'consoleproxy' SSL certificate:

Configure audit message handling options.

Services in each vCloud Director cell log audit messages to the vCloud Director database, where they are preserved for 90 days. To preserve audit messages longer, you can configure vCloud Director services to send audit messages to the syslog utility in addition to the vCloud Director database.



To log audit messages to both syslog and the vCloud Director database.

Type the syslog hostname or IP address.

To log audit messages only to the vCloud Director database

Press Enter.

If you would like to enable remote audit logging to a syslog
host please enter the hostname or IP address of the syslog server. Audit logs are stored by
vCloud Director for 90 days. Exporting logs via syslog will enable you to
preserve them for as long as necessary.
Syslog host name or IP address [press Enter to skip]:

Specify the port on which the syslog process monitors the specified server.

The default is port 514.

What UDP port is the remote syslog server listening on? The
standard syslog port is 514. [default=514]:
Using default value "514" for syslog port.

Specify the database type, or press Enter to accept the default value.

The following database types are supported:
       1. Oracle
       2. Microsoft SQL Server
Enter the database type [default=1]:
Using default value "1" for database type.

Specify database connection information.

The information that the script requires depends on your choice of database type. This example shows the prompts that follow specification of an Oracle database. Prompts for other database types are similar.


Type the hostname or IP address of the database server.

Enter the host (or IP address) for the database:

Type the database port, or press Enter to accept the default value.

Enter the database port [default=1521]:
Using default value "1521" for port.

Type the database service name.

Enter the database service name [default=oracle]

If you press Enter, the configuration script uses a default value, which might not be correct for some installations. For information about how to find the database service name for an Oracle database, see Configure an Oracle Database.


Type the database user name and password.

Enter the database username:vcloud
Enter the database password:

The script validates the information you supplied, then continues with three more steps.


It initializes the database and connects this server to it.


It offers to start vCloud Director services on this host.


It displays a URL at which you can connect to the Setup wizard after vCloud Director service starts.

This fragment shows a typical completion of the script.

Connecting to the database: jdbc:oracle:thin:vcloud/vcloud@
Database configuration complete.
Once the vCloud Director server has been started you will be able to 
access the first-time setup wizard at this URL:

Would you like to start the vCloud Director service now? If you choose not
to start it now, you can manually start it at any time using this command:
    service vmware-vcd start
Start it now? [y/n]:y
Starting the vCloud Director service (this may take a moment).

The service was started; it may be several minutes before it is ready for use.
Please check the logs for complete details.

vCloud Director configuration is now complete. Exiting...

Database connection information and other reusable responses you supplied during configuration are preserved in a file located at /opt/vmware/vcloud-director/etc/ on this server. This file contains sensitive information that you must reuse when you add more servers to a server group. Preserve the file in a secure location, and make it available only when needed.

To add more servers to this group, see Install vCloud Director Software on Additional Servers.

After vCloud Director services are running on all servers, you can open the Setup wizard at the URL displayed when the script completes. See vCloud Director Setup.