Editing an engine

You can edit engines that you have update rights to.

Do the following:

1. Open the QMC: https://<QPS server name>/qmc

2. Select Engines on the QMC start page or from the Start drop-down menu to display the overview.

3. Select the engine that you want to edit.

4. Click Edit in the action bar.

5. Edit the properties.

   Identification

   Identification properties

   Property	Description	Default value
   Node	The engine name.	Inherits the node name.

   Apps

   Apps properties

   Property	Description	Default value
   App autosave interval (seconds)	The number of seconds between autosaving of the apps. Autosave is always performed when a session ends.	30
   App cache time (seconds)	The number of seconds that a Qlik Sense app is allowed to remain in memory, after the last session that used the app has ended.	28800
   Table files root directory	A scheduled reload will search for files in this directory when relative paths are used to define file location. Information noteThis setting is used to support legacy features in QlikView scripts for relative paths to files during reload. You cannot use this setting to change the directory where the apps are stored.	%ProgramData%\Qlik\Sense\Apps
   Max number of undos	The maximum number of undos when editing app content, such as sheets, objects, bookmarks, and stories: min = 0, max = 999.	100

   Advanced

   Advanced properties

   Property	Description	Default value
   Listen ports	The listen port used by the Qlik Sense Engine Service (QES) for communication with the Qlik Sense web clients. Click to add more ports. Click to remove a port.	4747
   Allow data lineage	Save the data lineage (that is, the origin of the data) when executing a load script that loads data into Qlik Sense. This setting allows information about the LOAD statement that was used to load the table to be stored in the QVD file.	Selected
   Min memory usage (%)	The minimum memory capacity used by Qlik Sense. The cache is not cleared below this limit.	70
   Max memory usage (%)	The maximum memory capacity used by Qlik Sense.	90
   Memory usage mode	Influences how the Operating System (Windows) manages memory for the Engine process. Use the drop-down to select one of the following methods:  Hard max limit: never use more memory than defined by the Max memory usage (%) setting. This setting requires that the Operating System is configured to support this, as described in the SetProcessWorkingSetSizeEx documentation (QUOTA_LIMITS_HARDWS_MAX_ENABLE parameter). Ignore max limit: use as much memory as necessary, regardless of the Max memory usage (%) setting. Soft max limit: use more memory than defined by the Max memory usage (%) setting, if necessary and available.	Hard max limit
   CPU throttle (%)	The amount of CPU capacity used by Qlik Sense. Range: 0 – 100 %. You can increase or decrease the priority of the Qlik Sense Engine Service process, depending on how much CPU capacity the process is using. In this way, some of the CPU capacity can be released and used by other applications, improving the overall performance of the server. Information noteIf the CPU usage for the Qlik Sense Engine Service process exceeds the throttle level, it is most likely because the operating system has determined that more resources are available.	0 (that is, no throttling)
   Standard mode	When selected, standard mode is used. If cleared, legacy mode is used. Standard mode is the default mode that prevents actions that are potentially harmful. Standard mode is to be used unless there are special reasons not to. Legacy mode can be used for running QlikView load scripts unchanged, when loading data into Qlik Sense. For security reasons, Qlik Sense in standard mode does not support absolute or relative paths in the data load script or functions and variables that expose the file system. Warning noteDisabling standard mode can create a security risk by exposing the file system.	Selected
   HTTP callback port	The callback port used by the Qlik Sense Repository Service for sending HTTP events to engine.	4748
   Hypercube memory limit (bytes)	Limit for how much memory a hypercube evaluation can allocate during a request. If multiple hypercubes are calculated during the request, the limit is applied to each hypercube calculation separately . Note that the limit is not enforced on every allocation. If the setting has the value 0, the engine applies a global heuristic to limit the amount of simultaneously executing requests that allocate a lot of memory to calculations. A negative value disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases.	0
   Reload memory limit (bytes)	Limit for how much memory a reload request can allocate. A negative value or 0 disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases.	-1
   Export memory limit (bytes)	Limit for how much memory the export part of an export data request can allocate. Allocations made due to calculations are not counted against this limit. A negative value or 0 disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases.	-1
   Hypercube time limit (seconds)	Limits the single core CPU time equivalent that a hypercube calculation can use. The single core CPU time equivalent is a heuristic that approximates the CPU time spent, divided by the number of cores used during the calculation. This is not a hard limit and it is dependent on the complexity of processed calculation. A negative value or 0 disables the limit. For performance reasons, the CPU time is not tracked exactly.	60
   Reload time limit (seconds)	Limits the CPU time that a reload request can use. A negative value or 0 disables the limit.	-1
   Export time limit (seconds)	Limits the CPU time that the export part of an export data request can use. A negative value or 0 disables the limit.	-1
   Create search index during reload	When selected, all apps on the server are indexed during reload so that performance during the first search session is improved.	Selected

   Logging

   The Logging property group contains the engine logging and tracing properties in the Qlik Sense system.

   Logging properties

   Property	Description	Default value
   Audit activity log level	Use the drop-down to set the verbosity of the logger: Off: no entries Basic: a limited set of entries	Basic
   Service log level	Use the drop-down to set the verbosity of the logger: Off: no entries Error: only error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries	Info

   TRACING

   Tracing descriptions

   Setting	Description	Value
   Performance log interval (minutes)	The number of minutes in-between performance logging entries.	5
   System log level	All the standard engine messages are saved to this logger. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Info
   Performance log level	All the performance messages are saved to this logger ( by default updated default every five minutes). The log contains, for example, the number of active users, the number of open sessions, and the CPU load. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Info
   QIX performance log level	All the QIX protocol performance messages are saved to this logger. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Off
   Audit log level	More detailed, user based, messages are saved to this logger, for example, when the user makes a selection in an app. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Off
   Session log level	All the session messages are saved to this logger when a client session is terminated, for example, user information, machine ID, IP address and port number. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Info
   Traffic log level	All the traffic messages are saved to this logger, for example, all JSON-messages to and from the engine. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Off
   Analytic connections log level	All the analytic connections messages are saved to this logger. Use the drop-down to set the verbosity of the logger: Off: no entries Fatal: only fatal entries Error: same as fatal, but also including error entries Warning: same as error, but also including warning entries Info: same as warning, but also including information entries Debug: same as info, but also including debug entries	Info

   Information noteThe default path to the Qlik Sense log folder is %ProgramData%\Qlik\Sense\Log\<Service>.

   Logging

   Tags

   1. Click the text box to display the available tags.
   2. Start typing to filter the list.
      Information note Connected tags are listed under the text box.
   Custom properties

   Information noteIf no custom properties are available, this property group is not displayed at all (or displayed but empty) and you must make a custom property available for this resource type before it will be displayed here.
   Information noteIf you are running the Qlik Analytics Platform, additional settings are available, see Qlik Analytics Platform.
6. Click Apply to save your changes. If a mandatory field is empty, Apply is disabled.

Successfully updated engine properties is displayed at the bottom of the page.