Skip to main content
Announcements
[WEBINAR] Accenture & Qlik: Accelerating BI Migration to SaaS with Qlik on Dec 13th: REGISTER

Qlik Sense Enterprise on Windows: Improve app opening performance with ExcludeConnectionsOnOpenApp

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Qlik Sense Enterprise on Windows: Improve app opening performance with ExcludeConnectionsOnOpenApp

Last Update:

Nov 16, 2023 12:19:34 AM

Updated By:

Sonja_Bauernfeind

Qlik has introduced a new engine setting to improve initial app opening performance. This setting is relevant for environments with complex security rules and a high count of data connections.

ExcludeConnectionsOnOpenApp is available beginning with the following releases:

  • Qlik Sense Enterprise on Windows November 2023 IR
  • Qlik Sense Enterprise on Windows August 2023 Patch 6
  • Qlik Sense Enterprise on Windows May 2023 Patch 9

ExcludeConnectionsOnOpenApp is disabled by default. To enable it:

  1. Stop the Qlik Sense Engine and Qlik Sense Service Dispatcher services on all nodes with engines.
  2. On each engine node:
    1. Open a text editor as Administrator
    2. Open the Settings.ini file. Default location: C:\ProgramData\Qlik\Sense\Engine\Settings.ini
    3. Modify the file to add ExcludeConnectionsOnOpenApp=1:
      [Settings 7]
      ExcludeConnectionsOnOpenApp=1
      
      Do not remove the blank line at the end of the file. For additional information on how to modify the settings.ini file, see How to modify Qlik Sense Engine's Settings.ini.
    4. Save the file.
  3. After these changes have been made on all nodes, start the Qlik Sense Engine and Qlik Sense Service Dispatcher services on each node.

To revert ExcludeConnectionsOnOpenApp, modify the settings.ini file and remove the ExcludeConnectionsOnOpenApp=1 line.

 

Internal Investigation ID(s) 

IM-4424

Labels (1)
Comments
fosuzuki3
Contributor II
Contributor II

Hi @Sonja_Bauernfeind , this sounds interesting, but could you please clarify how this option changes the behavior of QS? For example, if it is disabled, will developers have issues when using the connections to develop their apps?

What we need to consider to decide if we need to enable/disable this option?

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @fosuzuki3 

I'm looking into this for you!

All the best,
Sonja 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @fosuzuki3 

There will be no difference in functionality. If you activate this feature, then you might experience opening the data load editor sometimes becoming slower because the security rules will need to be activated at that time instead. So instead of taking that hit during app open, you'll take the hit when you need the information. But there will be no functional difference.

Does this help?

All the best,
Sonja 

fosuzuki3
Contributor II
Contributor II

Hi @Sonja_Bauernfeind , yes thank you for the clarification!

Regards

Fernando

Contributors
Version history
Last update:
3 weeks ago
Updated by: