o On-demand App Service: generates on-demand apps that load subsets of data from

very large data

sets.
Paths
The following table lists the paths used by the Qlik Sense service dispatcher
(QSD) and the services that are
launched and managed by the QSD.
Executables l QSD: %ProgramFiles
%\Qlik\Sense\ServiceDispatcher\ServiceDispatcher.exe
l Services that are launched and managed by the QSD:
%ProgramFiles%\Qlik\Sense\ServiceDispatcher\node\node.exe
Logs l Broker Service: %ProgramData%\Qlik\Sense\Log\BrokerService
l Data Profiling Service: %ProgramData%\Qlik\Sense\Log\DataProfiling
l Hub Service: %ProgramData%\Qlik\Sense\Log\HubService
l Migration Service: %ProgramData%\Qlik\Sense\Log\AppMigration
l Web Extension Service: %ProgramData%\Qlik\Sense\Log\WebExtensionService
l On-demand App Service: %ProgramData%\Qlik\Sense\Log\OdagService
l Capability Service: %ProgramData%\Qlik\Sense\Log\CapabilityService
See: Logging (page 190)
Deployment examples of nodes running Qlik Sense services
You can deploy Qlik Sense services to run individually or combine them on dedicated
server nodes.
l Complete: A single-node deployment that includes all Qlik Sense services.
l Consumer node: A node that delivers Qlik Sense apps to end users. It includes
the Qlik Sense engine
service service, the Qlik Sense proxy service, and the Qlik Repository service.
Plan and deploy Qlik Sense - Qlik Sense, April 2018 31
2 Planning your deployment
l Proxy node: A node that manages Qlik Sense authentication, session handling, and
load balancing. It
includes the QRS, and the QPS services.
l Engine node: A node that provides the analytical power of Qlik Sense to the
client. It includes the
QRS, and the QES services.
l Proxy and engine node: A combined node that includes the QRS, QPS, and QES
service.
l Scheduler: A node that manages scheduled reloads of Qlik Sense apps and other
types of reload
triggering. It includes the QRS, QSS, and QES services. In order to perform reloads
the QSS requires
the QES to be running on the same node.
Service dependencies
This section describes the dependencies related to the Qlik Sense services (for
example, dependencies on
the operating system and other software).
Repository database
The Qlik Sense repository service (QRS) connects to the repository database to
store and retrieve data
necessary for the Qlik Sense services on the node on which the QRS is running. In a
default Qlik Sense
installation, the Qlik Sense repository service (QRS) uses the Qlik Sense
repository database (QRD) service
to read and write data in the repository database. A PostgreSQL database is used by
default.
File share
The file share stores the binary files for the Qlik Sense apps.
Directory service
The QRS and Qlik Sense proxy service (QPS) communicate with a configured directory
service (for example,
Microsoft Active Directory) using, for example, LDAP or ODBC.
Start and restart of services
When a node starts up, the Qlik Sense services are started automatically.
Start-up behavior
The Qlik Sense repository database (QRD) and Qlik Sense repository service (QRS)
are started fi