Performing a silent installation
When running a silent installation, Qlik Sense is installed with no dialogs at all. This means all features, properties and user selections have to be known before performing a silent installation. All setup options that are available in the user interface of the installer can be performed with silent operations.
Do the following:
-
Select Start > All Programs > Accessories > Command Prompt.
The Command Prompt window is displayed.
-
In the Command Prompt window, navigate to the folder containing the Qlik_Sense_setup.exe file.
-
Enter Qlik_Sense_setup.exe followed by the silent installation syntax preferred.
Syntax
Qlik_Sense_setup.exe [-silent] {-log "path\filename"} {layout="path"} {desktopshortcut=1|0} {skipstartservices=1|0} {installdir="path"} {userwithdomain="domain\user"} {userpassword="password} {dbpassword="password"} {hostname="www.machinename.domain.com"} {sharedpersistenceconfig="configfilepath"} {senddata=1|0} {skipvalidation=1|0} {databasedumpfile="path"} |
Qlik_Sense_setup.exe -? or -h | Brings up the on-screen silent setup help. |
Commands
-silent (or -s) | Command line-driven setup without UI (mandatory). | |
-log (or -l) | [log file name with path] |
Log file directory and log file name. Note: The user must have access to this directory.
|
-layout | [destination directory] |
Extracts files (including .msi files) to the destination directory.
Note: This argument should not be combined with other command line arguments.
|
Arguments
Arguments are separated by space and presented in the form [Argument]="[Value]". The double quotes can normally be omitted but may be needed, for example, when a path contains spaces.
The default values are the same as those used in the setup user interface.
desktopshortcut | 1|0 (defaults to 1 on clean installs) | Installs desktop shortcuts. |
skipstartservices | 1|0 (defaults to 0 on clean installs, otherwise the current state.) | To skip starting services after the installation has finished. |
installdir | [path to custom install directory] | Need only be defined if the default install directory will not be used (%ProgramFiles%\Qlik\Sense). |
userwithdomain | [domain\username] | The username used to run the Qlik Sense services. |
userpassword | [password] | The password of the user used to run the services. |
dbpassword | [password] | Password for the database superuser that creates the user that runs the database. |
hostname | [address of the central node] | The central node uses certificates to communicate securely with other servers. Leave blank to use default. |
sharedpersistenceconfig (or spc) | [path to configuration file including the filename] |
Activates setup of shared persistence as storage method. All settings for shared persistence must be in the configuration file referenced here. Warning: This is a parameter must be configured to install successfully.
|
senddata | 1|0 | Share system data with Qlik in anonymous form. |
skipvalidation | 1|0 | For installation or upgrade, if the value is 1, skip validation of the password provided for service user and shared folder access. For silent installation, database connection tests are also skipped. |
databasedumpfile | [path to database dump file] | To retrieve your repository database backup dump file. |
Example 1: To install Qlik Sense
Qlik_Sense_setup.exe -s spc="\\configpath\spc.cfg" userwithdomain=mydomain\myUser userpassword=myPassword dbpassword=mydbpassword
Example 2: To install Qlik Sense while redirecting the installation and log files to a different location
Qlik_Sense_setup.exe -s -l "c:\mylogpath" spc="\\configpath\spc.cfg" installdir="c:\mycustompath" userwithdomain=mydomain\myUser userpassword=myPassword dbpassword=mydbpassword
Shared persistence configuration file syntax
Configure the shared persistence storage model, using the sharedpersistenceconfig argument, and point to a configuration file that contains the settings to be used in the installation.
Example:
Qlik_Sense_setup.exe -s spc="\\configpath\spc.cfg" userwithdomain=domain\yourserviceuser userpassword=yourserviceuserpassword dbpassword=yoursuperuserpassword
The configuration file is in
Configuration file syntax
Setting | Description |
---|---|
|
User name of the repository database user. |
|
Password of the repository database user. |
|
Hostname of the machine running the repository database. |
|
Port used to communicate with the repository database. |
|
Root directory for the file share to use as content storage. We recommend that you keep the content in this folder's sub-directories, but this can be changed in the |
|
Directory to store apps in. |
|
Root directory for all static content of the site. |
|
Directory to save archived log files in. |
|
Set |
|
Set to |
|
Set to You need to configure the |
|
Addresses that the database service should listen to. You can supply a comma separated list of IPv4 or IPv6 addresses, or 0.0.0.0 (for all IPv4 addresses), ::/0 (for all IPv6 addresses) or * (for all addresses). |
|
Subnet specification that covers the IP addresses of all nodes in your site. Either add one row for each node, using /32 as suffix for each address, or add a subnet that covers all addresses using, for example, /24 as suffix. To allow all servers to access the repository database, use 0.0.0.0/0. If entering multiple IP addresses or ranges, use a comma separated list. A range can be either IPv4 or IPv6. |
|
Specify the maximum number of concurrent connections to the database. The default value is 100. If you have a multi-node site multiple this value by the number of nodes in the cluster. For example, <MaxConnections>100</MaxConnections> is a single server deployment. |
|
Set |
|
Setting |
|
Password of the |
|
Password of the |
|
Host name of the logging database. Set |
|
Port number of the logging database. Set |
Deprecated command line arguments
The use of the following command line arguments is no longer recommended.
rimnode | Determines the Repository role. |
-rimnodetype (or -rnt) |
Installs all the features required for the rim node type selected. The node type can be any one of: Complete, Proxy, Engine, Scheduler. |