Information about app and storage size for Qlik Cloud for Qlik Sense Enterprise SaaS and Qlik Sense Business can be found in Qlik Sense capacity.  

Note: An app on disk is typically 4-6 times bigger in memory, although this is a rule of thumb and exceptions can and do occur, and an app within the "on-disk" size limit may balloon past the "in memory" limit.  

App Objects have a memory limit of 10 GB, except when run on dedicated capacity.

If you are looking to compare other features between Qlik Sense Business and Qlik Sense Enterprise SaaS, see Compare product features 

For more information about capacity, see:

Qlik Sense specifications and capacity 
Pricing | Qlik Sense

tFTPDelete component does not work with wildcard “*“ as a global expression when using a SFTP connection and choosing File as Target Type.

tFTPDelete

1. When wildcard “*“ as a filemask, and the remote dir only contains files without subdirs, the job fails.
2. When wildcard “*“(or other filemask which can match any sub-dir name) as a filemask, and the remote dir also contains subdirs, the job still fails.

[FATAL] 16:58:50 tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP- tFTPDelete_1 Failure
com.jcraft.jsch.SftpException: Failure
    at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2827) ~[jsch-0.2.1.jar:0.2.1]
    at com.jcraft.jsch.ChannelSftp.rm(ChannelSftp.java:1971) ~[jsch-0.2.1.jar:0.2.1]
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.tFTPDelete_1Process(honda_tFTPDeleteWithSFTP.java:972) [classes/:?]
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.tFTPConnection_1Process(honda_tFTPDeleteWithSFTP.java:781) [classes/:?]
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.runJobInTOS(honda_tFTPDeleteWithSFTP.java:1776) [classes/:?]
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.main(honda_tFTPDeleteWithSFTP.java:1347) [classes/:?]
Exception in component tFTPDelete_1 (honda_tFTPDeleteWithSFTP)
4: Failure
    at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2827)
    at com.jcraft.jsch.ChannelSftp.rm(ChannelSftp.java:1971)
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.tFTPDelete_1Process(honda_tFTPDeleteWithSFTP.java:972)
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.tFTPConnection_1Process(honda_tFTPDeleteWithSFTP.java:781)
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.runJobInTOS(honda_tFTPDeleteWithSFTP.java:1776)
    at tono_cloud_ap.honda_tftpdeletewithsftp_0_1.honda_tFTPDeleteWithSFTP.main(honda_tFTPDeleteWithSFTP.java:1347)
[statistics] disconnected

No issue with “FTP“ mode.

Resolution

This issue is fixed in 8.0.1-R2025-01  

Cause

In SFTP mode, when wildcard “*“ as a filemask, it will use “ls“(-al) to filter the whole remote dir which is not working with our current code in tFTPDelete component (tFTPFileList/tFTPGet can filter that already).

And for second issue even subdir exists in the remote dir and wildcard (*) can match it, though the job still fails as “rm“ action cannot remove dir, even it is an empty subdir.

Related Content

tftpdelete-standard-properties

Internal Investigation ID(s)

• Internal Jira: QTDI-948
• Internal Jira: QTDI-912
  
  

Environment

Talend Data Integration 

From Talend Studio

1. Setting context variables to the repository and exporting the items.
   Please check Adding a built-in context variable to the Repository and Exporting items for further information.
2. By generating HTML documentation.
   Please check Generating HTML documentation for further information.

From Talend Administration Center

So far, there is no work around to export the context values from Talend Administration Center task, since you need to create context variables manually for the job,which you have used for the other jobs.

There is no feature to display all of the contexts you have created all together

Related Content

If you are looking for how to import context and change context parameters, please refer to these documentations as belows

importing-context-in-job

changing-context-parameters-in-jobs-and-routes

Environment

• Talend Studio 
• Talend Administration Center 

With Store Changes (see Change Processing) turned on for CDC tasks, Qlik Replicate tasks may crash or stop unexpectedly with the new feature use_manipulation_pk_for_apply enabled.

The following errors may be logged in the task log:

2024-07-30T09:53:22:497564 [AT_GLOBAL ]E: An exception occurred!!! (win32_exception_handler.c:109)

2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: Backtrace at exception: !{C:\Program Files\Attunity\Replicate\bin\at_base.dll!4537ab...

2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception code is 3221225477 (win32_exception_handler.c:112)

2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: tid=22112 (win32_exception_handler.c:115)

2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception as string is EXCEPTION_ACCESS_VIOLATION (win32_exception_handler.c:118)

Environment

• Qlik Replicate 2024.5.144 GA & 2024.5.247 PR1

Resolution

Fix Version

Upgrade to 2024.5 SP02 (for Windows and Linux) when available.

Workaround

To work around the issue:

1. Go to Task Settings...
2. Open the Full Load tab
3. In Full Load Settings set If target table already exists: DROP and CREATE table
   
   
   
   
4. Back in Task Settings... open the More Options tab
5. Add the following feature:
   
   use_manipulation_pk_for_apply
   value: Off
   
   
   

Cause

Product Defect ID: QB-28312 

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-28312 for reference.

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Starting Jan 30th (introduction of third-party runs, current packaging still applies)
• Starting April 2nd (switch to new packaging)
• FAQ

 

Timeline

The below timeline illustrates how the various stages of this packaging update will happen. In-between each stage should be sufficient time to analyze your usage and prepare for the enforcement.

• January 30th – Introduction of third-party runs
• April 2nd – New third-party packaging is available for purchase 
• May 1st – Enforcement
  • Third-party limits for seat-based licenses
  • Third-party overages for capacity licenses

Standard run vs third-party run

Standard runs

An automation run is considered a standard run if it only executes blocks from the following categories:

• All Qlik connectors (Qlik Cloud Services, Qlik Reporting, Qlik AutoML, Qlik …)
• Base blocks (excluding Call URL & Cloud Storage)
• Mail & Microsoft Outlook

Example:

 

Third-party runs

An automation run is considered a third-party run if it executes any blocks that are not in the standard connector categories.

As a rule of thumb, a standard run will execute one or more blocks from third-party connectors. Among others, third-party connectors are connectors like Slack, Amazon S3, Microsoft Excel, Call URL. A full overview of all automation connectors if available here.

Example:

Every run of this automation will execute the Send Message (Slack) block.
This will make every run a third-party run as the Slack connector is a third-party connector.
The “Contains third-party blocks” label indicates that the automation contains an active third-party block.

Possible third-party runs

For a run to be considered a third-party run, we only evaluate executed blocks. If the third-party blocks in the automation were not executed, the run will not count as a third-party run. A block not being executed could be caused by many factors like Condition blocks, Filter List blocks, deactivated third-party blocks, ...

This illustrates that an automation with a “Contains third-party blocks” label will not necessarily generate third-party runs on every run.

Example:

This automation will only execute the Send Message (Slack) block if the reload fails (from the Do Reload block). This means it will only generate third-party runs depending on the state of the Condition block.

Transition of existing entitlements

Starting Jan 30th (introduction of third-party runs, current packaging still applies)

1. Customers who are entitled to included runs will get these as third-party runs
2. Purchased runs will be converted to third-party runs
3. Renewals before the end of March will maintain the same included third-party runs until next renewal.

Starting April 2nd (switch to new packaging)

1. Every new purchase will be using the new packaging
2. Renewals will revert third-party runs to the edition included quantity of the new packaging + any purchase of third-party runs using the new packaging

FAQ

1. Will max concurrency be shared across run types?
Yes, both run types will count towards the same max concurrency.

2. Will usage of Qlik APIs through the Call URL block or other generic connectors count towards third-party runs?
Yes, when these blocks and connectors are used to make API requests to Qlik APIs, they will still count towards third-party runs. If you are missing blocks or functionality in a Qlik connector, please create an improvement request on our Ideation portal or support an existing request.

3. Will the new packaging have an included amount of third-party runs?
Yes, the new packaging will continue to provide some third-party runs for most editions of Qlik Cloud. More information on the editions and included amounts will be shared soon.

This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.

This article explains how to set up Cisco Duo as an Open ID Connect (OIDC) Identity Provider to authenticate to Qlik Cloud.

Set up Cisco Duo

1. in Cisco Duo, go to Application and create a new application.
   
   
2. Set Grant Type to Authorization Code 
   
   
   • Allow PKCE only authentication remains unchecked.
   • Access Token Lifetime can be set to 60 
     
     
3. Set Sign-in Redirect URLs to your Qlik Cloud tenant URL, appending /login/callback. Do not use the alias.
   
   Example: https://<TENANT URL>.<REGION>.qlikcloud.com/login/callback
   
   If you don't recall the original tenant URL, open https://<TENANT URL>.<REGION>.qlikcloud.com/api/v1/tenants in a browser tab to locate it.
   
   
4. In the Scopes section:
   
   
   1. Verify that openid is set as the scope
   2. Check profile and set the following claim:
      
      • IdP Attribute: <Display Name>
        
      • Claim: name
   3. Check email and set the following claim:
      
      • IdP: <Email Address>
        
      • Claim: email
        
        
5. Set a Name 
   
   
6. Uncheck Let users remove devices, add new devices, and reactive Duo Mobile
   
   
7. If required, limit who can authenticate through this application (Users in the organization that will be able to log in to Qlik Cloud).
   
   To do so, check Only allow authentication from users in certain groups and choose the required group.

Set up Qlik Cloud

1. Log in to the Qlik Cloud Management Console and navigate to Identity Provider
   
   
2. Create a new Identity Provider
   
   
   • Type: Interactive
   • Provider: Generic
     
     
3. Input the OpenID Connect Metadata URI as created in Cisco Duo
   
   The Metadata URI can be found under Discovery URL in the application created previously in Cisco Duo.
   
   
4. Input the Client ID as created in Cisco Duo
   
   
5. Input the Client Secret as created in Cisco Duo
   
   
6. Leave Realms (optional) blank
   
   
7. sub is set to sub
   
   
8. Click Create and Save
   
   
9. Click Validate
   
   After clicking Validate and logging in to Cisco Duo, confirm that claim mapping is correct and make the user a Tenant Admin so that you can still access the management console after activating Cisco Duo as an Identity Provider.
   
   Once Cisco Duo has been activated as your new IdP, the Invite User option will be disabled in your Management Console as users will now be managed by your new Identity Provider. See Identity providers.

Environment

Qlik Cloud 

Opening or working with a template in Qlik NPrinting Designer fails with the following error:

An error occurred while elaborating the entity tags.
Please check if the entities are properly placed inside their level tags.

Resolution

Refer to Qlik NPrinting Designer error: Tags (unknown member): Invalid request. Presentation cannot be modified for a workaround and Limitations for information on Qlik NPrinting Designer limitations.

Cause

This message could be the result of the organization using Sensitivity Labels or Azure Information Protection (AIP) labels.

Environment

• Qlik NPrinting

A specific line chart responds slower than expected and consumes excessive browser memory. 

Resolution

This is working as expected.

Set Presentation > Missing values to Show as gaps

Cause

The affected chart has the Presentation > Missing values set to Show as Zero.

This will fill missing values with zeros and render all line segments, leading to a slow response time. With Missing values set to Show as gaps, all line segments involving missing values will be skipped, improving performance. 

Internal Investigation ID(s)

QB-30492

Environment

• Qlik Sense Enterprise on Windows

Scenarios:

• Qlik Sense Enterprise on Windows has been migrated to a new domain. Bookmarks are no longer visible to users.
• The Qlik Sense server has been migrated to a new domain or assigned a new hostname. User records in the Qlik Management Console (QMC) refer to the previous user directory, which is no longer valid.

Accessing users will be identified according to new user directory, which can lead to duplicate user records. Depending on license allocation rules, there is also a risk that the same physical user will get a double user access allocation.

Please note that if direct assistance is required to implement these changes, Consulting Services will need to be engaged. See How and When to contact the Consulting Team. 

Resolution

This guide shows how to alter the user directory value by directly accessing the Qlik Sense Repository Database.  In this example the previous user directory OLDDOMAIN has been replaced with NEWDOMAIN.

Please note that if direct assistance is required to implement these changes, Consulting Services will need to be engaged. See How and When to contact the Consulting Team.

CAUTION: Direct change in the database are not supported and may cause irreversible corruption. Manual changes to the database must be executed with caution, and the system must be restored from backup at any symptom of system corruption.

1. Stop all Qlik Sense services, except the Qlik Sense Repository Database
2. Create a complete backup of Qlik Sense, to allow restoring the site in case of disaster
   Qlik Sense Help - Backup and restore
3. Connect to Qlik Sense Repository Database as described in article Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense 
4. Validate that connection is accurate by querying all users
   SELECT * FROM public."Users"
5. Change user directory name from old domain to new domain
   UPDATE public."Users"
   SET "UserDirectory" = 'NEWDOMAIN'
   WHERE "UserDirectory" = 'OLDDOMAIN';
6. Validate that intended change has been successfully applied to all affected users
   SELECT * FROM public."Users"
7. Start all Qlik Sense services
8. Confirm in QMC that users list shows the new domain as expected
   
   
9. Confirm in QMC that license allocation and allocation rules are accurate and match the directory change and allocation expectation
   
   
   
   
10. Login to Qlik Sense Hub with an authorized user from the “new domain”
11. Validate in QMC that the user access does not generate any duplicate entries, in the same view as in above steps 8 and 9.

Exporting charts from QlikView .qvw documents and downloading the files may lead to charts with corrupted visuals. This may specifically impact complex charts (utilizing shadows, scales, and other visual settings).

Example One:

This bar chart with active shadows has been downloaded to PDF. The file is corrupted and fails to open with the error Failed to load PDF document. 

Example Two:

Gauge charts scale exported bigger and the charts get smaller.

Resolution

Add the configuration SlowPrinting in the QlikView Settings.ini and export again.

Example for QlikView Desktop:

1. Close Qlikview Desktop
2. Navigate to C:\Users\<User>\AppData\Roaming\QlikTech\QlikView\
3. Open Settings.ini as an administrator
4. Add the following parameter under [Settings 7]
   SlowPrinting=1 (IMPORTANT: The line must be added at the top of the list i.e directly under [Settings 7])
5. Save the file.

Printing will be slower and potentially generate larger files.

For information about editing the settings.ini file, see How to change the settings.ini in QlikView Desktop and QlikView Internet Explorer Plugin.

Cause

By default, QlikView is set for high-speed PDF printing which may result in perceived lower-quality PDFs.

In turn, if it is not set for "high speed" PDF printing, and apparent lower quality is experienced, this may be a user perception issue and actually due to the "low speed" setting being enabled.

Environment

• QlikView

The file name format of charts downloaded from a QlikView app hosted on Qlik Cloud Analytics has changed with January 2025. Previously, file names were fixed, such as Chart_excel. The file now is a unique GUID for each download.

This is working as designed. The behavior is consistent with the client-managed version of the QlikView access point. 

Qlik Sense apps were not affected by this change.

Environment

• QlikView
• Qlik Cloud Analytics

The login failed for user exception occurs when promoting jobs from Talend Administration Center to Talend Management Console during execution period.

Job1 specifies the DB connection directly, and it runs well.

Job2 specifies the DB connection via using a context variable in DB connection parameter and it fails with a connection error. 

Both the two jobs use the same SQL Azure DB connection parameter, and it works fine when running Job2 in Talend Studio.

Talend Management Console logs show the error below:

FATAL:tDBInput_2 Login failed for user <db user>. ClientConnectionId:c3578634-babf-4494-a05c-4276900884d5

com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user <db user>. ClientConnectionId:c3578634-babf-4494-a05c-4276900884d5

LoginFailedforUser

Resolution

After changing the data type of the context value for the DB connection password from ‘Password’ to ‘String’ and re-deploy the job, the "login failed for user" issue was resolved.

Cause

The data type of the context value for the DB connection was set to ‘Password’ which causes this connection issue.

Environment

• Talend Studio 
• Talend Cloud 

After upgrading to the new Remote Engine, statistics are not visible when the Job is run from Talend Studio. However, it was functioning with the older Remote Engine. No changes have been made to the firewall, and the stats port range is permitted from the local machine to the Remote Engine server.

Resolution

1. Stop the Remote Engine.
2. Navigate to the <RE_installation_folder>/etc/org.talend.remote.jobserver.server.cfg file and change the value of the 'org.talend.remote.jobserver.server.TalendJobServer.ENABLED_PROCESS_MESSAGE' property to 'true'.
3. Start the Remote Engine.

After making the aforementioned changes, run the Job from Talend Studio on the Remote Engine to confirm the visibility of the statistics.

Environment

• Talend Studio 8.0.1

On Talend Management Console execution screen, the error below is shown.

Exceeded the limit of deployment attempts: the reason is unknown. If the behavior reoccurs in subsequent runs, contact our support for assistance.

Resolution

1. Upgrade to the the latest and supported Remote Engine version and apply the latest patch to your applications (For example: Runtime Server)
2. Check if reach the maximum number of allowable concurrent flows (running Jobs) and please try the following for troubleshooting.

'Exceeded the limit of deployment attempts: you have reached the limit of Flow deployments on the engine'

Cause 

1. The current Remote Engine you are using is Retired or End Of Life, check this documentation talend-remote-engine-lifecyle
2. Reach the maximum number of allowable concurrent flows (running Jobs) 

Environment

Talend Cloud 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Moving the data folder to a larger drive running out of disk space.

The default install directory is usually located on the C: drive and as the replicate environment grows larger and the task multiply users will often run out of disk space. To fix this you will need to delete files and free up space. You can also set up notifications on Disk Space.

Once that is done the next best thing to do is to move the data folder to a larger drive on the same server.

Resolution

Change the location in the Windows Registry

You can change the location without reinstalling. It requires the modification of the Windows Registry. This allows you to move the data folder and resume the tasks with no data loss and no need to reload the tasks.

For instructions, see Changing the Data Directory location on Windows | Qlik Replicate Help.

Reinstall

If you do not want to make changes to the registry, you can achieve the same by reinstalling Qlik Replicate. This allows you to move the data folder and resume the tasks with no data loss and no need to reload the tasks.

1. Uninstall Qlik Replicate
2. Move the data folder to new location with more storage space available 
3. Reinstall Qlik Replicate and point to the new data folder location.
4. Resume the tasks.

Related Content

How to Move the Data Directory to a Different Replicate Server
How to prevent Qlik Replicate services to go down when the disk space utilization is high

Environment

• Qlik Replicate 
• Data Directory 

Purpose

The purpose of this post is to help you install the database drivers necessary to allow your Qlik Data Gateway to communicate with your company's servers once you have completed the Qlik Data Gateway installation itself. 

Background

If you are anything like me, perhaps you panicked a bit at the thought of installing the Qlik Data Gateway in a Linux environment. I have a lot of experience with .EXE installations in Windows environments. You know "Next – Next – Next – Finish." But an .RPM file?  I had never even see that extension type before. If you were a Linux connoisseur beforehand, you probably guessed that my image for this post is an homage to the Fedora flavor of Linux. Otherwise you just thought it was an advertisement for the new "Raiders of the Lost Data" movie.

In any event, by now you have created your first Data Gateway, applied the registration key, completed the setup instructions and thankfully the command to check your Data Gateway service shows that it is running.

When you go back to the Data Gateway section of the Management Console and do a refresh your eyes fill you with happiness because your brand spanking new Data Movement Gateway shows "Connected.”

 A lesser person would go celebrate right now. But you've decided to try and connect to a source before doing your happy dance. So, you create a new Data Integration project to the destination of your choice. While you will ultimately have many different data sources, let's imagine that you decide to start with a "SQL Server (Log Based)" connection, as your first source test.

You input the server connection details, but your SQL Server doesn't use a standard port for security. Finally, you find information online that you should input your server IP followed by a "comma and the port #". As an example, if your servers IP is 39.30.3.1 and your security port is 12345 you would input "39.30.3.1,12345'. Next you input the user and password credentials. Your last step is to choose the database. Easy peezy, lemon squeezey. Right?

You press the "Load databases" button but suddenly a dialog comes up telling you that the Data Gateway can't connect because it can't find a SQL Server driver.

Driver Installation

Your heart starts beating quickly but naturally as a pro, you remain calm on the outside. Eventually you realize that whether on Windows or Linux, applications have always required drivers to communicate with servers. This is nothing new, we just got excited when we saw that connected message and thought we were done. Upon going back to the setup guide

[https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm]

you realize that there is in fact a link labeled "Setting up Data Gateway – Data Movement source connections."

So, you go ahead and click the link and it takes you to:

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-data-2.htm 

Wow, so many sources, and so many additional links to click to ensure the required drivers are in place for the sources your company will need. All the documentation is there, but I know firsthand that it can get a bit overwhelming, especially if Linux isn't your native language, which is the reason for this post.

Obviously every one of you reading this works in an environment that may require different data source connections than the others. Thus, there is no way for me to predict and help with your exact configuration. However, odds are strong that most of you likely require at least: SQL Server, Databricks, Snowflake, Postgres or MySQL, various combinations of them, or perhaps all of them.

As tedious, or imposing as it may be, I highly recommend you walk through the documentation for each data source you will need. But thanks to my buddy John Neal, I have attached a Linux shell script that can be executed to configure all 5 of those data sources for you. Given the many flairs and versions and configurations of Linux I can't ensure that it will work for everyone, but at least it is a start for those that may want to press an easy button, and those that like me may be somewhat or brand new to Linux.

If you choose to take advantage of it, understand that it is only being offered a shelp, and is not meant to replace the documentation. To utilize it you will need to do the following (Please note in my examples I have changed to the root user. If you are logged in as a normal user account, you may need to use SUDO "super user do"):

1. Copy the attached "repldrivers-el7.sh.txt" file your Linux home directory where you placed the gateway .RPM file.
2. Change the file name to simply be "repldrivers-el7.sh" so that it's clear that it is a shell script in case you or others see it in the future.
3. Issue the following command from your prompt: "chmod 775 repldrivers-el7.sh" so that the file has the appropriate security allowing it to be executed.
4. Issue the following command from your prompt: "./ repldrivers-el7.sh"  
5. Issue the following command from your prompt: "cd /etc"
6. Issue the following command from your prompt: "cat odbsinst.ini"    

If all went well with the installation your output should look like similar to the following image that was part of my file:

It's almost time to do our happy dance, but let's hold off until we test. In my starting example I asked you to assume we wanted to test against a "SQL Server (Log Based) connection." When we left off it was because we got an error message we had no driver while trying to load the list of databases. I will try that again.

 Oh no, the heart rate is going up again. 

We have successfully installed the Qlik Data Gateway. We have successfully installed the required drivers. Yet, we are getting this new error message. Let's focus on our breathing and try and digest the situation. What could cause our attempt to connect to our data source to timeout? I got it.

It's likely network security. We know what we want to talk to. We know the location. We know the credentials. But our networks aren't always wide open to do the talking. Resolving your connectivity/firewall issues may or not be with your abilities and if you are like me, you may need to seek the help of your IT/Networking team.

When I reached out to my friendly IT guru, here within Qlik, he was able to help me get everything in place so that my Linux server could speak with my database servers, including all of the needed ports.

Once they were completed I was able to test and sure enough my data connection succeeded.

Whether or not you do a happy dance, as I did, I hope that this post has helped you get to that sweet smell of success. After all, someone has to be known as the amazing person who got your Qlik Data Gateway going so that others in the Data Engineering team could create all of those lights out Qlik Cloud Data Integration projects that would be feeding data in near real time to all of those wonderul analytics use cases. Hopefully with the help of the documentation and this post, that person is you my friends. 

Challenge 

One of the things I've long admired about the Qlik Community is their willingness to help each other through this Community site. If you are a Linux guru and are so inclined I would love to see you share other versions of the shell script that I have started. Maybe your organization is using another flair/version of Linux and you needed to make a few tweaks to my file. Maybe your organization needed Oracle added and you can tweak my file. Whatever the reason, I sure hope you will give back to the community by sharing all of those tweaks here. Who knows, your help might help them be able to do their happy dance. And we all know the world is a better place when more people do their happy dance. 

Related Content 

Qlik Data Gateway - Data Movement prerequisites and Limitations - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-prerequisites.htm

Setting up the Data Movement gateway - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm

PS - I created both of the images here using a generative AI solution called MidJourney. I hope they've added to the fun of this post. 

Users can view all licenses by navigating between the Active and Expired tab.

1. Login to the legacy Support Portal by following this link or
   
   
   1. Login to Community (https://community.qlik.com) and click Support in the navigational ribbon
   2. Then click Licenses & Archived Cases 
   3. And choose View Licenses and Archived Cases to be redirected
      
      
      
      
2. On the Legacy Portal, click on View License Information or Archived Cases at the top of the page and select View My Licenses.
   
   
   
   
3. You will be redirected to the License List page or Legacy Cases list.
   
   Select Active (1) to view Active License.
   Select Expired (2) to view Expired Maintenance Licenses
   
   
   
   
   

1. If you would like to see a particular license, you can filter the list with the license key.
   
   

This can help in the troubleshooting process to find out what App/User was active and accessed an application right before an error/issue in the environment.
 
The entries are color coded for the name of the App in the Hub/QMC along with the APP ID and Session ID
 
Note: Session ID will change for different users and different browsers, this includes closing the browser and reopening it (which is a new session, but will be the same App ID). In this test there's only one session and two accesses of the app, but a user can open the app in another browser which will show it as the same user in two different sessions for the same app at the same time.
 

Environment: 

Qlik Sense Enterprise on Windows , version 3.2.1 and newer, single node

Windows 2012 R2

App Name: Load Test APP ID
Published APP ID?: c3ed4e49-dc98-4ff8-b140-f3d945236197 - Load Test APP ID
Session ID?: fe87b122-8979-45d4-9c37-3c39ce704045 - Load Test APP ID

C:\ProgramData\Qlik\Sense\Log\Engine\Trace\QLIKSERVER1_System_Engine.txt
 
First Open (loaded into memory):
 
16           20170321T215743.565+0100       INFO      QlikServer1         System.Engine.Engine   46           6f40f67b-47aa-406f-bb78-947e90cd9ff3         DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62282         0              Internal Engine                20170321T215743.566+0100       3136       3176       20170321T215516.000+0100       6f40f67b-47aa-406f-bb78-947e90cd9ff3
17           20170321T215743.573+0100       INFO      QlikServer1         System.Engine.Engine   46           31b65464-36b3-48c1-8dc8-f7b5c2ecbb9b              DOMAIN\qvservice         Server: Document Load: Beginning open of document                fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice             20170321T215743.573+0100                3132       3176       20170321T215516.000+0100       31b65464-36b3-48c1-8dc8-f7b5c2ecbb9b
18           20170321T215743.597+0100       INFO      QlikServer1         System.Engine.Engine   46           610de372-ad42-4975-863b-93f5d9fbcbec              DOMAIN\qvservice         DOC loading: Beginning load of document C3ED4E49-DC98-4FF8-B140-F3D945236197.           fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice                20170321T215743.597+0100       3756       3176       20170321T215516.000+0100       610de372-ad42-4975-863b-93f5d9fbcbec
19           20170321T215744.640+0100       INFO      QlikServer1         System.Engine.Engine   46           f15e84d0-f8d9-44d1-a8e1-3095b41e4a0d        DOMAIN\qvservice         Document Load: The document c3ed4e49-dc98-4ff8-b140-f3d945236197 was loaded.          fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice                20170321T215744.641+0100       4468       3176       20170321T215516.000+0100       f15e84d0-f8d9-44d1-a8e1-3095b41e4a0d
 
Second Open (already loaded in memory):
 
20           20170321T220052.937+0100       INFO      QlikServer1         System.Engine.Engine   47           34b26c68-67e8-4be1-9439-6026c0c59f9e          DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62296         0              Internal Engine                20170321T220052.937+0100       3136       3176       20170321T215516.000+0100       34b26c68-67e8-4be1-9439-6026c0c59f9e
21           20170321T220052.960+0100       INFO      QlikServer1         System.Engine.Engine   47           cc981161-bbfd-42ec-aa5c-b512e0602283         DOMAIN\qvservice         Server: Document Load: Beginning open of document     fe87b122-8979-45d4-9c37-3c39ce704045   DOMAIN              qvservice             20170321T220052.960+0100       3132       3176                20170321T215516.000+0100       cc981161-bbfd-42ec-aa5c-b512e0602283
 
Notice the first load will state what Session ID initiated the load into memory. The second attempt only gives the App ID in the first log line and then the Session ID is in an entry afterwards. While these entries should be right after each other, depending on what’s happening, they might be broken up by other entries. It’s unlikely, but does make it more difficult to troubleshoot a heavily trafficked environment without access to the Proxy logs.
 
Note: The First Open is only triggered when the QVF is not in memory, so the initial load in memory might be in another log file depending on when the log files are archived.
 
C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditSecurity_Proxy.txt
 
First Open (loaded into memory):
 
3              11.11.0.0              20170321T215732.019+0100       QlikServer1         738f0e4c-85bc-44ab-accb-18825ec407a5                Command=Login;Result=0;ResultText=Success   fe87b122-8979-45d4-9c37-3c39ce704045              c8d0eb48-fe7a-47da-bbca-0eab11340b92  0              DOMAIN              qvservice             0              Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess          /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Login                0              User authenticated. User 'DOMAIN\qvservice' used authentication method 'ticket' and got session 'fe87b122-8979-45d4-9c37-3c39ce704045'            1dc02c31e1779346144cbcc4b75a81a55f466159
4              11.11.0.0              20170321T215742.970+0100       QlikServer1         97ab24cb-edb8-4930-a343-69e044ec7dd0                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              94d89f25a8faad2ea59837ded7b6a1603a4607da

Second Open (already loaded in memory):
 
20           20170321T220052.937+0100       INFO      QlikServer1         System.Engine.Engine   47           34b26c68-67e8-4be1-9439-6026c0c59f9e          DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62296         0              Internal Engine                20170321T220052.937+0100       3136       3176       20170321T215516.000+0100       34b26c68-67e8-4be1-9439-6026c0c59f9e
21           20170321T220052.960+0100       INFO      QlikServer1         System.Engine.Engine   47           cc981161-bbfd-42ec-aa5c-b512e0602283         DOMAIN\qvservice         Server: Document Load: Beginning open of document     fe87b122-8979-45d4-9c37-3c39ce704045   DOMAIN              qvservice             20170321T220052.960+0100       3132       3176                20170321T215516.000+0100       cc981161-bbfd-42ec-aa5c-b512e0602283
 
As you can see the first load will state what Session ID initiated the load into memory. The second attempt only gives the App ID in the first log line and then the Session ID is in an entry afterwards. While these entries should be right after each other, depending on what’s happening, they might be broken up by other entries. It’s unlikely, but does make it more difficult to troubleshoot a heavily trafficked environment without access to the Proxy logs.
 
Note: The First Open is only triggered when the QVF is not in memory, so the initial load in memory might be in another log file depending on when the log files are archived.

C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditSecurity_Proxy.txt
 
First Open (loaded into memory):
 
3              11.11.0.0              20170321T215732.019+0100       QlikServer1         738f0e4c-85bc-44ab-accb-18825ec407a5                Command=Login;Result=0;ResultText=Success   fe87b122-8979-45d4-9c37-3c39ce704045              c8d0eb48-fe7a-47da-bbca-0eab11340b92  0              DOMAIN              qvservice             0              Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess          /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Login                0              User authenticated. User 'DOMAIN\qvservice' used authentication method 'ticket' and got session 'fe87b122-8979-45d4-9c37-3c39ce704045'            1dc02c31e1779346144cbcc4b75a81a55f466159
4              11.11.0.0              20170321T215742.970+0100       QlikServer1         97ab24cb-edb8-4930-a343-69e044ec7dd0                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              94d89f25a8faad2ea59837ded7b6a1603a4607da
 
Second Open (already loaded in memory):
 
5              11.11.0.0              20170321T220052.910+0100       QlikServer1         881a8f23-f3a2-4f2b-ae45-969dc9c0c2e3                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              0649a45ad43ccfcf97b82a1cd8d14dd2fa0cfe3b
6              11.11.0.0              20170321T220553.102+0100       QlikServer1         a5462a59-cf10-494e-b021-fc1c26bad82c                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              11c238cbc3edf8e921ebf0e0d8f71b199497a880
 
There’s a few logs listed here that will give other information along with the Session and App ID, but with the Proxy logs we can verify the Session ID that links to the App ID. This can point you to a time, user and app accessed giving you an idea of what users/apps were active and open at the time.

C:\ProgramData\Qlik\Sense\Log\Engine\Audit\QLIKSERVER1_AuditActivity_Engine.txt

First Open (loaded into memory):
 
1              12.16.1.0              20170321T215745.019+0100       QlikServer1         48345a91-0cef-4f54-adce-e1137ab27acd                20170321T215745.007+0100       12.2.2.0                Command=Open app;Result=0;ResultText=Success                fe87b122-8979-45d4-9c37-3c39ce704045              0e6278ad-ffff-4d6c-9d66-af84a1596d78                 1                DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197               Not available      Engine  Not available              Global::OpenApp             Open app            0              Success 48345a91-0cef-4f54-adce-e1137ab27acd
 
Second Open (already loaded in memory):
 
2              12.16.1.0              20170321T220053.193+0100       QlikServer1         ea7e3197-3651-4a87-9c56-a4d51872f01f                20170321T220053.193+0100       12.2.2.0                Command=Open app;Result=0;ResultText=Success                fe87b122-8979-45d4-9c37-3c39ce704045              a057e326-6123-406a-8ee2-e82a46efe367             1                DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197               Not available      Engine  Not available              Global::OpenApp             Open app            0              Success ea7e3197-3651-4a87-9c56-a4d51872f01f
 
This log gives the information on the app being opened with its Session ID.
 
C:\ProgramData\Qlik\Sense\Log\Engine\Trace\QLIKSERVER1_Session_Engine.txt
 
First Open (Closed browser tab):
 
1              20170321T220016.240+0100       INFO      QlikServer1         Session.Engine.Engine   53           6f637615-237c-4716-87d1-4a3f06ed81be        DOMAIN\qvservice                         fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN                qvservice             20170321T220016.238+0100       3132       3176       12.2.50504.0409.10                20170321T215516.000+0100       0e6278ad-ffff-4d6c-9d66-af84a1596d78                 c3ed4e49-dc98-4ff8-b140-f3d945236197    Load Test APP ID              20170320T195542.497Z                 Socket closed by client                20170321T215743.000+0100       0.001771              0.006285              1902       5619       13           0                UserDirectory=DOMAIN; UserId=qvservice           Off         6f637615-237c-4716-87d1-4a3f06ed81be
 
This has one entry for when tab in the browser was closed (but maintained the actual Session ID since the browser was still active) and you can see by the time stamp of 20170321T220016 is before the Second Open of 20170321T220053. If you had closed the Second Open session you would have a similar entry.
 
C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditActivity_Proxy.txt
 
First Open (No Session established until now):
 
1              11.11.0.0              20170321T215731.469+0100       QlikServer1         201ee217-3713-44cb-9277-d374799a84fb                Command=Get ticket;Result=0;ResultText=Success          0              0              0              INTERNAL            sa_proxy                0              Not available      Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Get ticket:ConsumeIncomingTicket  0              User claimed ticket: 'ewXLiJDk6xM1Q0TH'. Session will be etablished                201ee217-3713-44cb-9277-d374799a84fb
2              11.11.0.0              20170321T215731.512+0100       QlikServer1         7042d186-3f1d-4759-9d87-663b73522766                Command=Start session;Result=0;ResultText=Success    fe87b122-8979-45d4-9c37-3c39ce704045              0                0              DOMAIN              qvservice             0              DOMAIN\qvservice         Proxy    Not available                /qps/sessionstart/qvservice        Start session      0              Start session for user: 'DOMAIN\qvservice'                7042d186-3f1d-4759-9d87-663b73522766
3              11.11.0.0              20170321T215731.892+0100       QlikServer1         2e9f0d03-aabe-403a-b282-ec01a47283a0                Command=Add session;Result=0;ResultText=Success      fe87b122-8979-45d4-9c37-3c39ce704045                c8d0eb48-fe7a-47da-bbca-0eab11340b92             0              DOMAIN              qvservice             0              Not available                Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Add session:NotifyOfPostSession       0              Syncing user attributes for user 'DOMAIN\qvservice'        2e9f0d03-aabe-403a-b282-ec01a47283a0
4              11.11.0.0              20170321T215736.774+0100       QlikServer1         4f3ec3ce-604b-4fad-930c-6c5d3c417112                Command=Get session;Result=200;ResultText=Success  fe87b122-8979-45d4-9c37-3c39ce704045                bcce5b5b-a2e5-455c-9a36-f3fe076b03e3              0              DOMAIN              qvservice             0              Not available                Proxy    AppAccess          /qps/user?targeturi=http:%2f%2fqlikserver1.domain.local%2fhub%2f     Get session:HandleRequest 200         Handle connection request         4f3ec3ce-604b-4fad-930c-6c5d3c417112
5              11.11.0.0              20170321T215743.567+0100       QlikServer1         1fcb5c5c-15f5-40a6-bd54-0819643cd197                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           1fcb5c5c-15f5-40a6-bd54-0819643cd197
 
First Open (Closed tab)
 
6              11.11.0.0              20170321T220016.242+0100       QlikServer1         12a1b6ff-d000-4f56-a58c-8ca1bd36a567                Command=Close connection;Result=0;ResultText=Success            fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Close connection              0              Backend web socket connection Closed for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           12a1b6ff-d000-4f56-a58c-8ca1bd36a567
 
Second Open:
 
7              11.11.0.0              20170321T220052.937+0100       QlikServer1         f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb

 
Notice in this log the user gets a Ticket and Session in the first open to kick off the Session ID. You can then see that web socket connection is closed to the application for that session and then reopened right after it.
 
Note: The Syncing of attributes in the First Open that gets the ticket, it only does that the start of the session and will not be triggered until a new session is established.

C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditActivity_Proxy.txt
 
First Open (No Session established until now):
 
1              11.11.0.0              20170321T215731.469+0100       QlikServer1         201ee217-3713-44cb-9277-d374799a84fb                Command=Get ticket;Result=0;ResultText=Success          0              0              0              INTERNAL            sa_proxy                0              Not available      Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Get ticket:ConsumeIncomingTicket  0              User claimed ticket: 'ewXLiJDk6xM1Q0TH'. Session will be etablished                201ee217-3713-44cb-9277-d374799a84fb
2              11.11.0.0              20170321T215731.512+0100       QlikServer1         7042d186-3f1d-4759-9d87-663b73522766                Command=Start session;Result=0;ResultText=Success    fe87b122-8979-45d4-9c37-3c39ce704045              0                0              DOMAIN              qvservice             0              DOMAIN\qvservice         Proxy    Not available                /qps/sessionstart/qvservice        Start session      0              Start session for user: 'DOMAIN\qvservice'                7042d186-3f1d-4759-9d87-663b73522766
3              11.11.0.0              20170321T215731.892+0100       QlikServer1         2e9f0d03-aabe-403a-b282-ec01a47283a0                Command=Add session;Result=0;ResultText=Success      fe87b122-8979-45d4-9c37-3c39ce704045                c8d0eb48-fe7a-47da-bbca-0eab11340b92             0              DOMAIN              qvservice             0              Not available                Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Add session:NotifyOfPostSession       0              Syncing user attributes for user 'DOMAIN\qvservice'        2e9f0d03-aabe-403a-b282-ec01a47283a0
4              11.11.0.0              20170321T215736.774+0100       QlikServer1         4f3ec3ce-604b-4fad-930c-6c5d3c417112                Command=Get session;Result=200;ResultText=Success  fe87b122-8979-45d4-9c37-3c39ce704045                bcce5b5b-a2e5-455c-9a36-f3fe076b03e3              0              DOMAIN              qvservice             0              Not available                Proxy    AppAccess          /qps/user?targeturi=http:%2f%2fqlikserver1.domain.local%2fhub%2f     Get session:HandleRequest 200         Handle connection request         4f3ec3ce-604b-4fad-930c-6c5d3c417112
5              11.11.0.0              20170321T215743.567+0100       QlikServer1         1fcb5c5c-15f5-40a6-bd54-0819643cd197                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           1fcb5c5c-15f5-40a6-bd54-0819643cd197

First Open (Closed tab)
 
6              11.11.0.0              20170321T220016.242+0100       QlikServer1         12a1b6ff-d000-4f56-a58c-8ca1bd36a567                Command=Close connection;Result=0;ResultText=Success            fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Close connection              0              Backend web socket connection Closed for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           12a1b6ff-d000-4f56-a58c-8ca1bd36a567
 
Second Open:
 
7              11.11.0.0              20170321T220052.937+0100       QlikServer1         f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb
 
Notice in this log the user gets a Ticket and Session in the first open to kick off the Session ID. You can then see that web socket connection is closed to the application for that session and then reopened right after it.
 
Note: The Syncing of attributes in the First Open that gets the ticket, it only does that the start of the session and will not be triggered until a new session is established.

C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\QLIKSERVER1_Audit_Proxy.txt
 
First Open (loaded into memory):
  
1              20170321T215731.134+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           384a5be2-8c1f-4569-8b17-a6fa747b8f2f          DOMAIN\qvservice         Session 'a0ee67d2-581b-47db-9514-443ac4a008b1' is invalid (possibly timed out or logged out)            0              45b4435a-3e05-47c4-b78b-0e5311154a91                                                             ::ffff:172.16.16.100                                          {}             1650cb4421d90c3f0e3af23e1f5e2c8176219ad8
2              20170321T215731.188+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.RedirectionHandler       14           17bed8a0-b6ec-4316-9dfd-ff062b4b1c79     DOMAIN\qvservice         Authentication required, redirecting client@http://[::ffff:172.16.16.100]:62230/  to http://qlikserver1.domain.local:4248/windows_authentication/?targetId=6b07f3fb-5d9e-462f-b424-bb389054e645            0              45b4435a-3e05-47c4-b78b-0e5311154a91                                                             ::ffff:172.16.16.100                                          {}                8da259cac80248a0b1258dffa22a0bc5585c668b
3              20170321T215731.444+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.TicketValidator 14           ab854bb8-5c99-4a1c-8b76-00a443e94684    DOMAIN\qvservice         Issued ticket 'ewXLiJDk6xM1Q0TH' for user, valid for 1 minute(s)               0                                DOMAIN              qvservice             ewXLiJDk6xM1Q0TH                                                                       7f97ce8a8282eb9ed7aa0b61722b2504241e0e09
4              20170321T215731.470+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           f27f9ebc-4ad4-4d5a-968d-13e910e1efab        DOMAIN\qvservice         User claimed ticket: 'ewXLiJDk6xM1Q0TH'            0              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b DOMAIN              qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}             e025a74e13bb4c759fe5ad99787ad5589381b7bf
5              20170321T215731.891+0100       INFO      QlikServer1                Audit.Proxy.Proxy.DefaultModules.Session.SessionClientHandler               8              8dfacde2-3963-432b-af75-22d5122b5fea    DOMAIN\qvservice         Syncing user attributes for user DOMAIN\qvservice was successful                fe87b122-8979-45d4-9c37-3c39ce704045              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b            DOMAIN                qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}                df162a32bfed4ae4c37531b6f1ad4e7cb18b708e
6              20170321T215732.018+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           711c200a-60e9-457a-be6c-89f1ce11bf82          DOMAIN\qvservice         User 'qvservice' used 'ticket' authentication, got session: 'fe87b122-8979-45d4-9c37-3c39ce704045'                  fe87b122-8979-45d4-9c37-3c39ce704045              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b   DOMAIN              qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}                7fa218f968005afa6c0e635058e1e6c290e90d76
7              20170321T215735.128+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              11c49eb7-4ce8-45be-98d1-76a10f34562c          DOMAIN\qvservice         Retrieved 1 engine(s) from repository, result code Ok, app: __hub                fe87b122-8979-45d4-9c37-3c39ce704045              355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN                qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4242    {}                7b0262f7f34c583b38c13639692a495540079d74
8              20170321T215735.144+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              29022811-cbe3-4f9d-ba19-b3bb50f37e0e        DOMAIN\qvservice         Cached 1 prioritised Engine(s), app: __hub           fe87b122-8979-45d4-9c37-3c39ce704045          355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN              qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4242    {}                5ff601a6ada967d7d6c9990a1bddbe25e7bbc1cf
9              20170321T215735.186+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     24           dbf6cd5b-735e-4112-94c3-4db366bbe4b2       DOMAIN\qvservice         New target uri chosen: https://qlikserver1.domain.local:4900/ , app: __hub   fe87b122-8979-45d4-9c37-3c39ce704045              355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN                qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4900    {}                ba0e44b68b214c47fea575e93244c3c5f159c281
10           20170321T215743.535+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              7bcf1a03-6cfe-45ea-a06b-d1a780528be0        DOMAIN\qvservice         Retrieved 1 engine(s) from repository, result code Ok, app: c3ed4e49-dc98-4ff8-b140-f3d945236197    fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711      DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197                    {}             fe793ff3d692d1992e38f7be35c3a15d93ada65d
11           20170321T215743.535+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              425b5b86-579e-410f-8721-a816841bc16a         DOMAIN\qvservice         Cached 1 prioritised Engine(s), app: c3ed4e49-dc98-4ff8-b140-f3d945236197    fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711                DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197                                {}             ab51d2ad92cef8fff57fb15b1d5b115eeabedecb
12           20170321T215743.563+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     24           4c8e93c3-b3c9-475b-aa03-b8290f196014         DOMAIN\qvservice         New target uri chosen: wss://qlikserver1.domain.local:4747/, app: c3ed4e49-dc98-4ff8-b140-f3d945236197               fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711           DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197    qlikserver1.domain.local:4747    {}             f27c34ac0b7976a062ef3ea21d129acf451b0e65

This log only tracks the initial Session from the first Open, since the session is already established for the User. Further opening of the same app will not trigger a new entry for this Session/App ID
  
Final Note: There were no tests and review of entries for any new user sessions, different App IDs or for when the session times out or is forcible closed (closing the browser).  

As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).

This allows for analyzer capacity to be shared across all systems using the same license.

Environment

QlikView 
Qlik Sense Enterprise on Windows 
With a Signed License Key (SLK) applied as a unified license across multiple environments 

Here is an example:

A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.) 

This can be accessed through: System (A) > Licenses (B) > Choose the License (C) > Professional and Analyzer access (D)

Fig 1

If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up-to-date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.

This can be accessed in the Qlik Sense Management Console > License Management > License usage summary

Fig 2

The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.

Fig 3

For local consumption data, each server will store its own consumption and user information.   

For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.

For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:

RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe