Skip to main content Skip to complementary content

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:

  1. Select Start > All Programs > Accessories > Command Prompt.

    The Command Prompt window is displayed.

  2. In the Command Prompt window, navigate to the folder containing the Qlik_Sense_setup.exe file.

  3. Enter Qlik_Sense_setup.exe followed by the silent installation syntax preferred.

Information noteNote that elevation will take place if run from an unelevated process and the UAC is on.

Syntax

Qlik_Sense_setup.exe [-silent] {-log "path\filename"} {layout="path"} {rimnode=1|0} {rimnodetype="NodeTypeName"} {desktopshortcut=1|0} {skipstartservices=1|0} {installdir="path"} {userwithdomain="domain\user"} {userpassword="password} {dbpassword="password"} {hostname="www.hosturlofyourmachine.com"} {sharedpersistenceconfig="configfilepath"} {skipvalidation=1|0}
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.

Information noteThe user must have access to this directory.
-layout [destination directory]
Extracts files (including .msi files) to the destination directory.
Information noteThis 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.

rimnode 1|0 Determines the Repository role.
rimnodetype Complete|Proxy|Engine|ProxyEngine|Scheduler

Installs all the features required for the rim node type selected.

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 noteThis is a parameter must be configured to install successfully.

See: Shared persistence configuration file syntax

skipvalidation 1|0 To skip validation of the password provided for service user.
Information noteIf you enter a username that is more than 20 characters long, it must be in UPN format, and must include the full domain name. For example, longusername@full.domain.name.

Example 1:  

Qlik_Sense_setup.exe -s rimnode=1 rimnodetype=Scheduler

Example 2:  

Qlik_Sense_setup.exe -s userwithdomain=mydomain\myUser password=myPassword

Example 3:  

Qlik_Sense_setup.exe -s -l "c:\mylogpath" installdir="c:\mycustompath" dbpassword=mydbpassword rimnode=1

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

The configuration file is in XML format. You need to create the file according to the example described here.

<?xml version="1.0"?> <SharedPersistenceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DbUserName>username</DbUserName> <DbUserPassword>password</DbUserPassword> <DbHost>ip/hostname</DbHost> <DbPort>4432</DbPort> <RootDir>\\server\share</RootDir> <StaticContentRootDir>\\server\share\StaticContent</StaticContentRootDir> <CustomDataRootDir>\\server\share\CustomData</CustomDataRootDir> <ArchivedLogsDir>\\server\share\ArchivedLogs</ArchivedLogsDir> <AppsDir>\\server\share\Apps</AppsDir> <CreateCluster>true</CreateCluster> <InstallLocalDb>false</InstallLocalDb> <ConfigureDbListener>true</ConfigureDbListener> <ListenAddresses>*</ListenAddresses> <IpRange>0.0.0.0/0</IpRange> <MaxConnections>100</MaxConnections> <!--<JoinCluster>true</JoinCluster>--> <ConfigureLogging>true</ConfigureLogging> <SetupLocalLoggingDb>true</SetupLocalLoggingDb> <QLogsWriterPassword>writerpw</QLogsWriterPassword> <QLogsReaderPassword>readerpw</QLogsReaderPassword> <QLogsHostname>ip/hostname</QLogsHostname> <QLogsPort>4432</QLogsPort> </SharedPersistenceConfiguration>

Configuration file syntax

Setting Description
DbUserName User name of the repository database user.
DbUserPassword Password of the repository database user.
DbHost Hostname of the machine running the repository database.
DbPort Port used to communicate with the repository database.
RootDir 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 StaticContentRootDir, CustomDataRootDir and ArchivedLogsDir settings.
AppsDir Directory to store apps in.
StaticContentRootDir Root directory for all static content of the site.
CustomDataRootDir Root directory for all custom data of the site, for example, custom connectors.
ArchivedLogsDir Directory to save archived log files in.
CreateCluster

JoinCluster

Set CreateCluster to True if you want to create a new cluster, or set JoinCluster to True if you want to join an existing cluster. You can only use one of these settings in the configuration file. The other setting needs to be removed, or commented out like <!--<JoinCluster>true</JoinCluster>-->.
InstallLocalDb Set to True if you want to install a local PostgreSQL database on the node when you create a new cluster. This setting can only be used together with the CreateCluster setting.
ConfigureDbListener

Set to True if you want to configure the PostgreSQL database installed by Qlik Sense to listen to database connections from other nodes.

You need to configure the ListenAddresses and IpRange settings.

ListenAddresses

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).

IpRange 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 use a comma separated list.
MaxConnections 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.
ConfigureLogging Set ConfigureLogging to true if you want to set up centralized database logging.
SetupLocalLoggingDb Setting SetupLocalLoggingDb to true is equivalent to clicking New Logging Database in the installer UI. A new logging database will be installed with Qlik Sense.
QLogsWriterPassword Password of the qlogs_writer user account.
QLogsReaderPassword Password of the qlogs_reader user account.
QLogsHostname Host name of the logging database. Set QLogsHostname when SetupLocalLoggingDb is set to false.
QLogsPort Port number of the logging database. Set QLogsPort when SetupLocalLoggingDb is set to false.

Deprecated command line arguments

The use of the following command line arguments is no longer recommended.

-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.

-addfeatures (or -a)

Install the named features. Can be all or any of:

Engine, Proxy, Scheduler, PostgreSQL

Information noteThe silent feature names are case sensitive. For example this command will not start the installation: -s -a engine. The correct command is: -s -a Engine.
Information note-a Engine Scheduler will also install mandatory features, such as repository.
-removefeatures or -r Removes the named features
-desktopshortcut To add a desktop shortcut.
-skipstartservices To skip starting services after the installation has finished.
-installdir (or -i) Path to custom install directory. Need only be defined if the default install directory will not be used (%ProgramFiles%\Qlik\Sense).
-dbpassword (or -dbp)

Password for the Repository database superuser that creates the user that runs the database.

Warning noteUse carefully! The actual password will be visible in the log file. To mitigate this limitation please remove the installation log files after installation.
-hostname Host name of the central node.
-userwithdomain (or -u) Dictates the account that runs the services: Domain\User
-password (or -p)

Password for the account that runs the services.

Warning noteUse carefully! The actual password will be visible in the log file. To mitigate this limitation please remove the installation log files after installation.
-cleanup When the uninstall has completed, the Qlik Sense certificates and any file in the ProgramData\Qlik\Sense folder will be deleted

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!