Server Installer Command Line Parameters
This page lists the parameters of the PerformanceGuard Server 8.1 or newer installer, PerformanceGuardServer.exe. Each parameter corresponds to a field in the installation wizard. The installer saves most of the values in Settings.ini, see Server Settings Ini.
General
Section titled “General”| Parameter | Description | Default |
|---|---|---|
APPDIR |
The folder where PerformanceGuard is installed. When you upgrade, the installer uses the folder of the existing installation. | C:\Program Files\Performanceguard |
Backend server and database
Section titled “Backend server and database”| Parameter | Description | Default |
|---|---|---|
CREATE_BE_DB |
1 = create a new backend database. 2 = use an existing PerformanceGuard backend database (for example when you upgrade). |
1 |
BE_DB_HOST |
Hostname or IP address of the SQL Server for the backend database. You can add an instance name and a port, for example localhost\instance:6789. |
localhost |
BE_DB_NAME |
Name of the backend database. | pguard |
BE_DB_USER |
User that PerformanceGuard uses to access the backend database. | pguard |
BE_DB_PASSWORD |
Password of BE_DB_USER. |
|
BE_DB_DOMAIN |
Windows domain of BE_DB_USER. Only for a Windows account. When you set it, the backend services run as this Windows account. |
|
BE_SA_USER |
SQL Server system administrator account that creates the backend database. | |
BE_DB_SA_PASSWORD |
Password of BE_SA_USER. |
|
BE_DB_SA_DOMAIN |
Windows domain of BE_SA_USER. Only for a Windows account. |
|
BE_DATADIR |
Folder for the backend database’s data files. The folder must exist. | SQL Server default |
BE_LOGDIR |
Folder for the backend database’s log files. The folder must exist. | SQL Server default |
BACKEND_PORT |
TCP port on which the backend server accepts connections from frontend servers. | 4008 |
MERLINPORT |
Primary display port of the PerformanceGuard web server. | 80 |
PGUARDPORT |
Secondary display port of the PerformanceGuard web server. | 81 |
PGUARDSECURE |
true = the web server uses HTTPS. false = HTTP. |
false |
SSL_KEY_STORE_PATH |
Path to the certificate file, when PGUARDSECURE=true. |
|
SSL_KEY_STORE_PASSWORD |
Password of the certificate file. |
Frontend server and database
Section titled “Frontend server and database”| Parameter | Description | Default |
|---|---|---|
CREATE_FE_DB |
1 = create a new frontend database. 2 = use an existing PerformanceGuard frontend database. |
1 |
FE_DB_HOST |
Hostname or IP address of the SQL Server for the frontend database. You can add an instance name and a port, for example localhost\instance:6789. |
localhost |
FE_DB_NAME |
Name of the frontend database. | pguardfe |
FE_DB_USER |
User that PerformanceGuard uses to access the frontend database. | pguardfe |
FE_DB_PASSWORD |
Password of FE_DB_USER. |
|
FE_DB_DOMAIN |
Windows domain of FE_DB_USER. Only for a Windows account. When you set it, the frontend service runs as this Windows account. |
|
FE_SA_USER |
SQL Server system administrator account that creates the frontend database. | |
FE_DB_SA_PASSWORD |
Password of FE_SA_USER. |
|
FE_DB_SA_DOMAIN |
Windows domain of FE_SA_USER. Only for a Windows account. |
|
FE_DATADIR |
Folder for the frontend database’s data files. The folder must exist. | SQL Server default |
FE_LOGDIR |
Folder for the frontend database’s log files. The folder must exist. | SQL Server default |
AGENT_PORT |
TCP port on which the frontend server listens for agents. | 4001 |
BACKEND_HOSTNAME |
Hostname of the backend server that the frontend server connects to. | |
FE_ENCRYPT_KEY |
Agent encryption key (optional), 32 hexadecimal characters. See Custom encryption. |
Examples of installation commands
Section titled “Examples of installation commands”The following are examples only. Your actual command depends on what you want to achieve.
Install PerformanceGuard with backend and frontend databases, and log the installation progress in the file install.log:
PerformanceGuardServer.exe /exenoui /exelog bootstrapper.log /i // /l*v install.log /qn ^BE_DB_HOST="localhost" BE_SA_USER="sa" BE_DB_SA_PASSWORD="sa" BE_DB_USER="pguard" BE_DB_PASSWORD="password" ^FE_DB_HOST="localhost" FE_SA_USER="sa" FE_DB_SA_PASSWORD="sa" FE_DB_USER="pguardfe" FE_DB_PASSWORD="password" ^CREATE_FE_DB="1" CREATE_BE_DB="1"Upgrade PerformanceGuard with existing backend and frontend databases, and log the installation progress in the file install.log:
PerformanceGuardServer.exe /exenoui /exelog bootstrapper.log /i // /l*v install.log /qn ^BE_DB_HOST="localhost" BE_SA_USER="sa" BE_DB_SA_PASSWORD="sa" BE_DB_USER="pguard" BE_DB_PASSWORD="password" ^FE_DB_HOST="localhost" FE_SA_USER="sa" FE_DB_SA_PASSWORD="sa" FE_DB_USER="pguardfe" FE_DB_PASSWORD="password" ^CREATE_FE_DB="2" CREATE_BE_DB="2"When you upgrade, the installer also reads the settings of the existing installation from its Settings.ini.