QlikSenseTask.exe (QlikSenseTask.zip) is a tool for starting Qlik Sense tasks from the command line. Why QlikSenseTask? There will be many cases where QlikView data models and QVDs need to be loaded in QlikSense applications. This utility allows QlikView Publisher (and other schedulers) to call QlikSense tasks and load data into Qlik Sense apps.
Call QlikSenseTask.exe with the following parameters:
-proxy: - URL of Qlik Sense proxy -task: - name of reload task to execute. Put task names with spaces in quotes. -wait: - number of seconds the utility should wait for task to execute before timing out.
Example: qliksensetask -task:"Reload License Monitor" -proxy:https://localhost -wait:600"
Use config.txt to set any of these parameters at a global level. The command line values override the settings in config.txt. For example, use config.txt to set the -proxy and -wait values at a global level so that each time the executable is called, these values to not need to be set from the command line.
With QlikView Publisher
With QlikSenseTask,exe, QlikView Publisher can be used to call reload tasks in Qlik Sense. Below, QlikSenseTask.exe is set up as a supporting task in Publisher which reloads a task in Qlik Sense named "Reload Sales Dashboard" and waits 90 seconds before terminating.
This supporting task is triggered on the success of the reloaded data model in QlikView. Not pictured, the script in the Qlik Sense application binary loads the prepared QVW or QVD files.
Qlik Sense 1.0.X - QlikSenseTask.zip Qlik Sense 1.1 - QlikSenseTask-1.1.zip Qlik Sense 2.X - QlikSenseTask-2.X.zip Qlik Sense 3.X - QlikSenseTask-3.X.zip Note: 2.X is the same as 3.X, no changes. You can upgrade but it is totally the same. People were wondering if 2.X worked with 3.X, so this removes that doubt.
Security The current version of QlikSenseTask.exe only supports NTLM authentication. In the context of QlikView Publisher, this means that the service running Publisher will be the account to authenticate to Qlik Sense. (Note: It is possible but not yet implemented to use SSL certificates as an authentication mechanism. If there is a need, please let me know.)
The user that calls Qlik Sense needs to have access to the task. The simplest way to achieve this is to make the user a ContentAdmin in the Qlik Sense QMC.