You can manage your Qlik Sense Business subscription in My Qlik, including renewing your subscription, reducing the number of paid seats in your tenant, and cancelling your subscription.

If you are looking to manage your Enterprise SaaS subscription, please contact your account manager or your local Qlik Sales team.

Table of Content

• To access your subscription
• Manage Payment Method and Billing Information
• Managing the Number of Paid Seats
• Undoing the Seat Reduction
• Cancelling a Subscription
• Undoing the Cancellation

To access your subscription

1. Go directly to account.myqlik.qlik.com and log in
   
   or 
   
   Open My Qlik from your tenant after logging in
   
   
   
   
2. Choose the subscription or product you intend to modify from the provided list
   
   

Manage Payment Method and Billing Information

You can manage your Payment and Billing information for your subscription.

1. In your Account overview, click the ellipses (...)
2. Click Payment & billing 
   
   
   
   
   
   
3. Manage your Payment Methods 
   
   
   
   

Managing the Number of Paid Seats

You can increase and reduce the number of users in your Qlik Sense Business subscription using My Qlik. You can also choose to undo the reduction in users any time before the new term begins.

NOTE: The subscription is not reduced to the new number of seats until the beginning of the
next subscription term. You will continue to have the same number of seats available until the end of your current subscription term.

1. Choose the subscription and product you wish to manage.
2. Click the Manage button.
   
   
   
   
3. Click Add Seats or Reducate Seats  
   
   NOTE: You cannot reduce the number of seats below the number of active users in the tenant.
   
   
   
   

4. Follow the onscreen instructions. 
   

Undoing the Seat Reduction

If you decide that you do not want to reduce the number of seats, you can undo the request any time before the new term.

1. Click Undo Request in your subscription overview
   
   
   
   
2. Check I understand and click Confirm. 
   
   The subscription tile updates to reflect the original number of seats.

Cancelling a Subscription

Qlik Sense Business subscription at any time using My Qlik. You can also choose to undo the cancellation any time before the end of the term.

NOTE: The cancellation becomes effective at the end of your subscription term. You will
continue to have access to your subscription until the end of the term.

1. Choose the subscription and product you wish to manage.
2. Click the Manage button.
   
   
   
   
3. Click Cancel Subscription 
   
   
   
   

4. Follow the on-screen instructions. 
   
   The subscription tile updates to reflect the cancellation request and displays the date on which the cancellation becomes effective.

Undoing the Cancellation

If you decide that you do not want to cancel the subscription, you can undo the request any time before the end of the term.

1. Click Undo Request in your subscription overview
   
   
   

    

2. Check I understand and click Confirm. 

After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.

1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 
   
   
   • May 2023 Patch 13
   • August 2023 Patch 10
   • November 2023 Patch 4 
   • February 2024 IR
     
2. Back up the following files:
   
   
   • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
     
     *where C:\Program Files can be replaced by your custom installation path.
     
     
3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
   
4. Open and edit the capabilities.json with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   2. Locate: "enabled": true,"flag": "QMCShowAppSize"
   3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
   4. Save the file  
5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   2. Locate: </appSettings>
   3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
   4. Save
6. Start all Qlik Sense services
7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

Internal Investigation:

QB-22795
QB-24301

Environment

Qlik Sense Enterprise on Windows  May 2023, August 2023, November 2023, February 2024. 

If a tenant previously had an incomplete SMTP configuration with their Qlik Cloud, an error message will now be shown to the Tenant Administrator:

• Your email providers is not working – Go to Settings 

Resolution

To resolve this error a Tenant Admin can enter valid SMTP credentials. 

At the moment, it is not possible to delete/clear the previous credential entry in the authentication.  An option to clear the credentials is being prepared to support a return to a default (non-configured/empty) state and is expected to be available in the coming weeks.

We will update this article when the ability to clear becomes available. 

Example SMTP Error

Cause 

With the release of the SMTP service connectivity for Microsoft O365 from the Management Console, more stringent error checking was added to the basic authentication configuration. 

Related Content 

If interested, Admins can still successfully connect to Microsoft 0365 SMTP with this error showing. More details on the new available 0Auth2 authentication can be found here: Qlik Cloud: Introducing OAuth2 authentication for ... - Qlik Community - 2444243

Internal Investigation ID

• QB-26792

Environment

• Qlik Cloud

There are problems occurring when there are multiple TACs running.

Cause

The issue may arise due to the TACs sharing the same port, resulting in conflicts between them.

Resolution

1. Check if the problem occurs when you are running only one TAC.
   If there are no issues when running only one TAC, it is highly likely that the issue is not related to Talend's product. There may be issues with the architecture, which is beyond the scope of Qlik's technical support team. Please consult with our Sales team or CSM (Customer Success Manager) team.
2. Do you have multiple TACs running on the same server or environment?
   It is not recommended to have multiple TACs running on the same server or environment, as it may cause issues.
3. If you have an HA setup, please check that the HA setup is configured correctly.
   For further details, please refer to the documentation: Setting up High Availability.

Environment

• Talend Administration Center 7.3.1, 8.0.1

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.

Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.

Index

• Supported Scenarios
• Upgrades
• New installs
• Requirements
• Known limitations
• Installing anew Qlik Sense Repository Database using PostgreSQL
• Qlik PostgreSQL Installer - Download Link
• Upgrading an existing Qlik Sense Repository Database
• The Upgrade
• Next Steps and Compatibility with PostgreSQL installers
• How do I upgrade PostgreSQL from here on?
• Troubleshooting and FAQ
• Related Content

Video Walkthrough

Video chapters:

• 01:02 - Intro to PostgreSQL Repository
• 02:51 – Prerequisites
• 03:24 - What is the QPI tool?
• 05:09 - Using the QPI tool
• 09:27 - Removing the old Database Service
• 11:27 - Upgrading a stand-alone to the latest release
• 13:39 - How to roll-back to the previous version
• 14:46 - Troubleshooting upgrading a patched version
• 18:25 - Troubleshooting upgrade security error
• 21:15 - Additional config file settings

Supported Scenarios

Upgrades

The following versions have been tested and verified to work with QPI (1.4.0): 

Qlik Sense February 2022 to Qlik Sense November 2023.

If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.

New installs

The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.

Requirements

• Review the QPI Release Notes before you continue

• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:

  • Uninstall all patches before using QPI (see Installing and Uninstalling Qlik Sense Patches) or
  • Upgrade to an IR release of Qlik Sense which supports QPI

• The PostgreSQL Installer can only upgrade bundled PostgreSQL database listening on the default port 4432.
• The user who runs the installer must be an administrator.
• The backup destination must have sufficient free disk space to dump the existing database  
• The backup destination must not be a network path or virtual storage folder. It is recommended the backup is stored on the main drive. 
• There will be downtime during this operation, please plan accordingly
• If upgrading to PostgreSQL 14 and later, the Windows OS must be at least Server 2016

Known limitations

• Cannot migrate a 14.8 embedded database to a standalone
• Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• The installer itself does not provide an automatic rollback feature.

Installing a new Qlik Sense Repository Database using PostgreSQL

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, default: C:\Program Files\PostgreSQL\14

   Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

7. Set the database data folder, default: C:\Program Files\PostgreSQL\14\data

   Do not  use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer Release Notes

Upgrading an existing Qlik Sense Repository Database

The following versions have been tested and verified to work with QPI (1.4.0): 

February 2022 to November 2023.

If you are on any version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade.  From Qlik Sense August 2023 a 9.6 update is blocked.

The Upgrade

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    The review screen lists the settings which will be migrated. No manual changes are required post-upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-14 service. Do not rename this service. 
    
    
    

     

13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected. The original database folder in C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
    

     

16. Uninstall the old Qlik Sense Repository Database service.

    This step is required. Failing to remove the old service will lead the upgrade or patching issues.

    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the appropriate msi file.
       
       
       
       If you were running 9.6 before the upgrade, search PostgreSQL.msi
       If you were running 12.5 before the upgrade, search PostgreSQL125.msi
       
       
    3. The msi will be revealed.
       
       
    4. Right-click the msi file and select uninstall from the menu.
       
       
       
       
    
    
17. Re-install the PostgreSQL binaries. This step is optional if Qlik Sense is immediately upgraded following the use of QPI. The Sense upgrade will install the correct binaries automatically. 
    

    Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts. 

    If you do not immediately upgrade:
    
    
    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the .msi file appropriate for your currently installed Qlik Sense version
       
       
       
       For Qlik Sense August 2023 and later: PostgreSQL14.msi
       Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
       
       
    3. Right-click the file
    4. Click Open file location
       
       
       
       
    5. Highlight the file path, right-click on the path, and click Copy
       
       
       
       
    6. Open a Windows Command prompt as administrator
       
       
    7. Navigate to the location of the folder you copied
       
       Example command line: 
       
       cd C:\ProgramData\Package Cache\{GUID}
       
       Where GUID is the value of the folder name.
       
       
    8. Run the following command depending on the version you have installed: 
       
       Qlik Sense August 2023 and later
       
       msiexec.exe /qb /i "PostgreSQL14.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       Qlik Sense February 2022 to May 2023
       
       msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       This will re-install the binaries without installing a database. If you installed with a custom directory adjust the INSTALLDIR parameter accordingly. E.g. you installed in D:\Qlik\Sense then the parameter would be INSTALLDIR="D:\Qlik\Sense".
       
       
18. Finalize the process by updating the references to the PostgreSQL binaries paths in the SetupDatabase.ps1 and Configure-Service.ps1 files. For detailed steps, see Cannot change the qliksenserepository password for microservices of the service dispatcher: The system cannot find the file specified.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Next Steps and Compatibility with PostgreSQL installers

Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.

Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads. 

How do I upgrade PostgreSQL from here on?

See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.

Troubleshooting and FAQ

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\X.X
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-XX service.

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. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

Related Content

Qlik PostgreSQL installer version 1.3.0 Release Notes  
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades 

Prerequisites

• Since December 2020 Qlik Web Connectors requires .NET Framework 4.7.2.
• Windows 8.1 or later and Windows Server 2012 and later. Note: Running Qlik Web Connectors as a service is only supported on Windows Server editions.
• A modern browser, Qlik Web Connectors should run on IE9 and later, Chrome, Firefox and Apple Safari 6.1 and later. In general, expect the same browsers supported by QlikView / Qlik Sense
• Qlik Web Connectors should currently work with any supported version of QlikView or Qlik Sense If you are using Qlik Sense please make sure you read this page. 
• Note, for all of the connectors available so far (excluding MongoDB and the General Web Connector if connecting to an internal web service), Qlik Web Connectors requires connection to the internet in order to download data from whichever API you are interested in. A personal or corporate firewall may prevent access to the API(s), however some settings might help you configure this, see Qlik Connectors Web Package - an introduction for Enterprise Users?

Installing & Running Qlik Web Connectors

NOTE: These instructions are for running Qlik Web Connectors in 'desktop' mode which is the recommended mode when you start using the product for the first time.
For instructions on running Qlik Web Connectors on a server (so that it is always up and available) see Setting Up The Qlik Web Connectors Windows Service.
 

Troubleshooting

For troubleshooting, see:

• Qlik Web Connectors Troubleshooting Guide
• Troubleshooting Qlik Web Connectors

Installing Qlik Web Connectors

The following steps show how to run Qlik Web Connectors in localhost mode only with no authentication. See the deploy.config section in Qlik Connectors Web Package - Advanced Config With deploy.config on how to open up remote access and authentication.

Qlik Connectors Web Package is delivered as a zipped folder, there is no installer and Qlik Connectors Web Package installs no additional components on your systems. This makes it very small, lightweight and trivial to 'install' or remove.

To allow for easy upgrading, we suggest taking the following approach.

• Read Unblocking the Qlik Connectors Web Package zip distribution regarding unblocking the downloaded files contained in the zip, particularly if you have followed these instructions once and are experiencing issues.
• In a root drive, create a folder called 'Qlik Web Connectors' (e.g. c:\QlikWebConnectors. We would specifically not recommend placing it under 'Program Files' due to the reasons mentioned in the notes on the page above. Also, please do not run the program from a shared network drive or mapped folder you might experience issues.
• Unzip the Qlik Web Connectors folder that you have downloaded.
• Copy the contents of the unzipped folder to your new Qlik Web Connectors folder

You should now have a folder structure that looks something like this:

• You can now run the Qlik WebConnectors.exe file.

Note also that if you are using the processParams[Sync|Async|Batch|Auto] parameter in any of your load scripts you will need to ensure that QlikView/Qlik Sense AND Qlik Connectors Web Package have access to a folder where QlikView/Qlik Sense can store intermediate CSV parameter files and Qlik Connectors Web Package can read them (typically c:\QlikWebConnectors\Temp). This is explained fully on Qlik Connectors Web Package Synchronous, Asynchronous and Batch Requests Explained.

If you experience any issues running Qlik Connectors Web Package we would recommend ensuring that you are running it as an administrator - this is done on Windows 7 and other Windows versions by right clicking on the executable and selecting the option highlighted below. You may only need to run Qlik Connectors Web Package the first time as admin so that it can reserve the URL it runs on, although this will probably only be necessary when you start using more advanced configurations (see Qlik Connectors Web Package - Advanced Config With deploy.config).
 

You should now see the following window appear indicating that Qlik Connectors Web Package is running.

PLEASE NOTE : The exe should be run from your local hard drive - if you run the program from a shared network drive or mapped folder you might experience issues.
Qlik Connectors Web Package runs as a small webserver, by default on port 5555. If you minimize the window shown above you will see this indicated by the balloon tip and icon in the status bar.

This port can be easily changed using deploy.config (explained below). In most cases this should not be necessary, if you do alter this be sure to restart Qlik Connectors Web Package.

You can now click the 'open in default browser' link to view the Qlik Connectors Web Package Web UI.


 

Startup Log Files

Note, at this point, Qlik Connectors Web Package should have generated either 'Startup_Log.txt' or 'Service_Startup_Log.txt' (if running as windows service) in the root folder. If you are experiencing any issues starting Qlik Connectors Web Package, please first check the contents of this log file. We would also recommend you send it if you are contacting us for support about this.

Installing the Licence File

You should now see something like the following in your default browser, note that the connectors are not licensed:

Rewrite for Qlik Connectors Web Package

?You should go to the 'Licence' tab in QlikWebConnectors and:

• Enter the name you used when registering the license number were given when purchasing Qlik Web Connectors.

• Click the " Apply new LEF" button.

Verify the LEF details are applied correctly, including the connectors covered by your subscription.
It's also usually a good idea at this point to check the 'data endpoint' is up and running by browsing to:
http://localhost:5555/web

Which should show something like:

You can also request this as XML by appending ?format=xml to the url::
http://localhost:5555/web?format=xml

This also gives you a way of checking that Qlik Connectors Web Package is running correctly, is licensed and has the expected minimum version number from your QlikView or Qlik Sense load script before proceeding with the reminder of the load - you can see an example here: Checking the status of Qlik Connectors Web Package. Note that the above path will be different if you are accessing the Qlik Web Connectors server from another machine (see above article).

Using a specific connector

Selecting a Connector

On the 'Connectors' tab, select a connector you wish to use and click it to bring up its configuration form. In this example we use the Twitter Connector.

Each connector should have a link to an associated help page on its 'Support' tab:

Note that at present, most of the connector help pages will still have screen shots of the Qlik Web Connectors  WinForms edition. However, the connectors are 99% identical in both editions in terms of available tables, input parameters and behavior so the information on the help pages is still relevant.

Working With A Connector

Each connector will have a list of tables which it supports, underneath which appears a description for the currently selected table:

Some connectors will also have tables grouped into particular categories for easier discovery:

In this example we will select the Twitter Search table:

Click on Parameters button.
Next click the 'Authenticate' button:

A new browser window or tab should now open where you authenticate with Twitter. 

Please ensure that your browser will allow Pop-Ups for the purpose of authenticating.
Once you have done this you should receive a code which you should copy:

And paste back in to the connector: Use the code you provided. The code in the image does not match with the above code.

You should find you now have an authentication token saved with your settings and are able to enter some parameters for the table.
You can now copy and paste the generated load script into your QlikView or Qlik Sense application:

 

Common Connector Configuration

Each connector has its own 'Settings' tab. This is where you can delete any settings associated with the connector (i.e. input parameters saved in the table's UI) as well as clear any cached data (a small number of connectors cache some data to improve performance and/or minimize API calls).

Change Log

Each connector should also have a change log where you can see changes made over each version. We would recommend you read this each time you upgrade Qlik Connectors Web Package.

 

Upgrading

Upgrading Qlik Connectors Web Package is relatively easy, but by following some simple steps you'll be able to continue using any data which connectors may have cached, as well as continue using your existing connector settings.

IMPORTANT: Please note however that you should read the change logs for Qlik Connectors Web Package as well as any connectors you are using. In particular because, very occasionally due to API changes out of our control, we have to introduce breaking changes which might affect your QlikView or Qlik Sense applications. Therefore it is important to check the change logs for any items which might apply to you and update your applications and test where necessary.

• Stop running Qlik Connectors Web Package (note - if you are running Qlik Connectors Web Package as a service you should stop the service).
• Take a back up of your Qlik Web Connector WebEdition folder, which you created, by zipping it up and keeping it somewhere safe.
• On downloading the latest version of Qlik Connectors Web Package, you will have received a zip file - unzip this file somewhere. Note you should also unblock this file (Unblocking the Qlik Connectors Web Package zip distribution).
• Copy and paste its contents into the Qlik Web Connector WebEdition folder (i.e. over the top of the existing contents which you have just backed up) EXCLUDING the deploy.config and logins.xml files.
• IMPORTANT - Because you have likely edited both deploy.config and logins.xml, you will want to retain these settings rather than overwriting them with the 'master version from the latest download. You therefore have two options (and we hope to improve this situation in time):
  • 1) [Recommended] Copy across your just backed up versions of deploy.config and logins.xml into your Qlik Web Connector WebEdition directory and then check the deploy.config and logins.xml files from the latest download zip and add any additional elements which may have been made (which should happen rarely).
    OR
  • 2) Also copy the deploy.config and logins.xml files from the latest download over your existing files AND THEN manually copy any changes you had made to these files from the just backed up version of your site.
• When prompted overwrite all files and folders. NOTE - It has been seen very occasionally that when you unzip Qlik Connectors Web Package (or any zip for that matter) to your machine the files/folders sometimes do not pick up or inherit the correct users/permissions which might result in a WinIOError when you try to run Qlik Web Connector. You should check that your user account and/or whichever user account you have configured to run Qlik Connectors Web Package still has full access to this folder.
• Your cached data in the \Qlik Web Connector WebEdition\App_Data folder should still be there. If it's not, go to your backed up zip file and copy its App_Data folder's contents into your 'live' App_Data folder.
• Start Qlik Connectors Web Package again (note - if you are running Qlik Connectors Web Package as a service you should re-start the service).

Running Qlik Connectors Web Package As A Service

You can setup Qlik Connectors Web Package to run as a windows service, see Setting up the Qlik Connectors Web Package Windows Service. This is the recommended method when using in conjunction with a QlikView or Qlik Sense server as it will ensure Qlik Connectors Web Package is always up and running to provide data to the QlikView or Qlik Sense reloads.
 

Advanced Usage

This page explains how to run Qlik Connectors Web Package in localhost mode only with no authentication. You can also configure Qlik Connectors Web Package to run on a server and be accessible other machines. Please see the deploy.config section, Qlik Connectors Web Package - Advanced . Config With deploy.config for further details.

Qlik Connectors Web Package also has some enterprise features which help users further secure their Qlik Connectors Web Package installation, see Qlik Connectors Web Package - an introduction for Enterprise Users

Support & Troubleshooting

If you are having trouble getting Qlik Connectors Web Package running, first ensure you have carefully read the above page and then consulted the troubleshooting page, Troubleshooting Qlik Connectors Web Package

If you are still experiencing issues we recommend submitting a support request.

When embedding a sheet in an iFrame, the "full screen" toggle button for Qlik Sense native chart objects is missing. This feature is present at the sheet level in the hub

Full Screen toggle button is available at the sheet level in the hub

The same feature is  missing, once a sheet is added in an iFrame (Single Configurator)

Environment

• Qlik Sense Enterprise (all versions)

Resolution

This is a known limitation.

An improvement task has been created (Jira task VIZ-103)

Internal Investigation ID(s):

QB-4967
VIZ-103

Qlik Sense Enterprise on Windows is expected to only keep a certain number of script logs per app. This works as intended to avoid filling up disk space over time and to optimize Qlik Sense Repository performance. 
 
In older releases an inconsistency has been observed, where script logs are not always deleted as expected. This has since then been address (QLIK-86228).


Environments:

• Qlik Sense Enterprise on Windows all versions

This behavior is controlled by the setting "MinNumberOfExecutionResultsToKeepPerTask" (from Qlik Sense February 2019 and up) or "ExecutionResultsAmountKept"  (all prior versions) located in the Repository.exe.config file (By default, the Repository.exe.config file can be found in C:\Program Files\Qlik\Sense\Repository\ on your Qlik Sense machine.).

However, this is highly discouraged to change the default setting without being instructed to do so by Qlik Support as this may cause severe performance issues for the whole system.

The reason for that is that a reference to each of the existing script logs is stored in the Qlik Sense repository and increasing the number of logs kept will increase the size of the repository and decrease the Qlik Sense system global performance.

By default "MinNumberOfExecutionResultsToKeepPerTask" has a value of 3, which means that:

• It will keep for each App a maximum of 3 old logs and the latest log (Totally 4 script logs)
• The first cleaning will occur on the 9th reload of the App (MinNumberOfExecutionResultsToKeepPerTask x 3) and will remove the 5 oldest logs, leaving 4 logs. After that, always 4 logs will be kept.

NOTE: In the most recent version, you may not have the row 'ExecutionResultsAmountKept', but should have a new one: MinNumberOfExecutionResultsToKeepPerTask

Recommended workaround to keep older logs

The currently recommended workaround to keep the older logs is to use a third-party script (.bat script or else) to move the logs to another folder before they actually get deleted. Below is an example of how this could be done:

robocopy \\<domain>\QlikShare\ArchivedLogs\<FQDN_OF_RELOAD_NODE_1>\Script C:\AuditLogs\<FQDN_OF_RELOAD_NODE_1> /E /XC /XN /XO
robocopy \\<domain>\QlikShare\ArchivedLogs\<FQDN_OF_RELOAD_NODE_2>\Script C:\AuditLogs\<FQDN_OF_RELOAD_NODE_2> /E /XC /XN /XO

The frequency you should run this script it based on how frequently you reload your tasks.

When deploying a Data Service Job containing a tRest component to Talend Runtime from TMC, osgi service gives  error:

LinkageError :  loader constraint violation for class when selecting overriding method javax.ws.rs.core.Response per tRest.the log displays the following error messages.

The Job design appears as follows:

tRestRequest --> xxx --> tRest --> xxxx --> tRestResponse

The detailed error messages in the log:

2024-11-07T14:09:40,762 | ERROR | features-2-thread-1 | container.BlueprintContainerImpl 460 | 85 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle talenddev.Job_P2PO_ESB_SuperviserDetailsAdhoc_v5/0.1.10

org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to instantiate components

at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:741) ~[?:?]

Caused by: java.lang.LinkageError: loader constraint violation for class talenddev.job_p2po_esb_superviserdetailsadhoc_v5_0_1.Job_P2PO_ESB_SuperviserDetailsAdhoc_v5$ExceptionMapper4TalendJobRestService: when selecting overriding method 'javax.ws.rs.core.Response talenddev.job_p2po_esb_superviserdetailsadhoc_v5_0_1.Job_P2PO_ESB_SuperviserDetailsAdhoc_v5$ExceptionMapper4TalendJobRestService.toResponse(javax.ws.rs.WebApplicationException)' the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @284cb81 of the selected method's type 

Cause

According to the documentation of the tRest component, Talend Runtime does not support this component from a design perspective.

Resolution 

To build Jobs that need to be deployed into the Talend Runtime, it is recommended to use the tRESTClient component which is best suited for the Talend Runtime, even though the tRest component is working fine prior to v801-R2024-05.

For more information about the tRESTClient component, see tRESTClient.

Environment

• Talend ESB 8.0.1

With the introduction of third-party ODBC connectors for Direct Access Gateway, the stability of the Data Gateway can be impacted if no Data Preview limit is added during the configuration step. 

The section to verify under each connection would be "SELECT statement template for Data Preview".

Each driver has a specific syntax. Qlik provides some examples of connection strings in Sample connection strings and syntax.

Resolution

Verify that all the data connections have a limit configured in the data preview for ODBC Generic driver connections under "SELECT statement template for Data Preview" as documented in Database specific properties.

A PowerShell sample is attached to this article to extract these details. Running the script will generate a CSV file with a column named rowsLimitKeyword_Custom. Review every syntax to contain a type of limit (this can change for each data source, some common words are LIMIT, TOP, etc.). 

API endpoint https://qlik.dev/apis/rest/data-connections/

https://<tenant>/api/v1/data-connections?noDatafiles=true&filter=datasourceID eq "DG_GenericDriver"

We suggest using a separate server for development activities in general, highly recommended for customers using third-party drivers as those can cause abnormal/unexpected behaviors outside of our control.

Cause

Long-running commands can cause a bottleneck in the Data Gateway, an improvement for this is planned on Direct Access Gateway 1.7.0, but we recommend to verify the configuration of data connections at all times regardless. 

DirectAccess log will show the duration of the commands, for example:

"CommandDurationMs":340734.958,"Method":"post","Url":"http://localhost:5050/metadata/proxyCommand"

Internal Investigation ID(s)

QB-28905

Environment

• Qlik Cloud

The Qlik Sense Engine allows for a Hard Max Limit to be set on memory consumption. This setting requires that the Operating System is configured to support this, as described in the SetProcessWorkingSetSizeEx documentation (QUOTA_LIMITS_HARDWS_MAX_ENABLE parameter).

Before using the Hard Max Limit, familiarize yourself with Microsoft's memory management:

Source: learn.microsoft.com

By default, using the SetProcessWorkingSetSize function to set an application's minimum and maximum working set sizes does not guarantee that the requested memory will be reserved, or that it will remain resident at all times. When an application is idle, or a low-memory situation causes a demand for memory, the operating system can reduce the application's working set below its minimum working set limit. If memory is abundant, the system might allow an application to exceed its maximum working set limit.

The QUOTA_LIMITS_HARDWS_MIN_ENABLE and QUOTA_LIMITS_HARDWS_MAX_ENABLE flags enable you to ensure that limits are enforced.

When you increase the working set size of an application, you are taking away physical memory from the rest of the system. This can degrade the performance of other applications and the system as a whole. It can also lead to failures of operations that require physical memory to be present (for example, creating processes, threads, and kernel pool). Thus, you must use the SetProcessWorkingSetSize function carefully. You must always consider the performance of the whole system when you are designing an application.

How to review your memory settings in Qlik Sense or configure the Hard Max Limit:

After enabling QUOTA_LIMITS_HARDWS_MAX_ENABLE as per Microsoft's guidelines:

1. Open the Qlik Sense Management Console in a supported browser
2. Navigate to Engines in the Management Console and select your engine
   
   
   
   
3. Expand the Advanced settings from the menu to the right
   
   
   
   
4. Review your memory settings and verify that Max Max Limit is selected
   
   

See Editing an engine - Qlik Sense for administrators for details.

To note:

Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).

This is down to how the Qlik Sense Engine memory limit will be defined based on the total memory available.

Example:

• A server has 10 GB of memory in total, and the Max memory usage (%) is set to 90%.
• This will allow the process engine.exe to use 9 GB of memory. 
• Another application or process may at that point already be consuming 5 GB memory, and this will cause an overload of the system if the engine is set to use 9 GB. 
• The engine.exe will not be able to respect other services

The memory working setting limit is not a hard limit to set on the engine. This is a setting which determines how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters. 

Internal Investigation IDs:

QLIK-96872

A Talend Rest Job is sending a request to a secure REST web service through Jersey client and it was running fine in an older version. When running the same job  in a newer talend version, it is getting error Exception in component

tREST_1 javax.ws.rs.ProcessingException: Already connected at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:312) 

Resolution

It is recommended you should use talend tHTTPClient component as a replacement over tRest/tRESTClient component in job design.

tHttpClient component is available only when you have installed the 8.0.1-R2023-05 Talend Studio monthly update or a later one delivered by Talend. For more information, check with your administrator.

Cause

The root cause comes from a known bug in Jersey client and it is list below without robust fix:

https://github.com/eclipse-ee4j/jersey/issues/3000

https://github.com/eclipse-ee4j/jersey/issues/3001

Related Content

javax-ws-rs-processingexception-while-sending-request-through-jersey

Environment

Talend Studio 

When changing the name of a dataset, the source name still stays the same. This can be seen by uploading a  “firstname.qvd" and renaming it to “secondname.qvd”. 

The dataset's detail will show "firstname.qvd" as the source.

As a consequence:

1. you can have several datasets with the same name, but different sourcenames.
2. the data load editor always refers to the source name (“firstname”), not the data set name. 
   
   
   

   
   Trying to load  “FROM [lib://DataFiles/secondname.qvd]” will produce a "(Connector error: File not found)" error.

Resolution

This is not a defect, it's how the product is designed.

A dataset represents a data resource with its properties such as name. The value of that is that you are able to use more user-friendly names of datasets without having to change the source names, which can be useful when the dataset is pointing to a database table for instance.

In the future, there is a plan to add the possibility of calling the name of the datasets in the script. 

Environment

Qlik Cloud 

To help Qlik customers manage costs more effectively, Qlik has developed the Qlik Snowflake Monitoring application, designed to provide invaluable insights about your Snowflake costs, usage, inventory, security, performance and contract utilization. This app utilizes Qlik's Associative Engine to connect directly to your Snowflake instance and reveal insights from Snowflake's detailed metadata, offering valuable information that traditional query-based tools and Snowflake's own reports are unable to provide.

Leveraging Qlik Application Automation, and Data Alerts, you can:

• Install* & update the app with a fully guided, click-through installer, using an out-of-the-box Qlik Application Automation template.
• Get alerted when new versions of the Snowflake Monitor are available using Data Alerts.

*Minor configuration is required on first run to create the required data connections.

Content:

• Part One: 'Qlik Snowflake Monitoring App Installer' templateoverview
• Features
• Note on manual install
• Part Two: Creating and setting up analytics data connections
• Snowflake connection
• Note on Snowflake authentication
• REST connection to repository
• Note on update compatibility
• Part Three: Set up a Data Alert to notify when a new version of the app is available
• Summary

Part One: 'Qlik Snowflake Monitoring App Installer' template overview

This automation template is a fully guided installer/updater for the Qlik Snowflake Monitor. Leverage this automation template to easily install and update this application. The application itself is community-supported; and it is provided through Qlik’s Open-Source Software GitHub and thus is subject to Qlik’s open-source guidelines & policies.

For more information, refer to the GitHub Repository.

Features

• Easy app installation and updates
• Create new spaces or use existing spaces
• Automatic setup of settings, roles, and permissions
• Always installs the newest version from Qlik's OSS GitHub
• Tags apps to easily track installations and versions
• Works with both user and capacity-based subscriptions
• Compatible with all Snowflake tenant levels

Note on manual install

If the monitoring app was installed manually (i.e. not through the application automation installer), then the app will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring application and check their versions. This is because the application is tagged with ‘QCS - QSM - {App Name}’ and ‘QCS – QSM - {Version}’ during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

Part Two: Creating and setting up analytics data connections

The Qlik Snowflake Monitor requires two connections, one to your Snowflake instance to feed the data for your analytics, and one REST connection to the qlik-oss repository to run a version check on the monitor.

Snowflake connection

You will need to create a custom User, Role and Warehouse on your snowflake tenant. This is to ensure this user and role can see the monitoring details and can be monitored.

1. Update the credentials in the SQL script from GitHub 
2. Run the SQL as ‘ACCOUNTADMIN’ from your Snowflake tenant to create a warehouse to retrieve the relevant data. Make sure you change the password and store this securely.
3. Create a snowflake data connection in the Qlik analytics space into which the application was deployed, using the following details:
   
   
   • Server: The full hostname for the Snowflake account, not prefixed with http:// or https://
   • Port: Leave as default unless it needs changing.
   • Database: SNOWFLAKE
   • Schema: ACCOUNT_USAGE
   • Warehouse: QLIK_MONITORING_WH
   • Role: QLIK_MONITORING_ROLE
     
     

   For Authentication, this setup is defaulted to username & password.

   • Username: QLIK_MONITORING
   • Password: As specified in your configuration above
     
     

   Finally, you need to name the connection as follows:

   • Connection Name: SNOWFLAKE_MONITORING_DATA
     
     
   
   

    

Note on Snowflake authentication

If you wish to use an alternative authentication method, please follow the documentation accordingly on both Snowflake & Qlik.

REST connection to repository

The REST connection is used to fetch version details from the GitHub repository. On reload it will look for the the latest released version in github and check this against the version you have installed. You can later use this in ‘Part Three’ to create an alert when updates to the application are available. To create a REST connection the following information is required:

• URL: https://raw.githubusercontent.com/qlik-oss/qlik-snowflake-monitor/main/manifest.json 
• METHOD: GET
• Allow “WITH CONNECTION”: Enabled
• Connection Name: REST Monitoring Versioning API
  
  
  
  

Once these two connections have been set up, you can reload the application. The application has been created to accommodate Snowflake tenants of all sizes. If you have a small tenant, you will find the initial run of the load script can take around 30 minutes, and for larger tenants this can be over an hour or two. Subsequent runs will utilize cached QVDs that update daily to reduce reload times each subsequent day.

Note on update compatibility

If a new release of the application is made, occasionally a full reload of data is required, but generally, if the data schema is unchanged the existing QVDs will be maintained. This is through the use of versions in the names of the QVDs used to store the data.

Part Three: Set up a Data Alert to notify when a new version of the app is available

The application has the following two variables:

• vLatestVersion: The latest version of the app released on Qlik’s OSS GitHub.
• vIsLatestVersion: A Boolean of whether the app’s current version is equal to the latest version of the app released on Qlik’s OSS GitHub (1 if true, 0 if false).

To create a new Data Alert for updates to the monitoring app, follow these steps:

1. Right-click on a chart in the app, select Alerts and then Create new alert.
2. Clear out the defaults and provide the alert with a name such as Qlik Snowflake Monitor Update Available.
3. Select Add measure and select the fx icon to enter a custom expression. Enter the expression ’$(vLatestVersion)'. Ensure it is wrapped in single quotes, then provide the label for the expression Latest Version.
4. Select Add measure and select the fx icon to enter a custom expression. Enter the expression $(vIsLatestVersion), then provide the label for the expression Is Latest Version.
5. Confirm the Details & data tab resembles the following:
   
   
   
   
6. Navigate to the next tab, Conditions.
7. Set the Measure to Is Latest Version, the Operator to Equal to, and the Value to 0. This way, if the app is not the latest version (0), it will trigger the alert.
8. Confirm that the Conditions tab resembles the following:
   
   

   

6. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

Summary

The Qlik Snowflake Monitor can be easily installed by following these steps above. If you wish to find out more, check out this Ometis blog post and this Ometis Webinar to get a run through of the analytics this application can offer.

If you face any issues, please use the GitHub and raise an issue through the repository.

The AS/400 supports a file concept known as multiple-member files, in which one file (or table) can possess several different members. Each member is a part of the same file or table and shares the same schema, but the members are uniquely named and have unique data. Just like a partition tables in other regular RDBMS eg in Oracle, MySQL etc.

ODBC and OLE DB have no built-in mechanism for accessing multiple members. By default, ODBC always accesses the first member in a multimember file. This is the known limitation in Replicate User Guide: • Multi-member (Partitioned) tables are not supported.

To enable ODBC-based applications such as Data Transformation Services (DTS) to access multiple-member files, we need to use the AS/400's SQL ALIAS statement. The ALIAS statement lets you create an alias for each member we need to access. We use ALIAS to access all members in Qlik Replicate full load stage. More samples Creating and using ALIAS names.

However, all member data changes will be recorded into DB400 Journal file, Qlik Replicate can capture all members changes. No special settings needed in Qlik Replicate CDC stage.

This article describe how to overcome the limitation and setup Replicate task to replicate Multi-Member Tables.

Resolution

1. Create ALIAS for all member of the multi-member table (except the first member) in AS400 Terminal
   
   CREATE ALIAS apsupdb.MMPF_ALIAS2 FOR apsupdb.mmpf(MBR2)
   CREATE ALIAS apsupdb.MMPF_ALIAS3 FOR apsupdb.mmpf(MBR3)
   
   In the above sample, we create 2 alias in library apsupdb , corresponding to 2 members apsupdb.mmpf(MBR2) & apsupdb.mmpf(MBR3).
   
   
2. New a Full Load + CDC task with a few tables. Certainly the task contains the physical table (first member).
3. Press "Export Task" and edit the exported JSON file
4. Add the ALIAS to task JSON file as same as it's a regular table. 
5. Change all STRING data type columns from UTF8 to "ibm-285_P100-1995". In below sample we change
   
   STRING type column "ADDRESS":
   "source_column_data_types": [{
   "column_name": "ADDRESS",
   "converter_name": "ibm-285_P100-1995",
   "data_type": "kAR_DATA_TYPE_STR"
   }],
   
   This is because Replicate cannot get the ALIAS metadata correctly so all STRING data type are regarded as UTF8 which leads garbage data after Full Load done. Other data types (eg number, date etc ) need not to modify.
   
   
6. Import the JSON and run the task, as same as a regular task.

Environment

• Qlik Replicate All supported versions
• IBM DB2 for iSeries All supported versions

Related Content

Support Case: 00049024

This article is specific to Qlik Sense Enterprise on Windows.

Enable Audit Logging:

1. Open the Qlik Sense Management Console
2. Open your Repository in the Repositories menu
3. Enable Audit log level and Qlik Management Console (QMC) log level to at least Info. 
4. Save

For more information on audit logging itself, see: How to enable Audit Logging in Qlik Sense Enterprise on Windows.

To read who has deleted an app:

1. Navigate to either C:\ProgramData\Qlik\Sense\Log\Repository\Trace (default logging folder) or your archived log folder if the log file is from a previous archiving cycle. 
2. Locate and open QLIKSERVER1_Audit_Repository.txt 
3. The line including the delete app action will look like this:
   
   INFO QlikServer1 Audit.Repository.Repository.Core.Repository.AppRepository 56 17eca1c0-6c7a-4ed9-87ac-3184e331f508 DOMAIN\QVservice App delete c0dee38d-9346-1d6c-0e3a-ff6f9033c824 Delete DOMAIN administrator 
   
   In this example, the user administrator has deleted the app with ID c0dee38d-9346-1d6c-0e3a-ff6f9033c824.

Environment

Qlik Sense Enterprise on Windows 

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.

Beginning November 1, 2022, Qlik is enforcing rate limits to API requests on Qlik Cloud REST APIs. This means any API request originating to a REST API endpoint on Qlik Cloud is subject to rejection if the number of requests to an endpoint exceeds the allowed amount in a specified duration on that endpoint. 

What is API rate limiting?

API rate limiting is a mechanism for ensuring API and platform performance and scalability. It protects the platform from being overwhelmed by requests made to API endpoints by throttling the number of requests an endpoint will accept before blocking or rejecting more requests from a client.

What Qlik experiences (clients) are impacted by rate limiting?

All REST endpoints in Qlik Cloud have a rate limit tier assignment. Any requests made from Qlik Sense REST connector, requests made from Qlik Application Automation, qlik-cli, any REST client like Postman, or custom application you create is subject to rate limiting. 

Limits are enforced per tier, per user, per tenant. When a rate limit is reached, all endpoints in the same tier are blocked until the retry-after time expires. When you exceed a rate limit, your application receives an HTTP 429 status code response such as below:

Environment:

Qlik Cloud 

How do I handle rate limiting in my applications?

Depending on the language, client, and code you’ve written to interact with Qlik’s APIs, you need to accommodate it to handle rate limits based upon the APIs you’re using. One way to do this is to add code that handles the 429 response by reading the `retry-after` response header and adding a function that throttles your application to wait until the retry period has elapsed.

How does API rate limiting in Qlik Cloud work?

Initially, rate limits are going to be enforced on Qlik Cloud REST API endpoints only. It is our intention to add external rate limits for other types of traffic including but not limited to websocket connections in a future release.

Here are the enforcement tiers for the number of requests allowed on an endpoint based on its assigned tiers.

We identified these tiers after observing API requests and rate limiting decisions from the beginning of 2022. Additional consideration has been paid to endpoints with heavy usage to make sure the services the APIs call scale to support the anticipated request volume.

Why is API rate limiting important to me?

API rate limiting is a mechanism for protecting your experience using the Qlik Cloud platform. Here are some reasons why we’re beginning to enforce rate limits on tenants:

• Rate limits are a baseline security mechanism to prevent brute-force attacks against the platform.
• Rate limiting prevents system degradation from a single application or user overwhelming the system.
• Rate limiting communicates to customers an expected service level for an API endpoint and how requests are treated if you cross a rate limit threshold.
• Enables Qlik to provide a platform that is affordable and returns business value through consistent uptime and a performant experience for our customers

Where can I learn more about Qlik Cloud API rate limits?

Information about Qlik Cloud API rate limits is visible on qlik.dev  beginning today, October 11, 2022. In the API reference section for Manage APIs, you can identify the rate limit tier for endpoints you use. Any special tier endpoints will indicate the specific API rate limit on the APIs reference page.

We released a new API Policy for working with Qlik Cloud’s APIs. Please review this page so you can ensure the end users of your solutions receive a pleasant experience interacting with Qlik Cloud.

Qlik Cloud platform features and APIs rely on rate limits to help provide a predictably pleasant experience for users.

The details of how and when rate limiting works differs between features and not based on customer subscriptions. All customers meet the same API rate limit tiers depending on the API endpoint. See Rate limiting for details.

Examples:

• The List users endpoint has a Tier 1 rate limit
• The Create user endpoint has a Tier 2 rate limit

Environment

• Qlik Cloud

Fails to deploy a Job in TAC, an error occurs and the detailed error messages are shown as below:

Resolution

The following configuration has been added to impose constraints on Job in order to prevent Denial of Service attacks. High default values have been established, and it is recommended to adjust them according to your specific environment.

On Linux

Add the following parameters in setenv.sh file([TAC]/apache-tomcat/bin/setenv.sh):

set "JAVA_OPTS=%JAVA_OPTS% -Xmx4096m -Dfile.encoding=UTF-8 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIPPED_ENTRIES=200000 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_SIZE=194679051264 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIP_NAME_LENGTH=3096 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FOLDER_NAME_LENGTH=1024 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH=1024 -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIP_DEPTH=2048"

On Windows

Add the following parameters to the Windows Service under "Java Options", please follow these steps:

1. Locate tomcat_directory/bin/tomcat8w.exe, a GUI application for monitoring and configuring Tomcat services.
2. Rename tomcat8w.exe to the service name for TAC, which you can find in the "Service name" field below.
   For example:
   Original name: tomcat8w.exe
   New name: talend-tac-8.0.1.exe
3. Look for the "Java" tab and under "Java Options", add the following parameters:

   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIPPED_ENTRIES=200000
   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_SIZE=194679051264
   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIP_NAME_LENGTH=3096
   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FOLDER_NAME_LENGTH=1024
   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH=1024
   -Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ZIP_DEPTH=2048"
   Internal Comments
   Tags
   Zip content exceeds,MAX_ZIPPED_ENTRIES

Environment

• Talend Administration Center 8.0.1

By embedding a chart object to your web application, you will use the following example in the body of the HTML file to set the ui attribute to object,  indicating to qlik-embed that you want to embed a specific visualization from a Qlik Sense application.

[ Fig.1 ]

<qlik-embed
  ui="analytics/chart"
  app-id="<APP_ID>"
  object-id="<CHART_ID>"
></qlik-embed>

Using " ui= analytics/chart" it should correctly render, for instance, a single KPI object, as per the documentation below : https://qlik.dev/extend/extend-qlik-visualizations/supported-charts/

The following error can occurs when trying to render the KPI in your web application:

Failed to load visualization: 'kpi'

This is because the character set is not supported and the only supported one is "utf-8".

Resolution

Apply the following instructions in your HTML file element which enforces utf-8 encoding and solves the issue: 

<meta charset="utf-8"> 

For usage where the encoding cannot be controlled by the user (such as embedding in a tool, e.g. Microsoft Excel ) and this error arises, the customer will have to embed with the "classic/chart" type and the option "iframe=true".

Environment

Qlik Cloud

Related Content 

2.0.1 Add the script configuration for qlik-embed