Understanding and managing your Qlik Cloud subscription consumption is essential for maintaining predictable costs, ensuring uninterrupted service, and optimizing resource allocation across your organization. This guide provides you with the tools, strategies, and best practices to gain complete visibility into how your subscription is being consumed and implement proactive controls to stay within your capacity limits.

While Qlik Cloud measures consumption at the tenant level, you can achieve effective governance through strategic monitoring, automated alerting, and space-based management practices. This guide will walk you through the monitoring tools available, how to automate their deployment and refresh, and practical approaches to tracking consumption patterns and implementing controls that align with your organizational needs.

Content:

• Understanding the Administration activity center capacity consumption view
• The Home page capacity consumption dashboard
• How does this view fit into your monitoring strategy?
• Official consumption data: The Data Capacity Reporting App
• Automating the deployment of the consumption app
• Getting estimated usage with Qlik Cloud Monitoring Apps
• Automating Qlik Cloud Monitoring Apps deployment
• Proactive monitoring strategies: What to track and at what levels
• Monitoring automation runs
• Monitoring Data for Analysis
• Monitoring scheduled reloads
• Monitoring reports generated
• Practical approaches to controlling consumption
• 1. User education and communication
• 2. Alert-driven intervention workflow
• 3. Development vs. production separation
• Leveraging Qlik's alerting and distribution capabilities for consumption monitoring
• Available monitoring and distribution tools
• Setting up each monitoring approach
• Examples: Setting up consumption monitoring across key metrics
• Your action plan: From reactive to proactive
• Additional resources

Understanding the Administration activity center capacity consumption view

The Administration activity center Home page provides your first line of visibility into capacity consumption. Understanding what this view offers and how it complements the detailed monitoring apps will help you build an effective monitoring strategy.

The Home page capacity consumption dashboard

Navigate to the Administration activity center → Home to see a real-time dashboard summarizing capacity consumption. This view displays visual bar charts for consumption metrics relevant to your subscription:

Common metrics displayed:

• Data for Analysis: Purchased vs. used with color-coded breakdown (App Import, App Reload, Datafile); not available for user-based subscriptions
• Reports generated (monthly): Purchased count vs. used
• Standard automation runs (monthly): Purchased vs. used
• Third-party automation runs (monthly): Purchased vs. used
• Assistant questions asked (monthly): Purchased vs. used (if Qlik Answers is enabled)

Additional metrics may include Data Moved, Large App consumption, Qlik Predict deployed models, and others, depending on your subscription.

Metrics appear dynamically as features are adopted. If no one has asked an assistant question yet, that metric won't display until first use, keeping the dashboard focused on what you're consuming.

The Data for Analysis chart shows a current snapshot with the last update timestamp. Most metrics update multiple times per hour, providing near real-time visibility into your consumption position.

How does this view fit into your monitoring strategy?

The Administration activity center provides high-level consumption visibility designed for rapid assessment. For detailed analysis, investigation, and proactive monitoring, you'll complement this view with a set of monitoring apps.

Daily quick check (2 minutes):

1. Scan consumption bars to identify any metrics approaching capacity
2. Review indicators showing current usage levels
3. Verify Data for Analysis timestamp shows recent data

When you need more detail, the Home page tells you what is being consumed. The monitoring apps tell you who, where, when, and why. Capacity subscriptions should use the Data Capacity Reporting App as the source of truth, while the Qlik Cloud Monitoring apps can be treated as estimated consumption reports, for example:

• For automation consumption details: Use the Automation Analyzer
• For data consumption details: Use the Data Capacity Reporting App and Reload Analyzer
• For report consumption details: Use the Report Analyzer

Use the Home page for daily checks and status awareness. When consumption requires attention or you need to understand trends, drill into the appropriate monitoring app for detailed analysis.

For more information, see Monitoring resource consumption.

Official consumption data: The Data Capacity Reporting App

The Data Capacity Reporting App is your official, billable record of consumption for capacity-based subscriptions. This Qlik-supported application is generated once per day (morning Central European Time) and provides the definitive view of your consumption against your entitlement.

The app tracks eight key value meters across the current and previous two months:

• Data for Analysis: Total data loaded into or created in Qlik Cloud (measured by monthly peak usage)
• Data Moved: Volume of data moved to cloud destinations via Qlik Talend Data Integration
• Third Party Transformations: Datasets used in transformations but not delivered by Qlik Talend Data Integration
• Automation Runs: All automation executions using Qlik Automate
• Reports: Reports distributed using Qlik Reporting Service
• Job Executions: Number of Talend job task runs (Qlik Talend Cloud subscriptions)
• Job Duration: Total duration of Talend job executions (Qlik Talend Cloud subscriptions)

This app represents your billable consumption record. The data in this app is what Qlik uses for official capacity reporting and billing purposes. When there's any discrepancy between this app and other monitoring sources, the Data Capacity Reporting App is the authoritative source. This app refreshes only once daily, meaning you see yesterday's official position, not real-time consumption. For more frequent monitoring and estimated usage, you'll complement this with the Qlik Cloud Monitoring Apps.

For detailed information, see Monitoring detailed consumption for capacity-based subscriptions.

Automating the deployment of the consumption app

Rather than manually distributing the consumption app from the Administration activity center each day, automate this process using the Capacity consumption app deployer template in Qlik Automate.

Setup steps:

1. Create a new automation in Qlik Automate
2. Navigate to the App Installer category
3. Select "Capacity consumption app deployer" template
4. Configure variables (space names, versions to keep)
5. Test manually once
6. Schedule to run daily around midday CET

This automation creates or uses designated spaces, imports the latest version, publishes it to a managed space, and maintains version history according to your configuration. You now have a single source of truth that updates automatically each day. Create automations or alerts on the published app for automated insights.

For complete details, see the Qlik Community article: Automate deployment of the Capacity consumption app with Qlik Automate.

Getting estimated usage with Qlik Cloud Monitoring Apps

While the official consumption report updates once daily, the Qlik Cloud Monitoring Apps (community-supported) can be reloaded multiple times per day up to your contractual reload limits, giving you more timely estimated usage insights.

The Qlik Cloud Monitoring Apps provide estimated consumption data that may differ slightly from the official Data Capacity Reporting App. Use these apps for trend monitoring, troubleshooting, and proactive management, but always refer to the Data Capacity Reporting App for official billable consumption figures.

Particularly valuable monitoring apps include:

App Analyzer: Provides comprehensive application usage and operational analytics, including:

• App access patterns and session frequency by user
• Sheet and object usage tracking
• App metadata and lineage information
• Historical snapshots to track changes over time

Automation Analyzer: Provides detailed analysis of automation runs, including:

• Run frequency by automation, space, and user
• Success/failure rates and error patterns
• Execution duration trends
• Third-party block usage tracking

Reload Analyzer: Tracks data refresh activity, including:

• Reload frequency by app and space
• Duration and resource consumption
• Success rates and failure patterns
• Reload scheduling patterns

Access Evaluator: Analyzes user roles, access, and permissions across your tenant

Report Analyzer: Tracks report generation, including:

• Report task execution frequency
• Report distribution patterns
• Report generation consumption

Entitlement Analyzer: For user-based subscriptions, provides insights into:

• Professional and Analyzer seat allocation and utilization
• Analyzer capacity consumption by user (for Analyzer capacity licenses)
• User session patterns and license assignment

For a complete list of available monitoring apps, see the Qlik Community article: The Qlik Sense Monitoring Applications for Cloud and On-Premise.

Automating Qlik Cloud Monitoring Apps deployment

The Qlik Cloud Monitoring Apps deployer template simplifies installation and maintenance of these community apps.

What it handles:

• Installs/upgrades selected monitoring apps from Qlik's OSS GitHub
• Creates required API keys and data connections
• Manages API key rotation to ensure connections remain operational
• Creates or uses existing shared and managed spaces
• Schedules regular reloads (configurable frequency)
• Verifies prerequisite settings and notifies if configuration changes are needed

Reload frequency considerations: You can reload these monitoring apps multiple times per day to get more current estimated usage data. However, each reload counts against your tenant's reload capacity limits. Consider your contractual limits when scheduling. For most organizations, reloading 2-4 times per day provides a good balance between timely insights and consumption.

For complete implementation details, see the Qlik Community guide: Qlik Cloud Monitoring Apps Workflow Guide.

The monitoring apps are also available on GitHub: qlik-oss/qlik-cloud-monitoring-apps.

Proactive monitoring strategies: What to track and at what levels

Effective governance comes from monitoring consumption at multiple levels and implementing proactive interventions. Here's how to approach monitoring for key consumption metrics.

Monitoring automation runs

Automation runs are counted across all automations in your tenant, regardless of owner or run mode (manual, scheduled, triggered, webhook, API). Test runs within the automation editor also count toward your limit.

What to monitor:

Tenant level:

• Total automation runs per month against your purchased capacity
• Rate of consumption (tracking whether you're on pace to exceed limits)
• Third-party block usage (may incur additional costs depending on subscription)

Space level:

• Which spaces are generating the most automation runs
• Identify spaces with unusually high consumption

Automation level:

• Individual automation run frequency
• Failed runs that retry excessively
• Scheduled vs. triggered vs. webhook run distribution

User level:

• Which users own the most frequently running automations
• Users with failed automations requiring attention

Example alert scenario: Using the Automation Analyzer, create alerts when:

• Total third-party (billable) runs reach 80% of purchased capacity
• Any single automation runs more than 100 times per day
• Failed run rate exceeds 20% for any automation
• A specific space's automations account for more than 40% of total runs

Monitoring Data for Analysis

Data for Analysis is measured by monthly peak usage. A single day's spike can impact your entire month's consumption.

This data is only available via the Data Consumption report; it is a lagging metric and currently lacks customer data such as app names, user names, and space names. As such, use of an automation template to provide notifications may be preferable to standard alerts, and some app size metrics may be better analyzed in the reload analyzer.

What to monitor:

Tenant level:

• Daily peak compared to purchased capacity
• Trend analysis: Are daily peaks increasing?
• Current month peak vs. previous months

App level:

• Which apps are contributing most to data volume
• New apps that significantly increase consumption
• Apps with unexpectedly large data reloads

Space level:

• Data consumption by space

Example alert scenario: Using the Data Capacity Reporting App and Reload Analyzer:

• Alert when the daily peak reaches 80%, 90%, 95% of purchased capacity in the Data Capacity Reporting App
• Alert when any single app reload increases data volume by more than 20GB in the Reload Analyzer
• Alert when a space's total data exceeds a defined threshold in the Data Capacity Reporting App

Monitoring scheduled reloads

Each subscription tier has limits on maximum concurrent reloads, and capacity subscriptions have daily reload counts. Exceeding concurrent limits causes queuing; exceeding daily limits can block operations.

What to monitor:

Tenant level:

• Scheduled reloads that exceed contractual limits
• Concurrent reload patterns during peak hours
• Failed reload rate

Space level:

• Reload frequency by space (wasted work)
• Reload schedule overlap that causes queuing

App level:

• Apps with multiple reload tasks
• Apps with long-running reloads that block concurrency

Example alert scenario: Using the Reload Analyzer:

• Alert when an app has more than one reload task active
• Alert when failed reloads exceed 10% in any 24-hour period
• Alert when reload queuing occurs during business hours

Monitoring reports generated

Report generation counts vary by subscription tier, with add-on packs available for purchase. Across all reporting capabilities, tenants have a maximum of 30,000 reporting-related requests per day.

What to monitor:

Tenant level:

• Monthly report generation against purchased capacity
• Rate of consumption throughout the month

Report task level:

• Which report tasks generate the most reports
• Report tasks using cycling (can generate up to 500 unique reports per task)

Example alert scenario: Using consumption reporting and monitoring apps:

• Alert when monthly reports reach 75% of capacity
• Alert when any single report task generates more than 100 reports in a day
• Alert when daily reporting requests approach 25,000

For detailed information on report limits, see Qlik Reporting Service specifications and limitations.

Practical approaches to controlling consumption

While Qlik Cloud measures consumption at the tenant level, you can implement effective governance practices that provide meaningful control over resource usage.

1. User education and communication

Make users aware of the impacts of their consumption and empower them to monitor their own usage.

Implementation:

• Publish monitoring apps to managed spaces accessible by content creators
• Regular communications showing tenant-wide consumption status to creators

2. Alert-driven intervention workflow

Create early warning systems that trigger well before official capacity notifications.

Implementation:

Alert tier 1 (60-70% of capacity):

• Notification to admins and space owners & managers
• Review consumption trends
• Identify optimization opportunities

Alert tier 2 (75-85% of capacity):

• Formal review meeting
• Suspend non-critical scheduled executions (automation runs, assistants, reload tasks, report tasks, etc)
• Contact the account manager about potential overage

Alert tier 3 (90%+ of capacity):

• Disable non-essential executions (automation runs, assistants, reload tasks, report tasks, etc)
• Defer development/testing activities to next month
• Discussion about capacity expansion or overage management

3. Development vs. production separation

Use strict space controls to prevent development consumption from impacting production limits, or procure a development subscription from Qlik to fully isolate capacity.

Implementation:

• Create clear development space boundaries
• Limit development automation runs through governance
• Schedule development reload activities during off-peak hours
• Regular cleanup of abandoned development content

For information on subscription types and capacity planning, see Qlik Cloud capacity-based subscriptions.

Examples: Setting up consumption monitoring across key metrics

The following examples demonstrate how to set up comprehensive monitoring for different consumption metrics. These examples assume you have deployed the Capacity consumption app deployer (running daily around midday UTC) and the Qlik Cloud Monitoring Apps deployer (running overnight) with default settings.

Explore the apps to discover a wide range of operational metrics you can monitor, alert, automate, and subscribe to.

Example 1: Third-party automation runs monitoring and alerts

Scenario: Your organization uses third-party automation blocks (such as Slack, ServiceNow, or Salesforce connectors), which incur additional costs based on consumption. You need to monitor third-party automation runs to prevent unexpected charges and identify which automations are driving costs.

Navigate to the Automation Analyzer and create the following alerts:

Alert 1: Third-party runs approaching limit

• Location: Create on the "Run Quotas" chart in the "Dashboard" sheet by right-clicking on the Billable bar. This will create an alert with three useful measures present:
  
  
  
  
• Condition: "Runs Billable Remaining (Bar)" Less than 2000 (for example):
  
  
  
  
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Alert 2: Individual user excessive third-party runs

• Location: On the "Dashboard" sheet, open the "Runs by executor" tab, and create an alert from this table.
• Condition: Where "Runs Billable CMTD" is Greater than 1000 (or a reasonable limit for an individual user in the tenant):
  
  
  
  
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Automation - Automation usage notifier: Automation or user email notifications

This approach allows you to send email notifications or take action directly on executing users or owners, while sending a fully customised template to notify them that they are approaching limits.

See Automation Usage Notifier | GitHub for details.

• Location: Create a new automation by importing the JSON file provided at automationNotifier. There is a readme present there, in summary:
  • Monitors automation run usage against tenant quota
  • Works directly with the Automation Analyzer monitoring app
  • Supports threshold limits by (automatic lowest-limit enforcement):
    • Absolute run count
    • Percentage of licensed quota
  • Assessment modes:
    • Per automation (notify owners)
    • Per user (notify heavy users)
  • Automatic fallback notification to admin group for orphaned automations or deleted users
  • Rich HTML email alerts with direct automation links
  • Safe to schedule daily or trigger after analyzer reload
  • Fully configurable via simple variables
  • Designed for soft governance and early quota protection

Example 2: Data for Analysis capacity monitoring

Scenario: Your Data for Analysis consumption is measured by monthly peak usage. You need early warning when daily peaks are trending upward and visibility into which apps are driving consumption.

Step 1: Create peak usage alerts in the Data Capacity Reporting App

Alert 1: Warning capacity threshold

• Location: Create on the "Data for Analysis" current month peak usage chart
• Condition: Set "Capacity remaining" to Less than 0.3 (for 30%; adjust to business need)
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Alert 2: Critical capacity threshold

• Location: Create on the "Data for Analysis" current month peak usage chart
• Condition: Set "Capacity remaining" to Less than 0.15 (for 15%; adjust to business need)
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Step 2: Create a weekly trend subscription

In the Data Capacity Reporting App:

1. Create a sheet showing: Weekly peak trend (last 8 weeks), Top 10 apps by data volume, Space breakdown
2. Create a subscription
3. Schedule: Monday at 9:00 AM
4. Recipients: Administrators, managers
5. Format: PDF
6. Name: "Weekly Data for Analysis consumption report."

Example 3: Comprehensive monthly consumption review package

Scenario: You want to create a comprehensive monthly review package that combines official billable data with estimated usage trends to facilitate informed capacity planning discussions.

Create a Qlik Automate automation that runs on the first business day of each month:

1. Trigger: Scheduled monthly on the first weekday at 9:00 AM
2. Block 1: Generate a snapshot from the Data Capacity Reporting App using the Qlik Reporting connector:
   • All value meters with official consumption vs. purchased capacity
   • Month-over-month trends
   • Year-to-date comparison
3. Block 2: Generate a snapshot from Automation Analyzer using the Qlik Reporting connector:
   • Top 10 consuming automations
   • Executor breakdown
   • Space breakdown
4. Block 3: Generate snapshot from Reload Analyzer using the Qlik Reporting connector:
   • Top 10 apps by reload duration
   • Reload frequency analysis
   • Failed reload summary
5. Block 4: Compile snapshots into a single PDF or PowerPoint
6. Block 5: Distribute to stakeholder group via email

Your action plan: From reactive to proactive

The key to managing Qlik Cloud consumption effectively is shifting from reactive (waiting for 80%/90%/100% notifications) to proactive (continuous monitoring with early intervention).

This week:

• Deploy the Capacity consumption app deployer automation (if on a capacity-based subscription)
• Deploy the Qlik Cloud Monitoring Apps deployer automation with your selected monitoring apps
• Review the deployed monitoring apps and familiarize yourself with available metrics
• Set up your first consumption alert targeting your highest-risk metric

This month:

• Configure a comprehensive tiered alert system across all relevant consumption metrics
• Establish consumption targets for high-usage spaces or functions
• Create documentation for users on consumption best practices
• Conduct the first monthly consumption review meeting

Ongoing:

• Daily: Quick review of the Administration activity center Home page for the current status
• Weekly: Review of alert notifications and trend analysis in monitoring apps
• Monthly: Formal consumption review meeting with stakeholders
• Quarterly: Comprehensive audit of automations, apps, and reload schedules to identify optimization opportunities
• Continuous: Regular communication with users about consumption practices and organizational targets

By combining automated monitoring through the official Data Capacity Reporting App and community monitoring apps, tiered alerts, clear governance policies, and proactive intervention workflows, you can effectively manage your subscription costs and maintain predictable, controlled consumption across your organization.

Additional resources

Qlik Help documentation:

• Monitoring resource consumption
• Monitoring detailed consumption for capacity-based subscriptions
• Qlik Cloud capacity-based subscriptions
• Understanding the subscription value meters
• Managing automations
• Qlik Automate limitations
• Qlik Reporting Service specifications and limitations

Qlik Community Official Support Articles:

• The Qlik Sense Monitoring Applications for Cloud and On-Premise
• Qlik Cloud Monitoring Apps Workflow Guide
• Automate deployment of the Capacity consumption app with Qlik Automate

Developer resources:

• Monitor your deployment (Qlik Developer Portal)
• Qlik Cloud Monitoring Apps on GitHub

The Qlik Cloud Monitoring Apps are community-supported and provided as-is. They are not officially supported by Qlik, though they are maintained through Qlik's Open-Source Software GitHub. The Capacity consumption app deployer and Qlik Cloud Monitoring Apps deployer are supported automation templates found in the template picker catalog.

Content

• Background
• Qlik Licensing Service (QLS)
• Signed License Key (JWT)
• What is a JSON Web Token?
• What’s in this for me as a Customer?
• Activation Using the Signed License Key
• Frequency in which license information is updated
• Data Transmitted by an Activation Request
• Activation Reply
• Analyzer Capacity License Report Process
• Data Transmitted
• Sync Reply
• User Assignment Sync Process
• Data Transmitted
• Reply fromLicense Backend

Background

Qlik Products have generally utilized license keys to enforce license entitlements and use rights.  During activation, the licensed entitlement is downloaded to the product in the format of a Licensing Enabler File (LEF). Activation requires internet connectivity to the deployment and is triggered by entering a 16-digit serial number and a corresponding control number. Offline activation is also supported using a manual LEF by copying and pasting a text file into the activation user dialog. Communication is through an http protocol.

Qlik Licensing Service (QLS)

Introduced with the February 2019 release[GM1]  of Qlik Sense Enterprise, Qlik has developed an alternative process for product activation. There have been several drivers for this change, including a move to an https protocol for a more secure connection between the Customer deployment and Qlik infrastructure. More information follows below. 
 
To allow for Customers to make the decision when to move, Qlik has introduced the use of a Signed License Key to determine which activation method to use. Over time Qlik Licensing Service will replace the current activation process, but for now both methods of activations will work.

Signed License Key (JWT)

As mentioned above, Qlik has added one additional way to activate Qlik products. 

What is a JSON Web Token?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWT’s can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
 
Although JWT’s can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it. That is why we refer to this as the Signed License Key.

What’s in this for me as a Customer?

With the use of a Signed License Key, there are more Product and deployment offers to use.

• Use of multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
• Use of multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
• Use of the consumption-based license, Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.

All of the above is enabled by the use of the Signed License Key. This made possible as the local deployment will sync entitlement data with all deployment’s using the same Signed License Key through an online database, License Backend, hosted by Qlik within Qlik Cloud.

Activation Using the Signed License Key

This is initiated by entering a Signed License Key to the Control Panel. The request is performed by the service Licenses using port 443 (https protocol procedures applies).

Frequency in which license information is updated

Assignment information (what user has what type of access assigned) is synchronized from the license service to license.qlikcloud.com every 10 minutes. 
Changes to a license (such as adding additional analyzer capacity) can take up to 24 hours to be retrieved.

Data Transmitted by an Activation Request

Activation Reply

Analyzer Capacity License Report Process

(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)

Data Transmitted

Sync Reply

User Assignment Sync Process

Data Transmitted

Reply from License Backend 

 
This Reference Guide is intended solely for general informational purposes and its contents do not form part of the product documentation.  The information in this guide is subject to change without notice.  ALL INFORMATION IN THIS GUIDE IS BELIEVED TO BE ACCURATE BUT IS PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.  Qlik makes no commitment to deliver any future functionality and purchasing decisions should not be based upon any future expectation.

Long term offline capability for the releases April 2020 and onwards requires a change to the license (addition of a further attribute), which can only be added after a special approval from the Customer Success Organization.

See below for how to submit the request for approval and proceed. 

1. Contact the Qlik Support team using Chat or the Qlik Support Portal.
2. You will need to sign an offline addendum and share the signed addendum with Qlik Support. Choose between one of the two addenda attached to this article; one for banking and one for non-banking customers. 
3. Provide the License key that needs to be offline enabled, as well as the current Product version details, and the reason why the connection to Qlik's license back end (LBE) cannot be established.
4. Request the support team to update the temporary offline feature (Delayed sync) and activate the product via an SLD key first, providing temporary offline access until the permanent offline feature is enabled. Review: How to activate Qlik Sense, QlikView, and Qlik NPrinting without Internet Access
5. Once the license is processed and fulfilled for permanent offline activation, here is how the license activation process for long-term offline is done:
   • Long term offline use for Qlik Sense and QlikView Signed Licenses
   • Long term offline use for Qlik NPrinting Signed Licenses
   • Long term offline use for Qlik Catalog

As part of the agreement for granting a customer offline license usage, the customer is required to regularly upload User Assignment log files. See Offline User Assignment logs.

This process is not required for OEM customers; OEM customers can contact support directly through chat or by creating a case using the Support portal to have the offline parameters enabled.

Related Content 

Activate Qlik Products without Internet access - April 2020 and onwards
Long term offline use for Qlik Sense Signed Licenses
How to send User Assignment log files to Qlik? (Long term offline license activation) 

Environment

• Qlik Sense Desktop
• Qlik Cloud Analytics

You may not be able to either save or 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

Your license may not include Qlik Automate, or permissions need to be updated.

What licenses include Qlik Automate?

• Qlik Cloud capacity-based subscriptions (see Qlik Cloud Analytics subscription options)
• Qlik Cloud user-based subscription with Qlik Sense Enterprise SaaS; Qlik Sense Business does not include Qlik Automate (see Qlik Automate in user-based subscriptions).

What Permissions must be set?

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

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)

When using Talend Administration Center, you may encounter the following message

Error: License token will expire in xx days

This message refers to the license token expiring, not the license itself.

Resolution

Talend Administration Center has Internet access

• TAC automatically validates the license token.
• No manual action required.

Talend Administration Center has no Internet access

If TAC does not have Internet connectivity, follow these steps

1. Go to Talend Administration Center page and click:
   • Validate your license manually OR
   • Generate Validation Request (button name depends on TAC version).
2. A popup window will display a validation link (e.g. https://www.talend.com/api/get_tis_validation_token_form.php).
3. Copy this link into a text file.
4. On a machine with Internet access:
   • Paste the link into a browser.
   • Retrieve the validation token (e.g. 5xEfMp1ozPyiDTTUqzUHI8K3Xuvqx/iipc+).
5. Return to TAC on the offline system.
6. In the popup window:
   • Paste the validation token.
   • Click Enter validation token.

Your license token is now validated manually.

Cause

Talend Administration Center (TAC) requires an Internet connection during license token validation and the license token must be periodically validated.

• If TAC has Internet access, the token is validated automatically.
• If TAC does not have Internet access, you must manually validate the license token.

Related Content 

• Refer to the generating-validation-request-without-internet-connection for more details.
• You can also configure notifications to alert administrators before the license token expiration date managing-notifications.

Summary

If TAC has Internet access, license token validation is automatic. If not, use the manual validation process by generating a request, retrieving the validation token from another machine, and pasting it back into TAC.

Environment

• Talend Administration Center 
• Talend Studio 

Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.

The following requirements need to be met:

• A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
• Use of a Professional license. Analyzer licenses do not support Desktop Authentication
  For legacy token license: User and Login Passes allow Desktop Authentication
• No TEST license. Test licenses disallow the use of authentication links 
• Compatibility must be met. See Qlik Sense Desktop patch process and compatibility with on-premise installs and Qlik Cloud .

After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.

Environment

Qlik Sense Desktop 
Qlik Cloud 
Qlik Sense Enterprise on Windows 
Qlik Sense Business 

Related Content 

Starting Qlik Sense Desktop | Qlik Sense on Windows Help 
Starting Qlik Sense Desktop | Qlik Cloud Help
Configuring Qlik Sense Desktop authentication link 
How to authenticate Qlik Sense Desktop against SaaS editions 
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server  

Core-based and capacity-based licensing is a change from traditional licensing. Rather than limiting the number of users who can access the Qlik Sense site by a limit on tokens, core-based licensing restricts user access by limiting the number of CPU cores which can be used by the Engine to deliver end-user content.

With a core-based license, there is no functional reason to use the License Monitor app since the users will not use tokens. Instead, consumption of apps can be gauged by reviewing the Session Overview and Session Details sheets on the Operations Monitor.

Environments:

• Qlik Sense Enterprise on Windows with Core-based license

After applying the license, the administrator should review the Engine configuration to ensure that sufficient capacity has been assigned to the Engine(s) in the Qlik Sense site.

In this example, 256 cores are allocated to the license but the Central only has 8 available cores:

 

Opening the QlikView Management Console (QMC) shows an orange banner across the top:

Lef expires DD/MM/YYYY

• QlikView any version

Expired Maintenance

Your maintenance support period has or is going to soon expire. Note that this can apply for both a QlikView Server license as well as a QlikView Publisher license. 

Review your LEF information for the following tag:

Perpetual License: 

• PRODUCTLEVEL;10;;2019-01-31
• PRODUCTLEVEL;30;;2019-01-31

Subscription License:

• TIMELIMIT;VALUE;2021-06-30;2022-06-30

To solve:

If you have not renewed your maintenance contract, this is expected and working as designed. Although the banner reads, the system remains working, but cannot be upgraded or supported by Qlik.

If your contract has been renewed, do the following:

1. Go to the QlikView Management Console
2. Navigate to System > Licenses
3. Choose your QVS@node/QMS@node  (check both)  and open the QlikView Server Licenses tab (Note: Be sure to check the Publisher license key as well.)
4. On the bottom, click: Update License from Server
   
   
   
   
5. Restart the QlikView services.

NOTE: 

• Be sure to check the Publisher license key as well.  If the Publisher LEF has expired it will also display the orange banner. You will need to update the License as well. 
• If the license has been extended with a time limit, example - TIMELIMIT;VALUE;;2022-05-21 the product will work until the mentioned time limit date  how ever the banner will still show the expired message in the management console, this is work as design.

Signed License Key applied

Another root cause may be a known issue with Signed key License on QlikView 12.40, or improper permissions assigned to Qlik Service Dispatcher. Product Defect ID(s): QV-17628

To solve:

If you are using version 12.40, note that there is a new service called Qlik Service Dispatcher. An admin account needs to be applied to resolve the issue. Qlik Management Service (QMS) may also need to be restarted as a workaround.

This issue is resolved in 12.50.

Beginning on the 30th of January, Qlik introduced the concept of 3rd party runs in Qlik Automate. This is the first step towards a shift in our packaging that will focus on third-party runs only, while standard runs become free of charge.

This shift will happen over the course of a couple of months, giving you sufficient time to analyze your usage and make adjustments if necessary. Please reach out to your account manager if you have any questions.

Contents

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Introduction of third-party runs (Jan 30th)
• Switch to new packaging (April 2nd)
• Enforcement of overages (May 6th)
• Packaging details
• FAQ

Timeline

The timeline below 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 6th: 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

Introduction of third-party runs (Jan 30th)

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.

Switch to new packaging (April 2nd)

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

Enforcement of overages (May 6th)

1. When your monthly third-party runs are exhausted, overages will be enforced.
   1. For Capacity licenses with included third-party runs only, automations with active third-party blocks will no longer start and an overage status will be displayed. 
   2. For Capacity licenses with purchased third-party runs, overages will be charged according to your contract and configuration.
   3. For User based licenses with included or purchased third-party runs, automations with active third-party blocks will no longer start and an overage status will be displayed. 
2. Automations without active third-party blocks will continue to run (since they cannot generate third-party runs).

Packaging details 

The below table provides an overview of the new packaging for automations that will come in effect on April 2, 2025. Please reach out to your account manager for quotes and pricing related questions. 

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. Details are available in the above section "Packaging details".

4. Why are some automations with third-party blocks missing the label "Contains third-party blocks"?
An automation will only receive the label when someone performs a manual run or saves it in the editor. We are planning a new update that will apply this label to all automations with active third-party blocks regardless of someone saving them or not.
Please note that regardless of this label being on an automation or not, automation runs will still be evaluated and receive a correct billable yes/no label.

The video above demonstrates how to convert Qlik Sense Enterprise servers with Tokens to the Professional and Analyzer capacity licensing model.

The conversion breaks down like this:

• User Access Passes -> Professional
• Everyone else into Analyzer Capacity

Steps

1. Copy and Save existing User Access rules, storing for future reference.
2. Do the same for Login Access rules
3. Paste the Signed License Key (SLK) in the signed license box, and hit Apply
4. Recreate the Professional Access rules from scratch or copy and paste from the User Access Rule.
5. Validate the rule and click Apply
6. Recreate the Analyzer Capacity access rule from scratch or copy the Login Access rule
7. Validate the rule and click Apply

Environment

• Qlik Sense Enterpise

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.

Related Content 

Please refer to the Qlik Sense® License Conversion Policy dated March 2021 for details.

Transcript

Hello and welcome to this short video guide on upgrading a Qlik Sense token server to a Qlik Sense Professional and Analyzer subscription license.

Our starting point for this upgrade guide is a very simple Qlik Sense Enterprise server, which is using the token style license. That means users gain access using either a User Access or a Login Access pass. Token style Qlik Sense uses the legacy LEF license with a serial and control number activation. This will be replaced in the Professional and Analyzer model license with a Signed License Key (SLK).

Make sure that you copy or save the existing user access rules storing the rules for future reference. We will do the same for the login access rules. Copy and save the rule conditions for future reference.

When you're issued with your new Qlik Sense Enterprise Professional and Analyzer subscription license, you will be issued a new license key or a new tenant. You may continue to use the old Qlik Sense Enterprise token license for up to four months. This will allow you to stand up a new Qlik Sense Enterprise site with Professional Analyzer users in parallel, and transition over time; or do it in one big go.

In this example, we are going to upgrade an existing Qlik Sense token server using the Signed License Key to move it to the Professional and Analyzer user model. Paste the Signed License Key in the signed license box and hit apply. When the license is successfully applied, you will see the license number as well as a license summary on the summary page. In this example, we have 4 Professional Users, as well as 8,000 minutes of Analyzer Capacity per month. There are no user allocations carried over from the old token model.

We need to recreate the Professional access rules. You can create rules from scratch or copy and paste the old token rules to a new Professional allocation rule, like so. Make sure you validate the rule and then hit apply.

We will do the same thing for the Analyze Capacity access rule. Copy the old token access rule for login access and paste it in the analyze capacity access rule. Validate the rule and hit apply. A quick test will validate that the Professional user access rules are functioning correctly. And here we can see that a Professional user was successfully allocated according to the rule we've set up.

Now we will check that the Analyzer capacity allocation rule is also working as expected. Click on the license usage summary tab; and here you can see that 6 minutes of analyzing capacity have been consumed. Everything is working as expected.

Thank you for watching. We hope you found this video useful.

If you would like more information, take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in the Qlik product forums on Qlik community; or check out the support program space. Here you can search for answers in the support knowledge base, learn directly from Qlik experts via support webinar like Techspert Thursdays, and don't forget to subscribe to the support update blog. Thanks for watching.

After licensing a new Qlik Replicate Endpoint that requires an Endpoint Server (such as Salesforce, MongoDB, BigQuery) one or more Endpoint Servers cannot be reached. 

The message One or more Endpoint Servers cannot be reached is displayed and the individual servers are listed as disconnected in the status column.

Resolution

1. Stop:
   • All running tasks
   • The Qlik Replicate Server or Attunity Replicate Server service
   • The Qlik Replicate UI Server services
     
     
2. Verify that the endpoint server java.exe is not running:
   1. Open your Windows Task Manager
   2. Switch to Details
   3. Search for java.exe
      
      
      
      
   4. If you can locate the java.exe running, right-click and terminate it
      
      
3. Open a cmd.exe window as Administrator 
   
   
4. Change to the Qlik Replicate bin directory. Default: C:\Program Files\Attunity\Replicate\bin
   
   
5. In the cmd.exe window, run:
   

   ~\bin>repctl -d "D:\attuntity\replicate\data" exportrepository​

   Note: "D:\attunity\replicate\data"  is an example of the data folder location.
   
   
6. This will create the following file:
   
   $QLIK_REPLICATE_INSTALL_ROOT\data\imports\Replication_Definition.json​
   
   
7. Open the Replication_Definition.json in a text editor and look for the section for the Local Endpoint Server.
   
   Example of the section: 
   

      "endpoint_servers": [{
              "name": "Local",
              "host": "localhost",
              "port": 3560,
              "password": "{ZASomeRandomLettersAndNumbersHereXXXXXXXXXXXXXXXXXXX}",
              ...
          }]
   ​

    

8. Edit the password for that section, by changing it to say:

      "endpoint_servers": [{
              "name": "Local",
              "host": "localhost",
              "port": 3560,
              "password": "password",
              ...
          }]

    

9. In the cmd.exe window, run: 
   

   repctl -d "D:\attunity\replicate\data" importrepository json_file=Replication_Definition.json​

    

10. In Windows file explorer, rename the folder:
    $QLIK_REPLICATE_INSTALL_ROOT\data\endpoint_srv\data to data_old
    
11. Start the Qlik Replicate Server or Attunity Replicate Server and Qlik Replicate UI Server services.
    
    

12. Log back into the Qlik Replicate console and verify that your local endpoint server reports as running in the status column. 

Environment

Qlik Replicate 7.0 and later

The problem occurs when applying a valid SLK to QlikView. When clicking Apply License, the following error is shown:

Error when applying license: Post "https://license.qlikcloud.com/v1/definitions/signed": net/http: invalid header field value for "Authorization"

Resolution

This error occurs when the license code is copied with line break characters. Those are considered as part of the license, invalidating the code.

To resolve the problem, copy the license code in a text file editor and manually remove the line break characters. Then copy the correctly formatted string to activate the license. 

When removing the line breaks, verify that no other characters are deleted.

Example of an incorrectly and correctly formatted key:

Environment

• QlikView all versions

As a License Token is only valid for 90 days after it was created, it is renewed automatically by Talend Administration Center, except if Qlik Talend Administration Center is not connected or cannot access the Qlik Talend Token Site.

You will be experiencing a situation where the License Token will not automatically renew in the Qlk Talend Administration Center.

Resolution

• For the Qlik Talend Administration Center License Token to automatically renew, you must have internet access. Check if you faced any internet connection issues during that time. 
  If your Qlik Talend Administration Center does not have outside internet access, the manual validation will need to be done every 90 days: Generating a validation request | Qlik Talend Help
• Verify your proxy settings; the proxy should not block the connection to the license token validation server (https://www.talend.com/api/get_tis_validation_token_form.php). See: Proxy and firewall allowlist information| Qlik Talend Help.

  Port 443 is the port to access the license token validation server.

• Contact our Customer Support in order to check the expiration date of your Qlik Talend Administration Center License Token. See: Support.
• If you are using a patch before the TPS-5612, it would be advised to move to a patch TPS-5612 or later.
  
  There has been a following fix for the "License token will expire in x days" alert message in TPS-5612 patch.
  
  The alert message shows starting from 10 days before the license tokenexpiration date, and the license token will try to automatically renew once everyday in the 10 days. However, if there are Internet connectivity issues during this time, the license token will not renew automatically.
  In order for the license token to automatically renew, we have implemented a feature for the license to try to renew again upon failure every day. (The license token will try to renew check per day, once it failed and will do it again).
  
  Please see the following document for details: TPS-5612 (cumulative patch) | Qlik Talend Help.
  
  
• If you already owned a license that has been reactivated by Qlik Talend after renewal, you may have to validate it manually from the Qlik Talend Administration Center web application: How to validate a license after renewal| Qlik Talend Help.

For more information about how to clear the Qlik Talend Administration Center cache, refer to How to clear the Talend Administration Center (TAC) cache.

Cause 

There are two potential causes:

• Qlik Talend Administration Center has experienced a connectivity problem with the License Token server.
• The License Token has not yet expired.

Related Content

For more information about how to clear Talend Administration Center Cache, please refer to this official article:

Qlik Community: How-to-clear-the-Talend-Administration-Center-TAC-cache

Environment

Talend Administration Center 

You are a prospective customer and are looking to purchase a Qlik Cloud subscription.

• See How to purchase Qlik Sense SaaS digital subscription.
• If you are looking to manage an active subscription, see Managing Your Subscription in My Qlik.

You are a prospective customer, having never purchased Qlik licenses before and are interested in learning more about Qlik products and making a purchase:

• Go to Qlik.com to browse our available offerings and engage in our Live Chat if you have questions.
• Or contact Sales directly.

You are an existing Customer, having previously purchased a license directly from Qlik and wish to purchase additional licenses or CALs:

• Please contact your Account Manager. If you are unsure who the Account Manager is for your company, contact Support using Live Chat.

You are an existing Customer and purchased your licenses through a third party (not directly from Qlik) and wish to purchase additional licenses or CALs:

• Please contact your Responsible Partner from which you previously purchased licenses. If you are unsure who your Responsible Partner is, contact Support using Live Chat.

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