Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor, License Monitor, and Content Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor, License Monitor, and Content Monitor

The Operations Monitor loads service logs to populate charts covering the performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor. 

• Basic information can be found in Operations Monitor | help.qlik.com
• Detailed descriptions of sheets and visualizations are accessible in the About the Operations Monitor story available from the app overview page under Stories

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

• Basic information can be found in License Monitor | help.qlik.com  
• Detailed descriptions of sheets and visualizations are accessible in the About the License Monitor story available from the app overview page under Stories

The Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of the platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.

• Basic information can be found in Content Monitor | help.qlik.com  
• Each sheet in the Content Monitor includes an About text box to describe its content. 
  

All three apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor | Content Monitor (download page). Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

Qlik Sense upgrade process was completed successfully. However, upon attempting to run Qlik Sense services, the CPU usage spiked to 99% to 100%, rendering the Qlik server unresponsive.

Restarting the Qlik Sense services or rebooting the Qlik Sense Windows machine does not resolve the issue.

The Windows Task Manager on the Qlik Sense Windows machine reveals the Qlik Dispatcher service causes the CPU spike.

This article provides a solution for one possible root cause leading to a high CPU load. Other root causes may exist (such as an unoptimized Qlik Sense document) and will require additional troubleshooting.

Resolution

To resolve this particular root cause:

1. Navigate to C:\Program Files\Qlik\Sense\ServiceDispatcher\ on the Qlik Sense Windows machine
2. Open the services.conf file
3. Verify f you can locate duplicate entries, such as:
   
   
   
   
4. If duplicates are found, delete them.

Note: In a multi-node environment, this verification must be performed on all nodes.

Cause

A duplicated command in the configuration file was leading to multiple instances of the service being triggered, creating an infinite loop. This misconfiguration resulted in an excessive number of threads and consumed all available CPU resources.

Environment

• Qlik Sense Enterprise on Windows 

The following two items were deprecated in June 2025:

• Developer role
• Enable API keys toggle

The deprecation notice was communicated in an Administration announcement and documented on our What's New in Qlik Cloud feed. See Developer role and API key toggle deprecated | 6/16/2025 for details.

What products are affected by the removal of the role and toggle?

• Qlik Cloud Analytics
• Qlik Talend Cloud

What actions do I need to take?

To replace the deprecated built-in role, migrate your users away from the Developer role to a Custom Role with the required permissions (Manage API Keys).

To create and assign a replacement custom role:

1. In the Administration activity center, go to Manage users
2. On the Permissions tab, select Create new
3. Name the role using your organization's naming convention
4. Set Manage API keys to Allowed
5. Assign the role to users or groups who previously had the deprecated role
6. Remove the deprecated role from those users or groups

For additional reading on the Managed API Keys (set to Not allowed by default), see Permissions in User Default and custom roles | Permission settings — Features and actions.

When will the deprecated items be removed?

The Developer role and Enable API keys toggle will be removed in the coming weeks in line with the original announcement aiming for the end of 2025.

What will happen if we fail to migrate?

Once the Developer role has been removed, users who have not been updated to use the “Manage APK keys” = Allow permission will:

• Be unable to access the API keys UI in Profile > Settings
• Find their API keys disabled, resulting in 3rd-party integrations failing

API keys are not deleted from Qlik Cloud and will automatically be re-enabled once a user has been assigned the required Manage API Keys permissions.

To resolve this, a Tenant Administrator needs to act as outlined in What action do I need to take?

Environment

• Qlik Cloud Analytics
• Qlik Talend Cloud

Data connections to Qlik Cloud or Qlik Sense Enterprise on Windows can fail for several reasons. In this article we aim to provide you with a step-by-step guide on how to begin troubleshooting data connectivity errors, ruling out the most common root causes. 

Content:

• Step 1: Verify the Database Connection
• Network Connectivity
• Credentials and Settings
• Step 2: Verify the Connection Details in Qlik
• In Qlik Cloud
• In Qlik Sense Enterprise on Windows:
• Step 3: Test the Connection in Qlik Sense
• Step 4: Review the Qlik Sense logs
• Step 5: Contact the Database Vendor

Step 1: Verify the Database Connection

Network Connectivity

The first step in your investigation is to verify basic network connectivity to the database.

1. Run a simple ping or telnet either from the Qlik Sense (on-prem) server or your desktop in case of a Qlik Cloud issue. 
2. Rule out a restrictive firewall blocking required ports on both target and source by reviewing or temporarily disabling the firewall rules. 

Work with your network administrator on both where necessary. 

Credentials and Settings

If the network and firewall settings are not the issue, verify if the database operates as expected.

• Is it online?
• Has a recent upgrade been performed and has this affected the current configuration (driver compatibility issues, disabling features, introducing new security capabilities which need to be reviewed, etc..)

Next, we verify if the credentials and settings in our connection are correct. The easiest way to do this is by logging in directly to the database using its native client. 

Examples of on-premise database clients include:

• SQL Server Management Studio (SSMS) for SQL Server databases
• Oracle SQL Developer for Oracle databases
• MySQL Workbench for MySQL databases

For cloud-based databases: 

1. Cloud provider console: Most cloud providers, such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP), have a web-based console that you can use to monitor and manage your cloud resources. 
2. Cloud database management tools: Some cloud providers offer database management tools that can help you monitor and manage your database resources. 
3. Logging and monitoring tools: You can use logging and monitoring tools, such as AWS CloudWatch, to monitor the performance and activity of your cloud database. These tools can provide valuable information about any issues that may be affecting your database, including connectivity issues.

The specific tools you use will depend on the cloud provider you are using and the type of database you have.

Step 2: Verify the Connection Details in Qlik

Verify if the following are correct in Qlik Sense (details may vary depending on your data connection):

• Host or server name
• Database name
• Port
• User name
• Password

In Qlik Cloud

Depending on your permissions, you can either edit/verify your connection directly in the Qlik Sense App Data Load Editor or in the Space.

Using the Data Load Editor:

1. Open the Qlik Cloud App
2. Open the Data Load Editor
   
   
   
   
3. Choose the Data Connection you want to verify: 
   
   

In Qlik Sense Enterprise on Windows:

Depending on your permissions, you can either edit/verify your connection directly in the Qlik Sense App Data Load Editor or in the Qlik Sense Management Console.

Using the Data Load Editor:

1. Open the Qlik Sense App
2. Open the Data Load Editor
   
   
   
   
3. Choose the Data Connection you want to verify: 
   
   

Using the Qlik Sense Management Console:

1. Open the Qlik Sense Enterprise Management Console
2. Open Data Connections 
3. Locate the Data Connection causing an issue and open it
4. You can review the Connection String and Username and Password from here 
   
   

Step 3: Test the Connection in Qlik Sense

Once you have confirmed the connection details, you can test the connection in Qlik Sense.

1. Open the Data Connection
2. Click Test connection
   
   
   
   Any eventual will help you identify the issue.

Step 4: Review the Qlik Sense logs

Data connections generally fail during reload. Qlik Sense will log details of the error or preceding warnings in the corresponding reload log. These error and warning messages can then be used to look up solutions or troubleshoot further. 

• Qlik Cloud: Qlik Cloud Log files: Where to find log information in Qlik SaaS editions 
• Qlik Sense on-premise: How to find the Script (Reload) logs in Qlik Sense Enterprise on Windows  

Search the warnings and errors in our knowledge base for known solutions. Begin your search here.

Step 5: Contact the Database Vendor

If you have completed all the above and have not found solutions in the Qlik knowledge base, reach out to the database vendor for additional support. They will be able to provide specific information on troubleshooting the issue with your specific database.

In Qlik Sense Enterprise on Windows, using QRS API '/qrs/App/table' by providing a body returns more than expected rows. 

Example: 

1. Using POSTMAN, we perform a POST call including the body:
   
   
   
   
2. With the above body, we expect that the response rows would ONLY contain name, id, and values as defined above in "list":
   
   
   
   
3. However, this POST request returns more than the requested rows, such as id, name, valueType, choiceValues, and privileges:
   
   

Resolution

This behavior has been identified as defect SUPPORT-6127.

It is caused by the default value of the parameter HideCustomPropertyDefinition set to true in the Repository.exe.config file. Changing the parameter from true to false resolves it.

To change the value: 

1. Navigate to C:\Program Files\Qlik\Sense\Repository\ and locate Repository.exe.config
2. Open Repository.exe.config in a text editor
3. Find HideCustomPropertyDefinition and set its value from true to false
   If you are running a multi node environment, make the change on each node. 
4. Save the Repository.exe.config file‘false’

Cause

Issue related to the default configuration setting of the parameter HideCustomPropertyDefinition in the Repository.exe.config file.

Internal Investigation ID(s)

SUPPORT-6127

Environment

• Qlik Sense Enterprise on Windows

Beginning with Qlik Sense Enterprise on Windows 2024, Qlik has extended CSRF protection to WebSockets. For reference, see the Release Notes.

In the case of mashups, extensions,and or other cross-site domain setups, the following two steps are necessary: 

1. Add additional response headers. These headers help protect against Cross-Site Forgery (CSRF) attacks.
2. Change the applicable code in your mashup or extension.

Content

• Add the Response Headers
• Adapt your Mashup or Extension code
• Workflow
• Verification

Add the Response Headers

The three additional response headers are:

Access-Control-Allow-Origin: https://localhost:8080
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: qlik-csrf-token

Localhost and port 8080 are examples. Replace them with the appropriate hostname. Defining the port is optional. 

If you have multiple origins, seperate them by comma.

Example:

For more information about adding response headers to the Qlik Sense Virtual proxy, see Creating a virtual proxy. Expand the Advanced section to access Additional response headers.

Adapt your Mashup or Extension code

In certain scenarios, the additional headers on the virtual proxy will not be enough and a code change is required. In these cases, you need to request the CSRF token and then send it forward when opening the session on the WebSocket. See Workflow for a visualisation of the process.

An example written in Enigma.js is available here:

• Authentication: Qlik Sense JSON Web Token (JWT) 
• Code Sample 

The information and example in this article are provided as-is and are not directly supported by Qlik Support. More assistance can be found on the Qlik Integration forum. Professional Services are available to help where needed.

Workflow

Workflow

Verification

To verify if the header information is correctly passed on, capture the web traffic in your browser's debug tool.

Environment

• Qlik Sense Enterprise on Windows November 2024 and later

Uploaded Excel files cannot be deleted. Clicking the delete icon (A) does not have the desired effect.

Affected versions

• Qlik Sense Enterprise on Windows November 2024 IR to Patch 6

Resolution

This is caused by QB-31249 and QCB-31331, which have been addressed.

Upgrade to the latest Qlik Sense Enterprise on Windows versions. See the Release Notes for details.

Internal Investigation ID(s)

QCB-31331, QB-31249

When Stitch replicates data from SaaS sources, it must operate within the API rate limits defined by each vendor. These limits determine how many API requests can be made within a specific time period to prevent server overload. Exceeding them typically results in rate limit errors (most often HTTP 429 responses), which can temporarily interrupt data replication.

This article outlines common API rate limit errors observed in Stitch integrations and provides best practices to help you minimize and handle these limits for reliable data replication.

Known API Rate Limit Errors

The exact error message for exceeding API rate limits varies across platforms, but all indicate the same underlying cause — too many API requests made within a defined time window.

Refer to the table below for examples of rate limit errors observed in popular Stitch SaaS integrations | Stitch Documentation:

Stitch recommendations & solutions for rate limit errors

• Reduce replication frequency of an integration if extractions frequently exceed the API’s rate limit.

• Stagger replication frequency schedules for multiple integrations that connect to the same source account to reduce the number of concurrent calls.

• Use the key-based incremental replication method | Stitch Documentation where available:
  
  Full Table Replication: Extracts all data from the Start Date indicated in the integration settings during every extraction. This usually requires many API calls as most integrations use pagination to retrieve data.
  Incremental Replication: Only fetches new or changed records since the last successful sync, based on a bookmark value. 
  Incremental replication can reduce API call volume by extracting less data, thereby reducing the number of API calls that would need to be made.

• Monitor extraction logs in Stitch for frequent 429 errors.

• Contact the API provider to request increased rate limits where applicable.

• Contact Qlik Support if needed.

Environment

• Stitch 

You may not be able to choose Automation in the Create menu or receive the following error when trying to create an automation:

An error occurred while trying to create an automation

Resolution

This is likely due to a permission issue.

1. Verify the Default Role (read more) permissions; Shared Automations must be allowed:
   1. Go to the Tenant's Administration Activity Center
   2. Go to Manage users
   3. Switch to the Permissions tab
   4. Click User Default (top right corner)
      
      
      
      
   5. Expand Content type
   6. Expand Automations
   7. Enable Shared Automations by setting the feature to Allowed
      
      
      
      
2. Verify the tenant's Automation Creator role (read more) is assigned to the user:
   1. Go to the Tenant's Administration Activity Center
   2. Go to Manage users
   3. Switch to the Permissions tab
   4. Expand the Automation Creator role 
   5. Assign a user or group where necessary
      
      
      
      

If the issue persists:

Verify that the user who needs to be able to perform the create automation activity:

• has access to the app
• has been added as a member to the space the app resides in
• has the appropriate level of individual permissions (for example, can view is not sufficient)
  

See Working in managed spaces for details.

Environment

• Qlik Cloud Analytics
• Qlik Automate

Using a Signed License Key with its Signed License Definition in a long term offline environment past the 90 days provided by Delayed Sync requires (besides license modification) additional configuration steps!

• No license has long term offline capability enabled by default. 
• Long term offline capability needs to be specifically approved by Qlik and the conditions of offline use agreed to by the customer. See Request license off-line approval - April 2020 and onwards. Once approval has been obtained through the CSO, the license will be modified with an additional attribute OFFLINE;YES;;
• Additional configuration changes are necessary for long term offline mode to function
• (Delayed Sync requires a Signed License Definition, but does not require additional configuration steps)

Configuration changes needed:

These changes will need to be done on all nodes running the Service Dispatcher. Not only the Central node. 

1. Stop the ServiceDispatcher service
   
   
2. As Administrator, open the Service Dispatcher services.conf file.
   
   Default location Qlik Sense on-prem: C:\Program Files\Qlik\Sense\ServiceDispatcher
   Default location QlikView: C:\Program Files\QlikView\ServiceDispatcher
   
   
3. Locate [Licenses.parameters]and add the parameter -offline 
   
   Example:
   
   [licenses.parameters]
   -qsefw-mode
   -offline
   -app-settings="..\Licenses\appsettings.json"
   
   
   
   The displayed order is required in the February 2024 IR release. Previous and future versions (Patch 2 and later) do not have a fixed order requirement.
   
   
4. Save the file
   
   
5. Start the ServiceDispatcher service

Once the changes has been done you will need to retrieve the updated SLD key from https://license.qlikcloud.com/sld and then apply the same for successful offline activation.

Note on upgrading: If using a version of Qlik Sense prior to November 2022, this file may be overwritten during an upgrade.  Please be sure to re-apply this parameter and restart the Service Dispatcher on all nodes after an upgrade. With Qlik Sense November 2022 or later, custom service settings are by default kept during the upgrade. See Considerations about custom configurations. 

Internal Investigation ID(s):

QB-25231

Environment

Qlik Replicate 

#Logtsream Task

There are a couple of examples when the metadata is not updated on the Logstream task:

• When a DDL change happened on the source table.
• When the tables are removed and added frequently to the Logstream task some tables will not get the changes during that time we have to do the Metadata refresh as below.

1. Stop the Replicate task (Child task).
2. Next in Parent Task (Logstream task), we have to do the Metadata refresh and then resume the Logstream task.

NOTE: This option will refresh the Logstream table's metadata inside the SQLite file. It will not drop any data for the Logstream task.

This is applicable for the Logstream task only.

3.  Then resuming the child task will fix the issues encountered.

You may encounter an error when attempting to send emails from Qlik Talend Runtime version v8.0.1.R2025-02-RT, specifically within OSGi Data Services. While email notifications work correctly when triggered from Talend Studio, they fail in the Runtime Environment, resulting in the following error:

java.lang.IllegalStateException: No provider of jakarta.mail.util.StreamProvider was found

Resolution

It has been resolved in the R2025-06-RT runtime patch.
To fix this, please upgrade Runtime to v8.0.1. R2025-06-RT or the latest available patch version, and re-deploy your route. 

Cause

It is a known issue in tSendMail component for Talend Runtime v8.0.1.R2025-02-RT environment and has already been reported to our R&D team.

Internal Investigation ID(s) 

Internal Jira case ID: SUPPORT-3698

Environment

• Talend Studio 
• Talend ESB 

When using Direct Access Gateway to insert rows one by one in a loop, performance comparisons with on-prem may show a considerable difference.

If you install the Data Gateway close to the Data Source in the same way you might have other Qlik products reading from the same Data Source, you will notice that completing the same activity takes longer, this is because with Direct Access Gateway you need to consider the time it takes for the data to be transferred from your Data Source to your Data Gateway and in addition the time it takes to be moved from your Direct Access Gateway server to Qlik Cloud.

Another issue you might encounter is that sending row by row in a loop can also increase the likelihood of failure due to the time required to complete a cycle. 

Resolution

It is recommended to send batches of inserts, rather than sending rows one by one. 

This article's example demonstrates how to write a script that adds a separate loop to control fifteen 5k batches: 

InsertTable:
LOAD
RowNo() as RowID,
Indicator,
"Group",
State,
Subgroup
FROM [lib://DG4 Space:DataFiles/Mental_Health_Care_in_the_Last_4_Weeks.csv]
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

Set vBulkInsert='';


for b=0 to 999//Just for basic sample

Let vid = Peek('RowID',$(b), 'InsertTable');
Let vIndicator = Peek('Indicator',$(b),'InsertTable');
Let vGroup = Peek('Group',$(b), 'InsertTable');
Let vState = Peek('State',$(b),'InsertTable');
Let vSubgroup = Replace(Peek('Subgroup',$(b),'InsertTable'),chr(39), chr(39) & chr(39));

LET vBulkInsert = '$(vBulkInsert)' & 'INSERT INTO Test.dbo.Mental_Health_2 ([id],[Indicator],[Group],[State] ,[Subgroup])
VALUES (''$(vid)'',''$(vIndicator)'',''$(vGroup)'',''$(vState)'',''$(vSubgroup)'')' & chr(10) & chr(13);

next b;
;


LET vBulkInsert = '$(vBulkInsert)' & '!'& 'EXECUTE_NON_SELECT_QUERY;';
TRACE '$(vBulkInsert)';
LIB CONNECT TO 'DG3 Space:Microsoft_SQL_Server_(via_Direct_Access_gateway)_Mytest';
SQL $(vBulkInsert)
;

Environment

• Qlik Direct Access Data Gateway - All Versions

You may be experiencing a critical problem where some Talend jobs open without any components in the Designer View. The jobs appear empty in Studio even after:

• In the workspace confirmed the .item, .screenshot, and .properties files exist for the job. 
• Deleting the workspace to reload the jobs from Git.

This article briefly introduces how to fix Corruption in a Git Repository for Qlik Talend Projects

How To

Rolling Back to an Earlier Commit

This behavior indicates that the corruption exists in the Git repository itself. The most effective way to restore a corrupted Git project is to roll back to a previous version of the Git branch where the jobs were intact.

Steps

1. Review the Git commit history of the affected project.
2. Identify a commit where the projects were complete and not corrupted.
3. Restore the repository to that commit to recover the project files.

Related Content

References for Git Rollback

How can I rollback a Git repository to a specific commit?| stackoverflow.com

Revert a Git Repository to a Previous Commit | sentry.io

Environment

• Talend Studio 
• Talend Data Integration 

Question  

Is there a limit on how many task deployments I can have on Qlik Talend Runtime Server?

No, there is no fixed limit.

Qlik Talend Runtime Server does not have a numerical limit on the number of deployed Data Services or Routes. However, the actual number of services that can be deployed and run concurrently depends on the available system resources (CPU, Memory, etc.) 

Environment

Talend ESB 

After applying a valid Signed License Key (SLK), the QlikView Server (QVS) remains Unlicensed in the QlikView Management Console. This occurs while a network proxy is used on the QlikView server host.

Resolution

This solution requires QlikView May 2024.

1. Navigate to %ProgramData%QlikTech\ManagementService\QVPR\ 
   
   
2. Locate LicenseService.xml and open it in an editor (may require administrative permissions)
   
   
3. Find the <LicenseService> section and modify the following parameter values to localhost:
   
   (A) ServerAddress="https://localhost:9200/"
   (B) ServerName="LicenseService@localhost"
   
   
   
   
4. Save the changes to LicenseService.xml
   
   
5. Navigate to %ProgramData%QlikTech\QlikviewServer\
   
6. Locate Settings.ini and open it in an editor (may require administrative permissions)
   
   
7. Find the [Authentication] section and change the following parameter's value to localhost:
   
   (C) NxServiceConnectionString=http://localhost:9200
   
   
   
   
8. Find the [Settings 7] section and change the following parameter's value to localhost:
   
   (D) LicenseServiceUrl=http://localhost:9200
   
   
   
   
9. Still in the [Settings 7] section, add the following parameter:
   
   CustomLicenseServiceUrl=http://localhost:9200
   
   The CustomLicenseServiceUrl parameter is required to prevent the QlikView server from reverting to default license service settings. 
   
   For details, see How to Modify the QlikView Server Settings.ini file.
   
   
10. Restart all QlikView services

Cause

QlikView cannot reach the license server when a network proxy is configured on the host machine. 

Internal Investigation ID(s)

SUPPORT-6241, QV-23738, QV-23918

Environment

• QlikView all versions

This article briefly introduces how to do transformation for Key Columns in Talend Cloud Data Integration

How To

1. Select the Replication Task, open the task and apply Global Transformation rules by clicking on "Add Transformation Rule" for the Replace Column value. Apply transformation for the key column.

   TransformationRule

2. Add a rule in the expression builder.

   RuleExpressionBuilder

3. Rule gets added for the Primary key column because the PK is defined in the Source.

   Expression

4. Suppose if applying same rule for another table where PK is not defined.And you explicitly define PK in the UI, you can notice that Rule has not been applied to the Primary key Column because the Global Rules will look in the source if the PK is defined or not, if defined it will add the rule for the corresponding PK Column.

   Expression2

5. To add the rule for the column, you need to go to expression builder at the table level and add the condition.

   Condition

6. Now you can see the Rule been added to the PK column which explicitly defined.

   Expression3

Environment

• Qlik Replicate 
• Talend Cloud 

When running a silent installation, Qlik Sense is installed without dialog prompts. This means all features, properties, and user selections are set before performing a silent installation. All setup options available in the installer user interface can be performed with silent operators.

For details, see:

• Performing a silent installation
• Performing a silent upgrade

The installation can be broken down into three steps.

Step 1: Prepare the installation in accordance with the Qlik Sense system requirements

1. Set up a shared folder. 
2. Ensure the folder is shared with the service account.
3. The service account should be a local administrator.

Step 2: Prepare the configuration file 

This file will be used in the next step and includes all remaining configuration settings. This must be configured for the installation to complete successfully. See Shared persistence configuration file syntax (choose your respective version).

We have attached an example file. You'll need to change 'xxx' to the shared folder network path. Please consider using a hostname or DNS name instead of localhost. 

Step 3: Execute the silent installation

Run CMD as an administrator, then provide the installation command with the required arguments. When building the command, do not forget to confirm that you have read the EULA with the argument accepteula(1|0). Customer agreements can be found at Legal Agreements.

Example script to execute a silent install:

Qlik_Sense_setup.exe [-silent] {-log "path\filename"} {layout="path"} {accepteula=1|0}{desktopshortcut=1|0} {skipstartservices=1|0} {installdir="path"} {userwithdomain="domain\user"} {userpassword="password} {dbpassword="password"} {hostname="www.machinename.domain.com"} {sharedpersistenceconfig="configfilepath"} {senddata=1|0} {skipvalidation=1|0} {databasedumpfile="path"}

Environment

With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)