Previous Topic: Required Parameters in the response.varfileNext Topic: Upgrade Considerations (Silent installation)


Run or Edit the Silent Install Script File

After you create the response file, use one of the following options to start the silent installation:

Use the installation script file that is appropriate for your operating environment:

Note: For UNIX, if you invoke the installation script file using a dollar sign ($) in a parameter, prefix dollar sign ($) with backslash (\). For example, if the database password is 'abc$123', prefix backslash (\) as 'abc\$123'.

Windows
Syntax
Silent_Install_windows.bat [Parameter1] [Parameter2] [Parameter3]...
Usage:
Silent_Install_windows.bat -VcertPassword=a -VeiamCertPass=eiamadmin -VeiamPassword=eiamadmin -VdbPassword=sa -VreportingDbPassword=sa -VruntimeDbPassword=sa -VeiamAdminPass=eiamadmin
UNIX
Syntax
Silent_Install_unix.sh [Parameter1] [Parameter2] [Parameter3]...
Usage:
Silent_Install_unix.sh -VcertPassword=a -VeiamCertPass=eiamadmin -VeiamPassword=eiamadmin -VdbPassword=sa -VreportingDbPassword=sa -VruntimeDbPassword=sa -VeiamAdminPass=eiamadmin

The installation scripts include the following parameters:

-VcertPassword=value

Defines the password that controls access to the keys that encrypt passwords.

-VeiamCertPass

Defines the CA EEM certificate password (for example, pamadmin).

-VeiamPassword

Defines the password for the database that is used for automation objects (for example, pamadmin).

Note: VeiamPassword is the Windows domain password.

-VdbPassword

Defines the password for the database that is used for automation (for example, objectsroot).

-VreportingDbPassword

Defines the password for the reporting database (for example, root).

-VruntimeDbPassword

Defines the password for the database that is used at run time (for example, root).

-VeiamAdminPass

Defines the password for the CA EEM administrator, where the username value is EiamAdmin (for example, eiamadmin).

Important! Password parameters, whether passed through the command line or stored in the installation script file, are not encrypted.

When the installation completes, you can start the Orchestrator. Review the installation.log for any errors after the script executes (install_dir\server\c2o).