The HostInfo.xml file in Talend Data Catalog is used for license management. It contains your server's hardware and host identity information and is required whenever you need a new license generated by Qlik.

1. To download the HostInfo.xml file from your Talend Data Catalog, sign in as a user with the Application Administrator capability global role assignment.
2. Go to MANAGE > License.
3. Click DOWNLOAD LICENSE INFORMATION

4. Submit the HostInfo.xml file to the Qlik Customer Portal as part of your license request.
   
   Qlik will use the host information to generate a license file tied to your server.
   
   For active-passive cluster setups, you can get a license that works for both servers by providing two HostInfo.xml files, one for each server in your license request.

5. Once you have obtained your new .lic file, sign in as a user with the Application Administrator capability global role assignment.
6. Go to MANAGE > License.
7. Click UPDATE LICENSE
8. Confirm with Yes that you wish to continue.
9. Browse to the new license file and click Import.
10. Refresh your browser and log back in to see your new license.

Related Content

• Download License Information
• Update the License 
• Manage Users and Authentication 
• Manage Global Roles 

Environment

• Qlik Talend Data Catalog

Beginning on April 14, 2026, QlikView customers experienced outages and intermittent disruptions within their QlikView environments. These incidents coincided with the deployment of Microsoft’s April 2026 security patches to Domain Controllers, which affected QlikView Server Service (QVS) communications over port 4747.

The Microsoft patches introduced changes targeting Kerberos authentication and RC4 encryption. As a result, QlikView environments where RC4 remained enabled (such as at the domain account or Windows server level) became unstable or non-functional.

The impact on QlikView may include, but is not limited to:

• Failed QlikView Distribution Server distribution tasks with an error code indicating an Authentication Failure.
• "No Server" message on the QlikView AccessPoint with an error message in the Web server log indicating that the Web server cannot connect to the QlikView Server.
• Failed Qlik NPrinting distributions to QlikView using a QVP Connection.
• Problems accessing the QlikView Server settings from the QlikView Management Console, or failures for the QlikView Server to come online after a restart.

This article documents the steps to reconfigure the environment to comply with the RC4 cipher suite deprecation. 

Resolution

Information in this article is based on Microsoft's remediation steps and has been adjusted and expanded to include QlikView-specific instructions. For the original, see Detect and remediate RC4 usage in Kerberos | learn.microfot.com. 

There are three stages; not all may be required. Always start at the first one.

Reset the Computer Account

These steps require you to remove the computer from the domain and then re-add it. Before proceeding, ensure you have a Local Administrator account and its password for each of the QlikView servers.

1. Confirm the Domain Controllers and the QlikView server(s) have the Microsoft patch applied.
2. Reset the Active Directory Computer Account (not the Service Account) on the Domain Controller’s Active Directory Users and Computers interface.
3. Place the QlikView server(s) into a Workgroup:
   1. Log onto the local computer of the QlikView server
   2. Open the Server Manager
   3. Go to Local Server
   4. Go to Computer Name
   5. Place the server in a local group
   6. Reboot the QlikView server
   7. Repeat the step for all QlikView servers if you have additional nodes
4. Return the QlikView server(s) to the Domain:
   1. After the reboot, return to the Server Manager
   2. Go to Local Server
   3. Go to Computer Name
   4. Re-join the Domain and reboot the server
   5. Repeat the step for all QlikView servers if you have additional nodes
5. Test the QlikView environment to confirm this has resolved the interruptions.

Kerberos ticket reset

It may be necessary to clear the Kerberos ticket on the affected QlikView server(s).

1. Open PowerShell or a Command Prompt with elevated permissions
2. Run the command: Klist purge

Reset the Service Account

It may be necessary to reset the Domain password for the QlikView service account.

1. Verify that all server Domain Controllers and Windows Servers on which the QlikView Application is installed are patched.
2. Verify that RC4 encryption is disabled.
3. Reset the QlikView service account password.
4. Open the Services panel, then reapply the QlikView service account using the new password
5. Restart the QlikView services.

   If the QlikView service account was used for any data connection(s), they will need to be updated with the new password.

Related Content

• What Changed in RC4 with the January 2026 Windows Update and Why it is Important | techcommunity.microsoft.com 

Microsoft Patches:

• Windows Server 2022 (DC): KB5082142
• Windows Server 2019 (DC): KB5082123
• Windows Server 2016 (DC): KB508208

Environment

• QlikView

This article explains how to connect the Qlik MCP (Model Context Protocol) server to Snowflake Intelligence, enabling Snowflake Cortex Agents to query and interact with Qlik Cloud resources, such as apps, data assets, and analytics, directly from the Snowflake AI interface.

Content

• Prerequisites
• Setup Steps
• Create an OAuth2 Client in Qlik Cloud
• Register the Qlik MCP Server in Snowflake
• Connect to Qlik MCP in Snowflake Intelligence
• Test with a Cortex Agent
• Troubleshooting
• Related Content

Prerequisites

• Qlik Cloud: Tenant Administrator access to create OAuth clients in the Administration activity center
• Snowflake: ACCOUNTADMIN role (or a role with CREATE INTEGRATION and CREATE MCP SERVER privileges)
• Snowflake Intelligence access (Cortex Agents) enabled on your Snowflake account
• Your Qlik Cloud tenant hostname (example: your-tenant.us.qlikcloud.com)

Setup Steps

Create an OAuth2 Client in Qlik Cloud

The OAuth2 client provides Snowflake with the credentials it needs to authenticate against the Qlik MCP server on behalf of users. For details on creating OAuth clients, see Creating and managing OAuth clients.

Copy the Client ID and Client Secret immediately after creation. The secret cannot be retrieved later — if lost, you must generate a new one.

1. Log in to your Qlik Cloud tenant and navigate to the Administration activity center, or go directly to https://<your-tenant>/console.
2. Go to OAuth 
3. Click Create New
4. Fill in the following fields:
   
   
   • Name: A descriptive name
   • Client type: Web
   • Authentication method: Client secret
   • Redirect URL: https://identity.snowflake.com/oauth2/callback
   • Allowed origins (optional): https://identity.snowflake.com
   • Scopes: user_default, mcp:execute

     The mcp:execute scope is required to allow Snowflake to invoke tools on the Qlik MCP server. The user_default scope grants access to resources the authenticated user can already access in Qlik Cloud.

5. Click Create.
6. A dialog will display the Client ID and Client Secret. 
   
   Copy both values immediately and store them securely. The Client Secret will not be shown again.
   
   

Register the Qlik MCP Server in Snowflake

For details on the Qlik MCP server endpoint and supported tools, see Connecting to the Qlik MCP server.

Using the OAuth client credentials previously retrieved, run the following Snowflake SQL script to:

• Create an API Integration with OAuth2, pointing to your Qlik tenant
• Register an External MCP Server using that integration
• Grant usage to the appropriate role
  

  -- ============================================================
  -- Parameters — update these values before running
  -- ============================================================
  SET TENANT        = '<your-tenant>.us.qlikcloud.com'; -- Do not include https://
  SET CLIENT_ID     = '<your-oauth-client-id>';
  SET CLIENT_SECRET = '<your-oauth-client-secret>';
  SET ALLOWED_ROLE  = 'PUBLIC'; -- The Snowflake role that should have access.
                                -- ⚠️ PUBLIC grants access to all users in the account.
                                -- For production, replace with a more restrictive role.
  
  -- ============================================================
  -- Derived values — no changes needed below this point
  -- ============================================================
  SET MCP_URL = 'https://' || $TENANT || '/api/ai/mcp';
  
  -- Create the API Integration with OAuth2 configuration
  DROP API INTEGRATION IF EXISTS qlik_mcp_integration;
  
  EXECUTE IMMEDIATE
  $$
  DECLARE
      v_tenant        VARCHAR;
      v_client_id     VARCHAR;
      v_client_secret VARCHAR;
      v_mcp_url       VARCHAR;
      sql_stmt        VARCHAR;
  BEGIN
      SELECT GETVARIABLE('TENANT')        INTO v_tenant;
      SELECT GETVARIABLE('CLIENT_ID')     INTO v_client_id;
      SELECT GETVARIABLE('CLIENT_SECRET') INTO v_client_secret;
      v_mcp_url := 'https://' || v_tenant || '/api/ai/mcp';
  
      sql_stmt :=
          'CREATE API INTEGRATION qlik_mcp_integration'
          || ' API_PROVIDER = external_mcp'
          || ' API_ALLOWED_PREFIXES = (''' || v_mcp_url || ''')'
          || ' API_USER_AUTHENTICATION = ('
          || '   TYPE = OAUTH2'
          || '   OAUTH_CLIENT_ID = ''' || v_client_id || ''''
          || '   OAUTH_CLIENT_SECRET = ''' || v_client_secret || ''''
          || '   OAUTH_TOKEN_ENDPOINT = ''https://' || v_tenant || '/oauth/token'''
          || '   OAUTH_CLIENT_AUTH_METHOD = CLIENT_SECRET_POST'
          || '   OAUTH_AUTHORIZATION_ENDPOINT = ''https://' || v_tenant || '/oauth/authorize'''
          || '   OAUTH_REFRESH_TOKEN_VALIDITY = 86400'
          || '   OAUTH_ALLOWED_SCOPES = (''user_default'', ''mcp:execute'')'
          || ' )'
          || ' ENABLED = TRUE';
  
      EXECUTE IMMEDIATE sql_stmt;
  END;
  $$;
  
  SHOW API INTEGRATIONS LIKE '%qlik%';
  
  SET DISPLAY = 'Qlik MCP server ' || $TENANT;
  DROP EXTERNAL MCP SERVER IF EXISTS qlik_mcp_server;
  
  CREATE EXTERNAL MCP SERVER qlik_mcp_server
      WITH DISPLAY_NAME = $DISPLAY
      API_INTEGRATION  = qlik_mcp_integration;
  
  ALTER EXTERNAL MCP SERVER qlik_mcp_server
      SET URL = $MCP_URL;
  
  -- Grant access to the specified role
  GRANT USAGE ON INTEGRATION  qlik_mcp_integration TO ROLE IDENTIFIER($ALLOWED_ROLE);
  GRANT USAGE ON MCP SERVER   qlik_mcp_server       TO ROLE IDENTIFIER($ALLOWED_ROLE);
  
  -- ============================================================
  -- Verification queries
  -- ============================================================
  SHOW EXTERNAL MCP SERVERS;
  DESCRIBE EXTERNAL MCP SERVER qlik_mcp_server;
  SHOW API INTEGRATIONS LIKE '%qlik%';
  
  -- Initiate the user OAuth flow
  SELECT SYSTEM$START_USER_OAUTH_FLOW('qlik_mcp_integration');
  ​

  The SYSTEM$START_USER_OAUTH_FLOW call at the end generates a URL you can open in a browser to validate the OAuth handshake with Qlik Cloud before proceeding to Snowflake Intelligence.

Connect to Qlik MCP in Snowflake Intelligence

Once the MCP server is registered in Snowflake, you can authorize and use it directly from the Snowflake Intelligence UI.

1. Open Snowflake Intelligence. The URL follows the pattern https://ai.snowflake.com/<orgname>/<accountname>.
   
   For example, https://ai.snowflake.com/myorg/myaccount. If you are unsure of your URL, contact your Snowflake account administrator.
   
   
2. Click your profile icon (bottom left corner) to open your personal settings.
3. Navigate to the Connectors section. You will see Qlik MCP Server listed, pointing to your configured Qlik Cloud tenant.
4. Click the Connect button next to the Qlik MCP entry.
5. You will be redirected to Qlik Cloud to complete the OAuth2 authorization flow. Log in with your Qlik Cloud credentials if prompted, then approve the requested permissions (user_default, mcp:execute).
6. After authorization, you are returned to Snowflake Intelligence. The Qlik MCP connector will show a Connected status.
7. You can now ask Snowflake Intelligence questions that involve Qlik Cloud resources. The Cortex Agent will automatically invoke the appropriate Qlik MCP tools to retrieve data, apps, or analytics content.
   
   

Test with a Cortex Agent

To validate the full integration, create a test Cortex Agent that uses the Qlik MCP server.

Before running: Replace CORTEX_APP.PUBLIC with the database and schema where you want to create the agent in your Snowflake environment. The database must already exist.

-- Replace <YOUR_DATABASE> and <YOUR_SCHEMA> with your target database and schema
CREATE OR REPLACE AGENT <YOUR_DATABASE>.<YOUR_SCHEMA>.qlik_mcp_test_agent
  FROM SPECIFICATION $$
models:
  orchestration: auto
instructions:
  response: >
    You are a test agent that verifies connectivity to the Qlik MCP server.
    Use the available Qlik tools to answer the user's question.
  orchestration: "Use the Qlik MCP tools to answer questions about Qlik Cloud."
mcp_servers:
  - server_spec:
      name: "<YOUR_DATABASE>.<YOUR_SCHEMA>.QLIK_MCP_SERVER"
$$;

Once created, invoke the agent with a test prompt such as: What Qlik apps are available in my tenant?

A successful response confirms end-to-end connectivity between Snowflake Cortex and the Qlik MCP server.

Troubleshooting

OAuth redirect fails

Typically caused by a Redirect URL mismatch. Verify https://identity.snowflake.com/oauth2/callback is set in the Qlik OAuth client

mcp:execute scope error

The scope not enabled on OAuth client. Edit the OAuth client in Qlik Cloud Administration activity center and add the mcp:execute scope

Client Secret rejected

Secret was rotated or lost. Generate a new client secret and update $CLIENT_SECRET in the script

MCP Server not visible in Snowflake Intelligence

The correct role was not granted. Confirm GRANT USAGE ON MCP SERVER was executed for the user's active role.

Agent returns no results

The OAuth flow was not completed. Complete the steps in Connect to Qlik MCP in Snowflake Intelligence.

Related Content

• Connecting to the Qlik MCP server | Qlik Cloud Help
• Creating and managing OAuth clients | Qlik Cloud Help
• Snowflake External MCP Server documentation

Environment

• Qlik MCP
• Qlik Cloud

The information in this article is provided as-is and to be used at your own discretion. Depending on the tools used, customizations, and/or other factors, ongoing support on the solution described may not be provided by Qlik Support.

Qlik Cloud automatically places applications on compute engines based on calculated metrics that determine the required resources. This automatic placement works well for most apps, but some require manual intervention.

Apps with large chart objects that generate large hypercubes can consume all available memory and crash. By pinning an app to a specific engine size, you control the minimum compute resources available for interactive consumption.

For details, see Assigning engines to improve application performance and Pin applications to engine sizes.

This article aims to clarify how reloads are handled for an app pinned to an engine, since assigning an engine concerns only the opening and consumption of apps by end users, not app reloads.

How reloads are handled:

• The optimization concerning app reloads is based on a similar concept: Qlik Cloud still automatically places applications on engines based on calculated metrics that determine the required resources.
• As a rule, the app will initially be placed on an engine based on the metrics of the last successful reload.
• If that engine is not sufficiently large, the reload will at first fail and then be moved to a larger one, where it will restart from scratch.
• This process is not made obvious to end users and administrators. The initial failures won't be noticed in logs or alerts, although analyzing the details might show a later "start time" than expected since only the successful run will be shown.
• The next time the task is run, it will automatically start on the larger engine.
  In rare scenarios, the calculated metrics might not reflect the required resources, and the behaviour could be erratic. In case of issues, do not hesitate to contact support with all the necessary information (appIds, taskIds, reloadIds, timestamps). 

Environment

• Qlik Cloud

Deploying the Qlik Data Gateway Monitoring Tool

The Data Gateway Monitoring tool provides an additional layer of logging that Qlik's R&D team can use to troubleshoot Data Gateway issues for a Data Gateway that was successfully installed and running previously. 

This troubleshooting tool is not necessary for the day-by-day operation of the Data Gateway Direct Access deployment and can be disabled after troubleshooting has been completed.

1. Download the Qlik.ConnectorAgent.Monitor.Installer-x.x.x.exe installer available at
   Installing Data Gateway Monitor Instructions and Download link
   
2. Install the Qlik Data Gateway Monitoring tool where you have the Qlik Data Gateway Direct Access deployed.
   
   The installation requirements are the same as for Qlik Data Gateway Direct Access. See Best practices. 
   
   A Windows Server service will be installed that can be set to manual when troubleshooting is completed.
   
   
3. Reproduce the issue and monitor logging will automatically collect/log data.
   
   
4. Zip and upload the logs from C:\ProgramData\Qlik\Gateway\Monitor\Logs to the Qlik Support case.
   
   If the zip is too large for the support site, ask your Qlik support engineer to provide you with the dedicated upload space for your specific case.
   

More details about this tool can be found here.

General Health Check and Monitoring of Qlik Data Gateway

1. To check overall Data Gateway health, access the following URL in a supported browser: http://localhost:5050/health
   
   A simple 'OK' will appear if Gateway is connected to the cloud instance and running normally.
   
   
   
2. To check Data Gateway connections status, access the following URL in a supported browser: http://localhost:5050/status
   
   Scroll to the bottom of the status page. Healthy Data Gateway status will be indicated by a Pass result.
   
   

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.

Qlik constantly refines its Analytics, over time replacing old charts with new, modernized alternatives. These deprecations are announced well in advance and include instructions on how best to replace these old charts, whether that is to use a new one, several new ones, or to make use of new settings.

As an example, seven visualization bundle charts are scheduled for deprecation in May 2027, most of which have already been removed from the asset panel and are no longer in use in recent applications. See Upcoming deprecation of Qlik Analytics charts in May 2027.

What do I use instead?

Charts that are up for deprecation are often no longer in use. However, if you happen to still have a very old application and need to replace it, see Visualization bundle > Deprecated charts for more information on what to use instead. The list will be updated whenever a new set of charts is deprecated.

How do I find out if my apps are using the deprecated charts?

Qlik recommends reviewing your apps for old charts. Depending on your platform (Qlik Cloud or Client-managed), there are different methods you can deploy.

Qlik Cloud

Qlik Cloud administrators should use the Qlik Cloud Monitoring Apps to track the usage. The App Analyzer has a sheet dedicated to where deprecated charts are being used on a tenant in Qlik Cloud. The App Analyzer is based on usage events rather than scanning every app. Use the App Analyzer to find which apps and sheets have charts that need to be updated to newer and more modern alternatives. The easiest way to install and update the Qlik Cloud Monitoring Apps is to use the automation template. If you already have the App Analyzer, just remove the automation and install a new one to get the latest version of the App Analyzer. 

Client-managed

For client-managed installations, use the Monitoring apps. The Content Monitor app has a sheet for tracking deprecated charts. At reload, the Content Monitor app scans every app in the installation in order to list all applications and sheets that are using charts that are being deprecated. It also lists the installed extensions and their deprecation status. The Monitoring apps are bundled with the Qlik Analytics installation. The first version with the new sheet will be included in the May 2026 release. If you want to track usage in prior versions, the deprecated chart usage scanner will also be available on the product download page.

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

To change the Talend Remote Engine wrapper port defaults, edit the Remote Engine's wrapper configuration file named RE_HOME/etc/talend-remote-engine-wrapper.conf. 

1. Stop the Remote Engine service on the target machine before editing configuration files.
2. If the engine was installed with the wrapper service, edit the following: 
   
   RemoteEngineInstallationDirectory/etc/talend-remote-engine-wrapper.conf
   
   
3. Adjust or add the JVM arguments and any wrapper-specific port settings.
   
   Example:
   
   =====================
   wrapper.jvm.port.min=61000
   wrapper.jvm.port.max=61999
   wrapper.port=62000
   ===================
   
   
4. Save the change.
5. Start the engine service.
6. Verify pairing and connection in Talend Management Console, and verify that the correct ports are used.
   
   Linux (use ps -ef | grep java):
   
   
   
   Windows (resource monitor):
   
   
   
   

For more information, see wrapper.jvm.port.

Environment

• Qlik Talend Cloud
• Remote Engine; Linux & Windows

To configure a proxy for a Talend Data Catalog server on Linux:

1. Stop the Talend Data Catalog application server
2. Locate the Talend Data Catalog Tomcat configuration:
   
   On Linux, the Talend Data Catalog server typically runs in a Tomcat‑style container under the installation directory (for example, /opt/talend/talend-data-catalog).
   
   The key paths are $TDC_HOME/bin/setenv.sh or equivalent startup script, often in /bin/ or /bin/linux_x86_64.
   
   
3. Configure the JVM proxy properties:
   
   
   1. Edit the $TDC_HOME/bin/setenv.sh of the Talend Data Catalog server on Linux.
   2. Add the JVM arguments for the proxy: -Dhttps.proxyHost= <IP or HostName> -Dhttps.proxyPort=3128
      
      Example:
      
      

      JAVA_OPTS="-D\"catalina.data=${CATALINA_DATA}\" -D\"connector.port=${M_CONNECTOR_PORT}\" -D\"shutdown.port=${M_SHUTDOWN_PORT}\" -D\"server.fqdn=${M_SERVER_FQDN}\" -Dlog4j2.disableJmx=true -Djava.awt.headless=true -Dhttp.proxyHost=<IP or HostName> -Dhttp.proxyPort=3128 -Dhttps.proxyHost= <IP or HostName> -Dhttps.proxyPort=3128"

4. Restart
5. To verify if the Talend Data Catalog application server uses the proxy, run the following command:
   
   

   $ps -ef | grep java

   
   This will output the following:
   
   [root@RHEL8-QCDI01 ~]# ps -ef | grep java
   root       23155       1  6 May11 ?        12:28:04 /home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../jre/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms256M -Xmx4096M -Dcatalina.data=/home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../data -Dconnector.port=11480 -Dshutdown.port=11481 -Dserver.fqdn=localhost -Dlog4j.configurationFile=/home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../tomcat/conf/log4j2.xml -Dlog4j2.disableJmx=true -Djava.awt.headless=true -Dhttp.proxyHost=10.76.203.106 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=10.76.203.106 -Dhttps.proxyPort=3128 -Djdk.tls.ephemeralDHKeySize=2048 - [...]
   
   

Note the effect using a proxy will have if you have SAML/SSO enabled. See Configuring the SAML server for details. 

Environment

• Talend Data Catalog Server
• Squid Proxy Server

You may encounter the following error when using Qlik Talend Cloud and a Remote Engine:

REST Microservice fails on Remote engine with: Log4jLoggerFactory: method 'void <init>()' not found 

Resolution

Use Hive 3 to resolve this dependency issue. Choose the appropriate version in the Hive connection configuration. See tHiveConnection.

Cause

This is due to the Hive version 2 (hive-exec2 dependency) using log4j-slf4j-impl, which causes a conflict on the Remote Engine deployment. 

Environment

• Qlik Talend Cloud

This article describes how to connect Talend Studio to Starburst (Galaxy or Enterprise) using the Trino JDBC driver. It covers driver download, JDBC connection configuration inside Talend Studio, and load script patterns for querying Starburst catalogs. It is intended for use alongside Qlik Sense Enterprise on Windows (client-managed) environments where Talend Studio is used as the ETL layer to stage or transform data before it is consumed by Qlik.

Content

• Prerequisites
• Download the Trino JDBC Driver
• Configure the JDBC Connection in Talend Studio
• Connection Settings: Galaxy vs. Enterprise
• Schema and Catalog Usage
• Trino SQL Compatibility Notes
• Talend Component Patterns
• Troubleshooting
• References

Prerequisites

Before configuring the connection, ensure the following requirements are met:

• Talend Studio (Data Integration or Big Data edition), version 7.x or later.
• Java Runtime Environment (JRE) 11 or later, as required by the Trino JDBC driver.
• Network connectivity from the Talend Studio workstation or server to the Starburst cluster endpoint.
• A Starburst user account (Galaxy service account or Enterprise user) with SELECT privileges on the target catalog and schema.
• Internet access to download the Trino JDBC driver from Maven Central, or an internal Maven proxy that mirrors it.

Download the Trino JDBC Driver

Talend Studio connects to Starburst using the Trino JDBC driver. Unlike the ODBC driver used for Qlik Sense direct connections, no platform installer is required. The driver is a single JAR file.

1. Download the Trino JDBC driver JAR from Maven Central:

   https://repo1.maven.org/maven2/io/trino/trino-jdbc/479/trino-jdbc-479.jar

2. Save the JAR to a stable local path, for example:

   C:\Drivers\Starburst\trino-jdbc-479.jar  

3. Do not rename the JAR file. Talend Studio uses the filename to identify the driver.

Check the Starburst documentation for the recommended JDBC driver version that matches your Starburst Galaxy or Enterprise deployment. The version referenced above (479) is the version used in the Data Nova Conference demo environment.

Configure the JDBC Connection in Talend Studio

Talend Studio uses a generic JDBC database connection type to connect to Starburst. The steps below apply to both Starburst Galaxy and Starburst Enterprise. The only difference is the JDBC URL and credentials.

Add a New Database Connection

• Open your Talend Studio project.
• In the Repository panel, expand Metadata and right-click Db Connections.
• Select Create connection.
• Enter a connection name (for example: Starburst Galaxy or Starburst Enterprise) and click Next.

Select the JDBC Connection Type

• In the DB Type dropdown, search for and select JDBC.
• Click Next to proceed to the driver and URL configuration.

Configure Driver and Connection Parameters

Complete the connection form with the following parameters:

Example JDBC URL for the Data Nova Conference demo environment (Starburst Galaxy):

jdbc:trino://stardock-qlik.starport.starburst.io:443/transactional_data

1. Click the [...] button next to the Driver JAR field and browse to the trino-jdbc-479.jar file saved in Download the Trino JDBC Driver.
2. In the Driver Class field, enter or select: io.trino.jdbc.TrinoDriver
3. Enter the User ID and Password for the Starburst service account.
4. Click Check to test the connection. A successful test displays the Starburst version.
5. Click Finish to save the connection.

If the connection test fails with an SSL error when connecting to Starburst Galaxy, ensure that Java's certificate store trusts the public CA that signed the Galaxy endpoint certificate. For Starburst Enterprise with a self-signed certificate, import the certificate into the JRE keystore using keytool.

Connection Settings: Galaxy vs. Enterprise

The table below summarises the JDBC parameters that differ between Starburst Galaxy and Starburst Enterprise: 

The Trino JDBC driver is the same JAR for both Galaxy and Enterprise. Only the JDBC URL, port, and authentication settings differ.

Schema and Catalog Usage

Starburst organises data in a three-level hierarchy: catalog > schema > table. The JDBC URL specifies the default catalog. The schema is set in the Talend connection configuration and can be overridden at the component level.

Specifying the Default Catalog in the JDBC URL

Include the catalog name as the path component of the JDBC URL:

jdbc:trino://stardock-qlik.starport.starburst.io:443/transactional_data

In this example, transactional_data is the catalog. All queries run through this connection will default to that catalog unless a three-part table name is used.

Using Three-Part Table Names in Talend Components

When querying tables across multiple catalogs within the same Talend job, use three-part table names in tDBInput or tDBRow SQL queries:

SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM transactional_data.retail.customers
WHERE created_date >= DATE '2024-01-01'

Always use three-part table names (catalog.schema.table) in SQL queries inside Talend components to avoid ambiguity, even when a default catalog is set in the JDBC URL.

Trino SQL Compatibility Notes

Starburst uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed when writing SQL inside Talend components (tDBInput, tDBRow, tDBOutput):

Talend Component Patterns

The following patterns cover common scenarios for reading from and writing to Starburst within a Talend Studio job.

Reading Data with tDBInput

• Use the Starburst JDBC connection configured in Configure the JDBC Connection in Talend Studio.
• In the tDBInput component, set the Query field to a valid Trino SQL SELECT statement using three-part table names.
• Map the output schema columns to match the SELECT column list.

Writing Data with tDBOutput

• Starburst supports INSERT INTO for Iceberg and Delta Lake tables. Hive connector tables may be read-only depending on the catalog configuration.
• Set the Action on the table to Insert and ensure the target table exists in Starburst before running the job.
• Use three-part table names in the Table field: catalog.schema.table.

Incremental Loads with Context Variables

Use Talend context variables to pass date parameters into SQL predicates for incremental data loads:

Define a context variable:

context.lastLoadDate = 2024-01-01

Reference it in the tDBInput query:

SELECT *
FROM transactional_data.retail.transactions
WHERE transaction_date >= DATE '" + context.lastLoadDate + "'

For production incremental loads, persist the last successful load date to a Talend context file or a control table in Starburst so that the value survives job restarts.

Troubleshooting

Connection test fails: ClassNotFoundException

• Verify the full path to the trino-jdbc-479.jar is correct in the Driver JAR field.
• Confirm the Driver Class is exactly io.trino.jdbc.TrinoDriver (case-sensitive).
• Ensure the JAR has not been renamed or moved since the connection was saved.

Connection test fails: SSL handshake error

• For Starburst Galaxy, confirm that the Talend Studio JRE trusts the public CA certificate chain for *.galaxy.starburst.io.
• For Starburst Enterprise with a self-signed certificate, import the certificate into the JRE keystore: keytool -import -alias starburst -keystore $JAVA_HOME/lib/security/cacerts -file starburst.crt
• Verify that the JDBC URL uses the correct port (443 for Galaxy, 8443 for Enterprise HTTPS).

Authentication failure: Access Denied

• Confirm the User ID and Password match the Starburst Galaxy service account credentials or the Starburst Enterprise user account.
• For Galaxy, verify that the service account has not been deactivated or had its password rotated.
• Test the same credentials in the Starburst Galaxy Query Editor or Enterprise query interface before diagnosing the Talend connection.

Query error: [Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive.
• Confirm the Starburst user account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst query interface before embedding it in the Talend component.

Slow job performance

• Push filtering predicates into the SQL WHERE clause in the tDBInput query rather than relying on Talend tFilterRow components downstream.
• Select only required columns rather than using SELECT *.
• Review the Starburst query history to identify slow-running queries and optimise at the catalog or connector level.

References

• Trino JDBC driver (Maven Central)
• Starburst Galaxy documentation
• Talend Studio documentation

Environment

• Talend Studio

This article describes how to connect Qlik Sense Enterprise on Windows (client-managed) to Starburst Galaxy using the Starburst ODBC driver. It covers driver installation, data connection configuration, and load script patterns for querying Starburst Galaxy catalogs via Trino SQL.

Content

• Prerequisites
• Install the Starburst ODBC Driver
• Configure an ODBC Data Source (DSN)
• Create a Data Connection in Qlik Sense
• Load Script Patterns
• Trino SQL Compatibility Notes
• Troubleshooting
• Related Content and References

Prerequisites

Before configuring the connection, ensure the following requirements are met on the Qlik Sense server or any node that will execute data load tasks:

• Qlik Sense Enterprise on Windows (client-managed), version February 2022 or later.
• Network connectivity from the Qlik Sense server to the Starburst Galaxy cluster endpoint (default port 443 over HTTPS/TLS).
• A Starburst Galaxy account with a running cluster and at least one catalog configured.
• A Starburst Galaxy service account username and password (or personal access token) with SELECT privileges on the target catalog and schema.
• Administrator access on the Windows server to install the ODBC driver and configure the DSN.

Install the Starburst ODBC Driver

Starburst provides a dedicated ODBC driver for Galaxy that is based on the Simba/Magnitude Trino ODBC driver. Use only the Galaxy-specific build to ensure compatibility with Galaxy authentication and TLS settings.

1. Download the Driver
   1. Log in to your Starburst Galaxy account at https://galaxy.starburst.io.
   2. Navigate to Settings > Clients & Tools > Drivers.
   3. Download the Windows 64-bit ODBC driver package (.msi or .zip).
   4. Copy the installer to the Qlik Sense server.
2. Install the Driver
   1. Run the installer as a local administrator.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select "System DSN" scope so that the Qlik Sense service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver even if the Qlik Sense process appears as 32-bit. Qlik Sense on Windows runs as a 64-bit process.

Configure an ODBC Data Source (DSN)

A System DSN makes the driver available to all Windows services, including the Qlik Sense Engine and Scheduler services.

1. Open ODBC Data Source Administrator (64-bit) from Windows Administrative Tools.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstGalaxy (used in the Qlik connection string)
   Host	<your-cluster>.galaxy.starburst.io
   Port	443
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP (username/password) or OAuth2 (token)
   SSL	Enabled (required for Galaxy)
   SSL Certificate	Use the system certificate store

   
   
   
5. Click Test Connection to verify connectivity. A successful test returns the Starburst Galaxy version.
6. Click OK to save.

If the test connection fails with a TLS error, ensure that the Starburst Galaxy root certificate is trusted by the Windows certificate store on the Qlik Sense Enterprise on Windows server.

Create a Data Connection in Qlik Sense

1. In the Qlik Sense Management Console (QMC), navigate to Data Connections.
2. Click Create new and select ODBC.
3. Select the StarburstGalaxy DSN created in Configure an ODBC Data Source (DSN).
4. Enter the service account credentials.
5. Set the connection name to: Data Nova Conference:Starburst Galaxy
   This name is required by the standard load script connection string used in Qlik apps that target this tenant.
6. Click Apply and test the connection.

The connection name Data Nova Conference:Starburst Galaxy is the canonical name used in all Qlik load scripts for this integration. Changing it requires updating all dependent scripts.

Load Script Patterns

The following patterns cover common scenarios for loading data from Starburst Galaxy into Qlik Sense Enterprise on Windows.

1. Establish the Connection
   
   Always use the following statement at the top of the load script tab that accesses Starburst Galaxy:

   LIB CONNECT TO 'Data Nova Conference:Starburst Galaxy'; 

2. Basic SQL SELECT

   Use three-part table names (catalog.schema.table) in all Trino SQL statements:

   Customers:
   SQL SELECT
      customer_id,
      customer_name,
      region,
      created_date
   FROM burstbank.retail.customers
   WHERE created_date >= DATE '2024-01-01';

3. Joining Tables

   Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume:

   Orders:
   SQL SELECT
      o.order_id,
      o.customer_id,
      o.order_date,
      o.total_amount,
      c.customer_name,
      c.region
   FROM burstbank.retail.orders o
   JOIN burstbank.retail.customers c ON o.customer_id = c.customer_id;

4. Incremental Load

   Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

   LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

   Transactions:
   SQL SELECT *
   FROM burstbank.retail.transactions
   WHERE transaction_date >= DATE '$(vLastLoadDate)';

Trino SQL Compatibility Notes

Starburst Galaxy uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed:

Troubleshooting

Connection fails in QMC

• Verify the DSN name matches exactly (case-sensitive) in the data connection configuration.
• Confirm the Qlik Sense service account has Read permission on the Windows registry key for the System DSN.
• Check that TCP port 443 is open outbound from the Qlik Sense server to the Galaxy cluster host.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive in some catalogs.
• Confirm the Galaxy service account has SELECT privileges on the target table.
• Test the same SQL in the Starburst Galaxy Query Editor before embedding it in the Qlik load script.

Slow load performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses.
• Select only required columns rather than using SELECT *.
• Consider using Starburst Galaxy materialized views for frequently queried aggregations.

Related Content and References

• Starburst Galaxy documentation
• Qlik ODBC connector documentation

Environment

• Qlik Sense Enterprise on Windows

This article describes how to connect Qlik Sense Enterprise on Windows (client-managed) to Starburst Enterprise (self-managed, on-premises or private cloud) using the Starburst ODBC driver. It covers driver installation, data connection configuration, and load script patterns for querying Starburst Enterprise catalogs via Trino SQL.

Content

• Prerequisites
• Install the Starburst ODBC Driver
• Configure an ODBC Data Source (DSN)
• Create a Data Connection in Qlik Sense
• Load Script Patterns
• Trino SQL Compatibility Notes
• Differences vs. Starburst Galaxy
• Troubleshooting
• Related Content and References

Prerequisites

Before configuring the connection, ensure the following requirements are met on the Qlik Sense server or any node that will execute data load tasks:

• Qlik Sense Enterprise on Windows (client-managed), version February 2022 or later.
• Network connectivity from the Qlik Sense server to the Starburst Enterprise coordinator node (default port 8443 for HTTPS/TLS, or 8080 for HTTP).
• A Starburst Enterprise deployment with at least one catalog configured and the coordinator accessible from the Qlik network segment.
• A Starburst Enterprise user account with SELECT privileges on the target catalog and schema.
• Administrator access on the Windows server to install the ODBC driver and configure the DSN.
• The Starburst Enterprise TLS certificate (or the CA certificate chain) if using HTTPS, to be trusted by the Windows server.

Install the Starburst ODBC Driver

Starburst provides a dedicated ODBC driver for Starburst Enterprise based on the Simba/Magnitude Trino ODBC driver. Download the Enterprise-specific build from your Starburst Enterprise distribution. Do not use the Galaxy driver.

1. Download the Driver
   1. Log in to the Starburst Enterprise software portal or obtain the driver package from your Starburst account representative.
   2. Download the Windows 64-bit ODBC driver package (.msi) that matches your Starburst Enterprise version.
   3. Copy the installer to the Qlik Sense server.
2. Install the Driver
   1. Run the installer as a local administrator.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select "System DSN" scope so that the Qlik Sense service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver. Qlik Sense on Windows runs as a 64-bit process regardless of the label shown in Windows Task Manager.

Configure an ODBC Data Source (DSN)

A System DSN makes the driver available to all Windows services, including the Qlik Sense Engine and Scheduler services.

1. Open ODBC Data Source Administrator (64-bit) from Windows Administrative Tools.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstEnterprise (used in the Qlik connection string)
   Host	<coordinator-hostname-or-ip>
   Port	8443 (HTTPS) or 8080 (HTTP — not recommended for production)
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP, Kerberos, or Password (depends on Starburst Enterprise configuration)
   SSL	Enabled for HTTPS deployments; disabled for HTTP-only test environments
   SSL Certificate	Path to the PEM or PFX certificate file, or use the system certificate store if the CA is trusted

    

5. Click Test Connection to verify connectivity. A successful test returns the Starburst Enterprise version.
6. Click OK to save.

If Kerberos authentication is required, ensure the Qlik Sense service account has a valid Kerberos ticket and that the Kerberos configuration file (krb5.ini) is present at C:\Windows\krb5.ini on the Qlik Sense server.

Create a Data Connection in Qlik Sense

1. In the Qlik Sense Management Console (QMC), navigate to Data Connections.
2. Click Create new and select ODBC.
3. Select the StarburstEnterprise DSN created in Configure an ODBC Data Source (DSN)
4. Enter the service account credentials appropriate to your authentication method (LDAP username/password, or leave blank for Kerberos SSO).
5. Set the connection name to reflect your deployment (for example: Starburst Enterprise:Production).
   Update the LIB CONNECT TO statement in your load scripts to match the connection name you choose.
6. Click Apply and test the connection.

Unlike Starburst Galaxy, the connection name for Starburst Enterprise deployments can be customised to match your environment. Ensure the name is consistent across all load scripts that use this connection.

Load Script Patterns

The following patterns cover common scenarios for loading data from Starburst Enterprise into Qlik Sense. The patterns are identical to those used with Starburst Galaxy; the only difference is the connection name in the LIB CONNECT TO statement.

1. Establish the Connection
   
   Replace the connection name with the one configured in Create a Data Connection in Qlik Sense:

   LIB CONNECT TO 'Starburst Enterprise:Production'; 

2. Basic SQL SELECT

   Use three-part table names (catalog.schema.table) in all Trino SQL statements:

   Customers:
   SQL SELECT
       customer_id,
       customer_name,
       region,
       created_date
   FROM hive.sales.customers
   WHERE created_date >= DATE '2024-01-01';

3. Joining Tables

   Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume:

   Orders:
   SQL SELECT
       o.order_id,
       o.customer_id,
       o.order_date,
       o.total_amount,
       c.customer_name,
       c.region
   FROM hive.sales.orders o
   JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

4. Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

   LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

   Transactions:
   SQL SELECT *
   FROM hive.sales.transactions
   WHERE transaction_date >= DATE '$(vLastLoadDate)';

Trino SQL Compatibility Notes

Starburst Enterprise uses the Trino query engine. The same Trino SQL conventions apply as for Starburst Galaxy:

Differences vs. Starburst Galaxy

The table below summarises the key differences between the two deployment models relevant to a Qlik Sense integration:

Troubleshooting

Connection fails in QMC

• Verify the DSN name matches exactly (case-sensitive) in the data connection configuration.
• Confirm the Qlik Sense service account has Read permission on the Windows registry key for the System DSN.
• Check that the configured TCP port (8443 or 8080) is open outbound from the Qlik Sense server to the Starburst Enterprise coordinator.
• If using HTTPS, verify that the Starburst Enterprise TLS certificate or its CA is trusted by the Windows server certificate store.

Kerberos authentication failures

• Confirm that the krb5.ini file exists at C:\Windows\krb5.ini and contains the correct KDC settings for your domain.
• Verify that the Qlik Sense Windows service is running as a domain account (not Local System) with a valid Kerberos principal.
• Test Kerberos connectivity separately using the kinit utility before diagnosing ODBC issues.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive in some catalogs.
• Confirm the Starburst user account has SELECT privileges on the target table.
• Test the same SQL in the Starburst Enterprise query interface before embedding it in the Qlik load script.

Slow load performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses.
• Select only required columns rather than using SELECT *.
• Review the Starburst Enterprise query history to identify slow-running queries and optimise at the catalog/connector level.

Related Content and References

• Starburst Galaxy documentation
• Qlik ODBC connector documentation

Environment

• Qlik Sense Enterprise on Windows

This article describes how to connect Qlik Cloud Analytics to Starburst Enterprise (self-managed, on-premises, or private cloud) using a Qlik Data Gateway - Direct Access and the Starburst ODBC driver. It covers gateway installation and registration, ODBC driver and DSN configuration on the gateway host, TLS certificate handling for self-managed deployments, and data connection setup in Qlik Cloud. It is intended for Qlik Cloud tenants that need to query Starburst Enterprise catalogs directly from Qlik Cloud apps and scripts.

Content

• Architecture Overview
• Prerequisites
• Qlik Data Gateway - Direct Access Requirement
• Install the Starburst ODBC Driver on the Gateway Host
• Configure TLS Certificate Trust on the Gateway Host
• Configure an ODBC DSN on the Gateway Host
• Install and Register the Qlik Data Gateway - Direct Access
• Create a Data Connection in Qlik Cloud
• Load Script Patterns
• Trino SQL Compatibility Notes
• Comparison: Starburst Enterprise vs. Starburst Galaxy
• Troubleshooting
• Related Content and References

Architecture Overview

Qlik Cloud Analytics is a fully managed SaaS platform. Because Starburst Enterprise runs within a customer-managed network, a Qlik Data Gateway - Direct Access must be deployed within the same network as, or with routable access to, the Starburst Enterprise coordinator node. The gateway acts as a secure proxy, relaying data load requests from Qlik Cloud to Starburst Enterprise over the ODBC connection configured on the gateway host.

The connection flow will look as follows:

Qlik Cloud tenant → Qlik Data Gateway (Direct Access) → Starburst ODBC DSN → Starburst Enterprise coordinator

The gateway host is a Windows or Linux server that you manage. It must have outbound HTTPS access to both the Qlik Cloud tenant (port 443) and the Starburst Enterprise coordinator (port 8443 for HTTPS, or 8080 for HTTP). The gateway is typically deployed inside the same private network as the Starburst Enterprise cluster.

Prerequisites

Before beginning, ensure the following requirements are met:

• A Qlik Cloud tenant with a Qlik Cloud Analytics subscription.
• Tenant Admin or Space Admin rights in Qlik Cloud to create data connections.
• A dedicated Windows or Linux server to host the Qlik Data Gateway - Direct Access (minimum: 4 vCPU, 8 GB RAM, Windows Server 2016+ or RHEL/Ubuntu 20.04+), deployed inside or with routable access to the Starburst Enterprise network.
• Network connectivity from the gateway host to the Starburst Enterprise coordinator node (port 8443 for HTTPS, or 8080 for HTTP).
• Outbound HTTPS access (port 443) from the gateway host to your Qlik Cloud tenant URL (e.g. https://<tenant>.us.qlikcloud.com).
• The Starburst Enterprise TLS certificate or CA certificate chain (if using HTTPS with a self-signed or private CA certificate), to be imported into the Windows certificate store on the gateway host.
• A Starburst Enterprise user account with SELECT privileges on the target catalog and schema.
• Administrator access on the gateway host to install software, configure ODBC System DSNs, and manage the Windows certificate store.

Qlik Data Gateway - Direct Access Requirement

A Qlik Data Gateway - Direct Access is required to connect Qlik Cloud Analytics to Starburst Enterprise. Unlike Qlik Sense on Windows (client-managed), Qlik Cloud does not execute data load scripts directly. All connections to on-premises or privately hosted data sources are routed through the gateway.

A Qlik Data Gateway - Direct Access must be installed and registered to your Qlik Cloud tenant before a Starburst ODBC data connection can be created or used. Attempting to create the connection without a registered gateway will result in an error.

Because Starburst Enterprise runs inside a customer-managed network, the gateway host is typically deployed within that same network. This ensures the gateway can reach the Starburst Enterprise coordinator without requiring firewall rules that expose the coordinator to the public internet.

The gateway must be installed on a host that:

• Has network access to the Starburst Enterprise coordinator on the configured port (8443 for HTTPS or 8080 for HTTP).
• Has the Starburst Enterprise ODBC driver been installed and a System DSN configured (see Install the Starburst ODBC Driver on the Gateway Host, and Configure an ODBC DSN on the Gateway Host).
• Has outbound HTTPS access to the Qlik Cloud tenant on port 443.
• Has the Starburst Enterprise TLS certificate or CA chain been trusted in its certificate store (see Configure TLS Certificate Trust on the Gateway Host).
• Runs continuously. The gateway must be active whenever a Qlik Cloud app or script loads data from Starburst.

blockquote For high availability, install the gateway on two or more hosts within the Starburst Enterprise network and register all of them to the same Qlik Cloud tenant. Qlik Cloud will distribute data load requests across available gateway instances.

Install the Starburst ODBC Driver on the Gateway Host

The Starburst ODBC driver must be installed on the gateway host, not on the Qlik Cloud infrastructure. Qlik Cloud reads data through the gateway, so the driver must be present and configured where the gateway is running.

Download the Driver

Use the Starburst Enterprise-specific ODBC driver build, not the Starburst Galaxy driver.

1. Log in to the Starburst Enterprise software portal or obtain the driver package from your Starburst account representative.
2. Download the Windows 64-bit ODBC driver package (.msi) that matches your Starburst Enterprise version.
3. Copy the installer to the gateway host.

Install the Driver

1. Run the installer as a local administrator on the gateway host.
2. Accept the licence agreement and choose the default installation directory.
3. When prompted, select System DSN scope so that the Qlik Data Gateway service account can access the driver.
4. Complete the installation. No restart is required.

Install the 64-bit driver on the gateway host. The Qlik Data Gateway - Direct Access runs as a 64-bit process and requires the 64-bit ODBC driver. Use ODBC Data Source Administrator (64-bit) for all DSN configuration.

Configure TLS Certificate Trust on the Gateway Host

Starburst Enterprise deployments commonly use HTTPS with a certificate signed by a private or internal CA. Unlike Starburst Galaxy, whose certificate is signed by a publicly trusted CA, the Starburst Enterprise certificate chain may not be automatically trusted by Windows. The certificate must be imported into the Windows certificate store on the gateway host before the ODBC DSN can establish a TLS connection.

Obtain the Certificate

1. Obtain the Starburst Enterprise TLS certificate or the root CA certificate that signed it from your Starburst Enterprise administrator.
2. The certificate file is typically in PEM (.pem, .crt) or DER (.cer) format.
3. Copy the certificate file to the gateway host.

Import the Certificate into the Windows Certificate Store

1. Open the Microsoft Management Console (MMC) on the gateway host: press Win + R, type mmc, and press Enter.
2. In MMC, select File > Add/Remove Snap-in.
3. Add the Certificates snap-in and select Computer account when prompted.
4. Navigate to Trusted Root Certification Authorities > Certificates.
5. Right-click and select All Tasks > Import.
6. Follow the Certificate Import Wizard to import the Starburst Enterprise CA certificate.
7. Confirm the certificate appears in the Trusted Root Certification Authorities store.

If the Starburst Enterprise deployment uses a certificate signed by an intermediate CA, import the full chain: the root CA certificate and any intermediate CA certificates. Importing only the leaf (server) certificate is not sufficient for TLS validation.

Verify Certificate Trust

After importing the certificate, verify that the gateway host trusts the Starburst Enterprise endpoint by opening a browser on the gateway host and navigating to the coordinator URL (such as https://<coordinator-host>:8443). If the page loads without a certificate warning, the certificate chain is trusted correctly.

This step is only required for HTTPS deployments with private or self-signed certificates. It is not applicable for Starburst Enterprise using a certificate signed by a publicly trusted CA (such as Let's Encrypt, DigiCert).

Configure an ODBC DSN on the Gateway Host

A System DSN must be created on the gateway host. This is the DSN that Qlik Cloud will reference when the data connection is used in a load script or app.

1. Open ODBC Data Source Administrator (64-bit) on the gateway host.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the driver list and click Finish.

4. Configure the DSN with the following settings:

   Setting	Value
   DSN Name	StarburstEnterprise (must match the name used when creating the Qlik Cloud data connection)
   Host	<coordinator-hostname-or-ip>
   Port	8443 (HTTPS) or 8080 (HTTP — not recommended for production)
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP, Kerberos, or password (depends on Starburst Enterprise configuration)
   SSL	Enabled for HTTPS deployments; disabled for HTTP-only test environments
   SSL Certificate	Use the system certificate store (after completing Configure TLS Certificate Trust on the Gateway Host)

    

5. Click Test Connection to verify connectivity from the gateway host to the Starburst Enterprise coordinator. A successful test returns the Starburst Enterprise version.
6. Click OK to save the DSN.

Test the DSN connection while logged in as the same Windows service account that will run the Qlik Data Gateway service. DSN access permissions are per-user for User DSNs and per-machine for System DSNs. Always use System DSN for service accounts.

If Kerberos authentication is required, ensure the Qlik Data Gateway service account has a valid Kerberos principal and that the Kerberos configuration file (krb5.ini) is present at C:\Windows\krb5.ini on the gateway host before configuring the DSN.

Install and Register the Qlik Data Gateway - Direct Access

The Qlik Data Gateway - Direct Access installer is downloaded from the Qlik Cloud Administration Center and registers the gateway to your tenant during installation. The gateway itself is product-agnostic, meaning the installation steps are identical for Starburst Galaxy and Starburst Enterprise connections. 

Download the Installer

1. In Qlik Cloud, open the Qlik Cloud Administration activity center
2. Navigate to Data Gateways.
3. Click Add and select Direct Access Gateway.
4. Follow the on-screen instructions to download the installer for the gateway host operating system.

Install the Gateway

1. Copy the installer to the gateway host.
2. Run the installer as a local administrator.
3. When prompted, enter the Qlik Cloud tenant URL and an API key.
   
   See Generating and managing API keys for instructions on how to generate an API key.
   
   
4. Complete the installation. The gateway service will start automatically and register with the Qlik Cloud tenant.

Verify the Gateway is Registered

1. Return to the Qlik Cloud Administration activity center > Data Gateways.
2. Confirm the gateway appears in the list with a Connected status.
3. If the gateway shows a Disconnected status, check outbound HTTPS connectivity from the gateway host to the tenant URL on port 443.

The gateway service runs under a Windows service account (or as a systemd service on Linux). Ensure this account has Read access to the System DSN registry keys and is granted Log on as a service rights on Windows. For Kerberos authentication, the service account must also have a valid Kerberos ticket.

Create a Data Connection in Qlik Cloud

Once the gateway is registered and the ODBC DSN is configured on the gateway host, create the ODBC data connection in Qlik Cloud.

1. In Qlik Cloud, go to Create
2. Choose Data connection from the available actions and choose your Space
3. In the connector list, search for and select ODBC.
4. In the connection configuration panel, set the following:
   
   

   Field	Value
   Data gateway	Select the Direct Access Gateway registered in Install and Register the Qlik Data Gateway - Direct Access
   DSN	StarburstEnterprise (the System DSN configured on the gateway host in Configure an ODBC DSN on the Gateway Host)
   Username	Starburst Enterprise user account username (leave blank for Kerberos SSO)
   Password	Starburst Enterprise user account password (leave blank for Kerberos SSO)
   Connection name	Administrator-defined (e.g. Starburst Enterprise:Production)

5. Click Create.
6. Test the connection. The test runs through the gateway, confirming end-to-end connectivity from Qlik Cloud through the gateway to Starburst Enterprise. 

Unlike Starburst Galaxy, the connection name for Starburst Enterprise is administrator-defined and can reflect the deployment environment (e.g. Starburst Enterprise:Production, Starburst Enterprise:Staging). Ensure the name is used consistently in all load scripts that reference this connection.

Load Script Patterns

Load scripts in Qlik Cloud apps use the same patterns as Qlik Sense on Windows. The LIB CONNECT TO connection name must match the data connection created in Create a Data Connection in Qlik Cloud.

Establish the Connection

Replace the connection name with the one configured in Create a Data Connection in Qlik Cloud:

LIB CONNECT TO 'Starburst Enterprise:Production'; 

Basic SQL SELECT

Use three-part table names (catalog.schema.table) in all Trino SQL statements:

Customers:
SQL SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM hive.sales.customers
WHERE created_date >= DATE '2024-01-01';

Joining Tables

Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume through the gateway:

Orders:
SQL SELECT
    o.order_id,
    o.customer_id,
    o.order_date,
    o.total_amount,
    c.customer_name,
    c.region
FROM hive.sales.orders o
JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

Incremental Load

Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

Transactions:
SQL SELECT *
FROM hive.sales.transactions
WHERE transaction_date >= DATE '$(vLastLoadDate)';

Avoiding Synthetic Keys

Rename non-key fields that share names across tables by prefixing the table name. Island tables should be commented out:

Orders:
SQL SELECT
    order_id,
    customer_id, // Key — keep as-is
    order_date AS Order_order_date, // Renamed to avoid synthetic key
    total_amount AS Order_total_amount
FROM hive.sales.orders;

In Qlik Cloud, scheduled reloads run through the gateway. Ensure the gateway service is running and the gateway host has network access to the Starburst Enterprise coordinator at the time scheduled reloads are triggered.

Trino SQL Compatibility Notes

Starburst Enterprise uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed in all Qlik load script SQL statements:

Comparison: Starburst Enterprise vs. Starburst Galaxy

The table below summarises the key differences in the Qlik Cloud connection setup between Starburst Enterprise and Starburst Galaxy:

Troubleshooting

Gateway shows Disconnected in Qlik Cloud

• Verify outbound HTTPS connectivity from the gateway host to the Qlik Cloud tenant URL on port 443.
• Check that the gateway service is running: in Windows Services, look for Qlik Data Gateway - Direct Access.
• Review the gateway log files at %ProgramData%\Qlik\DataGateway\logs for connection errors.
• Confirm the API key used during registration has not been revoked in Qlik Cloud.

Data connection test fails: DSN not found

• Confirm the DSN name in the Qlik Cloud data connection matches exactly (case-sensitive) the System DSN name on the gateway host.
• Open ODBC Data Source Administrator (64-bit) on the gateway host and verify the DSN exists under the System DSN tab.
• Ensure the Qlik Data Gateway service account has access to the System DSN. Restart the gateway service after creating or modifying the DSN.

Data connection test fails: SSL/TLS error

• Confirm that the CA certificate chain for the Starburst Enterprise deployment has been imported into the Trusted Root Certification Authorities store on the gateway host.
• The test connection runs on the gateway host, not in Qlik Cloud. All certificate issues must be resolved on the gateway host.
• Verify that the SSL Certificate setting in the DSN is set to use the system certificate store, not a specific file path that may no longer be valid.

Kerberos authentication failures

• Confirm that the krb5.ini file exists at C:\Windows\krb5.ini and contains the correct KDC and realm settings for your domain.
• Verify that the Qlik Data Gateway Windows service is running as a domain account (not Local System) with a valid Kerberos principal.
• Test Kerberos connectivity separately using the kinit utility before diagnosing ODBC issues.
• After any changes to krb5.ini or the service account configuration, restart the Qlik Data Gateway service.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct. Catalog, schema, and table names are case-sensitive.
• Confirm the Starburst Enterprise user account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst Enterprise query interface before embedding it in the Qlik load script.

Scheduled reload fails, but manual reload succeeds

• Scheduled reloads run through the gateway under the service account context. Ensure the gateway service account has the same DSN access and Kerberos credentials as the interactive user.
• Verify the gateway is in a Connected state at the time the reload is scheduled.
• Check the Qlik Cloud reload log for gateway timeout errors and increase the gateway connection timeout if necessary.

Slow reload performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses. All data passes through the gateway, so minimising row count reduces transfer time.
• Select only required columns rather than using SELECT *.
• Consider co-locating the gateway host in the same network segment as the Starburst Enterprise coordinator to minimise latency.
• Review the Starburst Enterprise query history to identify slow-running queries and optimise at the catalog or connector level.

Related Content and References

• Qlik Data Gateway - Direct Access documentation 
• Starburst Enterprise documentation 
• Qlik Cloud Data Sources

Environment

• Qlik Cloud

This article describes how to connect Qlik Cloud Analytics to Starburst Galaxy using a Qlik Data Gateway - Direct Access and the Starburst ODBC driver. It covers gateway installation and registration, ODBC driver and DSN configuration on the gateway host, and data connection setup in Qlik Cloud. It is intended for Qlik Cloud tenants that need to query Starburst Galaxy catalogs directly from Qlik Cloud apps and scripts.

Content

• Architecture Overview
• Prerequisites
• Qlik Data Gateway - Direct Access Requirement
• Install the Starburst ODBC Driver on the Gateway Host
• Configure an ODBC DSN on the Gateway Host
• Install and Register the Qlik Data Gateway - Direct Access
• Create a Data Connection in Qlik Cloud
• Load Script Patterns
• Trino SQL Compatibility Notes
• Comparison: Qlik Cloud vs. Qlik Sense on Windows
• Troubleshooting
• Related Content and References

Architecture Overview

Qlik Cloud Analytics is a fully managed SaaS platform. Because Starburst Galaxy is not directly accessible from the Qlik Cloud infrastructure without network configuration, a Qlik Data Gateway - Direct Access must be deployed within the same network as, or with routable access to, the Starburst Galaxy cluster endpoint. The gateway acts as a secure proxy, relaying data load requests from Qlik Cloud to Starburst Galaxy over the ODBC connection configured on the gateway host.

The connection flow will look as follows:

Qlik Cloud tenant → Qlik Data Gateway (Direct Access) → Starburst ODBC DSN → Starburst Galaxy cluster

The gateway host is a Windows or Linux server that you manage. It must have outbound HTTPS access to both the Qlik Cloud tenant (port 443) and the Starburst Galaxy cluster endpoint (port 443).

Prerequisites

Before beginning, ensure the following requirements are met:

• A Qlik Cloud tenant with a Qlik Cloud Analytics subscription.
• Tenant Admin or Space Admin rights in Qlik Cloud to create data connections.
• A dedicated Windows or Linux server to host the Qlik Data Gateway - Direct Access (minimum: 4 vCPU, 8 GB RAM, Windows Server 2016+ or RHEL/Ubuntu 20.04+).

  A Qlik Data Gateway - Direct Access must be installed and registered to your Qlik Cloud tenant before a Starburst ODBC data connection can be created or used. Attempting to create the connection without a registered gateway will result in an error.

• Network connectivity from the gateway host to the Starburst Galaxy cluster endpoint (port 443, HTTPS/TLS).
• Outbound HTTPS access (port 443) from the gateway host to your Qlik Cloud tenant URL (such as https://<tenant>.us.qlikcloud.com).
• A Starburst Galaxy service account with SELECT privileges on the target catalog and schema.
• Administrator access on the gateway host to install software and configure ODBC System DSNs.

Qlik Data Gateway - Direct Access Requirement

A Qlik Data Gateway - Direct Access is required to connect Qlik Cloud Analytics to Starburst Galaxy. All connections to on-premises or privately hosted data sources are routed through the gateway.

The gateway must be installed on a host that:

• Has network access to the Starburst Galaxy cluster on port 443.
• Has the Starburst ODBC driver installed and a System DSN configured (see Install the Starburst ODBC Driver on the Gateway Host, and Configure an ODBC DSN on the Gateway Host).
• Has outbound HTTPS access to the Qlik Cloud tenant on port 443.
• Runs continuously. The gateway must be active whenever a Qlik Cloud app or script loads data from Starburst.

For high availability, install the gateway on two or more hosts and register all of them to the same Qlik Cloud tenant. Qlik Cloud will distribute data load requests across available gateway instances.

Install the Starburst ODBC Driver on the Gateway Host

The Starburst ODBC driver must be installed on the gateway host. Qlik Cloud reads data through the gateway, so the driver must be present and configured where the gateway is running.

1. Download the Driver
   1. Log in to your Starburst Galaxy account at https://galaxy.starburst.io.
   2. Navigate to Settings > Clients & Tools > Drivers.
   3. Download the Windows 64-bit ODBC driver package (.msi or .zip) appropriate for the gateway host operating system.
   4. Copy the installer to the gateway host.
2. Install the Driver
   1. Run the installer as a local administrator on the gateway host.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select System DSN scope so that the Qlik Data Gateway service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver on the gateway host. The Qlik Data Gateway - Direct Access runs as a 64-bit process and requires the 64-bit ODBC driver. Use ODBC Data Source Administrator (64-bit) for all DSN configuration.

Configure an ODBC DSN on the Gateway Host

A System DSN must be created on the gateway host. This is the DSN that Qlik Cloud will reference when the data connection is used in a load script or app.

1. Open ODBC Data Source Administrator (64-bit) on the gateway host.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the driver list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstGalaxy (must match the name used when creating the Qlik Cloud data connection)
   Host	<your-cluster>.galaxy.starburst.io
   Port	443
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP (username/password) or OAuth2 (token)
   SSL	Enabled (required for Galaxy)
   SSL Certificate	Use system certificate store

5. Click Test Connection to verify connectivity from the gateway host to Starburst Galaxy. A successful test returns the Starburst Galaxy version. 
6. Click OK to save the DSN.

Test the DSN connection while logged in as the same Windows service account that will run the Qlik Data Gateway service. DSN access permissions are per-user for User DSNs and per-machine for System DSNs. Always use System DSN for service accounts.

Install and Register the Qlik Data Gateway - Direct Access

The Qlik Data Gateway - Direct Access installer is downloaded from the Qlik Cloud Administration activity center and registers the gateway to your tenant during installation.

1. Download the Installer
   1. In Qlik Cloud, open the Qlik Cloud Administration activity center.
   2. Navigate to Data Gateways.
   3. Click Add and select Direct Access Gateway.
   4. Follow the on-screen instructions to download the installer for the gateway host operating system.
2. Install the Gateway
   1. Copy the installer to the gateway host.
   2. Run the installer as a local administrator.
   3. When prompted, enter the Qlik Cloud tenant URL and your API key.
      
      See Generating and managing API keys for instructions on how to generate an API key.
      
      
   4. Complete the installation. The gateway service will start automatically and register with the Qlik Cloud tenant.
3. Verify the Gateway is registered
   1. Return to the Qlik Cloud Administration activity center > Data Gateways.
   2. Confirm the gateway appears in the list with a Connected status.
      If the gateway shows a Disconnected status, check outbound HTTPS connectivity from the gateway host to the tenant URL on port 443.

The gateway service runs under a Windows service account (or as a systemd service on Linux). Ensure this account has Read access to the System DSN registry keys and is granted Log on as a service rights on Windows.

Create a Data Connection in Qlik Cloud

Once the gateway is registered and the ODBC DSN is configured on the gateway host, create the ODBC data connection in Qlik Cloud.

1. In Qlik Cloud, go to Create
2. Choose Data connection from the available actions and choose your Space
3. In the connector list, search for and select ODBC.
4. In the connection configuration panel, set the following:
   
   

   Field	Value
   Data gateway	Select the Direct Access Gateway registered in Install and Register the Qlik Data Gateway - Direct Access
   DSN	StarburstGalaxy (the System DSN configured on the gateway host in Configure an ODBC DSN on the Gateway Host)
   Username	Starburst Galaxy service account username
   Password	Starburst Galaxy service account password or personal access token
   Connection name	Data Nova Conference:Starburst Galaxy

5. Click Create.
6. Use the Test button to verify the connection. The test runs through the gateway, confirming end-to-end connectivity.

The connection name Data Nova Conference:Starburst Galaxy is the canonical name used in all Qlik load scripts for this integration. Changing it requires updating all dependent scripts. This name is consistent across Qlik Sense Enterprise on Windows and Qlik Cloud (this article).

Load Script Patterns

Load scripts in Qlik Cloud apps use the same patterns as Qlik Sense on Windows. The LIB CONNECT TO connection name must match the data connection created in Create a Data Connection in Qlik Cloud.

Establish the Connection

Always use the following statement at the top of the load script tab that accesses Starburst Galaxy:

LIB CONNECT TO 'Data Nova Conference:Starburst Galaxy'; 

Basic SQL SELECT

Use three-part table names (catalog.schema.table) in all Trino SQL statements:

Customers:
SQL SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM hive.sales.customers
WHERE created_date >= DATE '2024-01-01';

Joining Tables

Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume through the gateway:

Orders:
SQL SELECT
    o.order_id,
    o.customer_id,
    o.order_date,
    o.total_amount,
    c.customer_name,
    c.region
FROM hive.sales.orders o
JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

Incremental Load

Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

Transactions:
SQL SELECT *
FROM hive.sales.transactions
WHERE transaction_date >= DATE '$(vLastLoadDate)';

Avoiding Synthetic Keys

Rename non-key fields that share names across tables by prefixing the table name. Island tables should be commented out:

Orders:
SQL SELECT
    order_id,
    customer_id, // Key — keep as-is
    order_date AS Order_order_date, // Renamed to avoid synthetic key
    total_amount AS Order_total_amount
FROM hive.sales.orders;

In Qlik Cloud, scheduled reloads run through the gateway. Ensure the gateway service is running and the gateway host has network access to Starburst Galaxy at the time scheduled reloads are triggered.

Trino SQL Compatibility Notes

Starburst Galaxy uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed in all Qlik load script SQL statements:

Comparison: Qlik Cloud vs. Qlik Sense on Windows

The table below summarises the key differences in the Starburst connection setup between Qlik Cloud Analytics and Qlik Sense Enterprise on Windows (client-managed):

Troubleshooting

Gateway shows Disconnected in Qlik Cloud

• Verify outbound HTTPS connectivity from the gateway host to the Qlik Cloud tenant URL on port 443.
• Check that the gateway service is running: in Windows Services, look for Qlik Data Gateway - Direct Access.
• Review the gateway log files at %ProgramData%\Qlik\DataGateway\logs for connection errors.
• Confirm the API key used during registration has not been revoked in Qlik Cloud.

Data connection test fails: DSN not found

• Confirm the DSN name in the Qlik Cloud data connection matches exactly (case-sensitive) the System DSN name on the gateway host.
• Open ODBC Data Source Administrator (64-bit) on the gateway host and verify the DSN exists under the System DSN tab.
• Ensure the Qlik Data Gateway service account has access to the System DSN. Restart the gateway service after creating or modifying the DSN.

Data connection test fails: SSL/TLS error

• Confirm that the Windows certificate store on the gateway host trusts the CA certificate chain for *.galaxy.starburst.io.
• The test connection runs on the gateway host, not in Qlik Cloud. All certificate issues must be resolved on the gateway host.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct. Catalog, schema, and table names are case-sensitive.
• Confirm the Starburst Galaxy service account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst Galaxy Query Editor before embedding it in the Qlik load script.

Scheduled reload fails, but manual reload succeeds

• Scheduled reloads run through the gateway under the service account context. Ensure the gateway service account has the same DSN access as the interactive user.
• Verify the gateway is in a Connected state at the time the reload is scheduled.
• Check the Qlik Cloud reload log for gateway timeout errors and increase the gateway connection timeout if necessary.

Slow reload performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses. All data passes through the gateway, so minimising row count reduces transfer time.
• Select only required columns rather than using SELECT *.
• Consider co-locating the gateway host in the same network region as the Starburst Galaxy cluster to minimise latency.

Related Content and References

• Qlik Data Gateway - Direct Access documentation 
• Starburst Galaxy documentation 
• Qlik Cloud Data Sources

Environment

• Qlik Cloud

Is Qlik Sense Enterprise on Windows affected by the security vulnerability CVE-2023-26136 (nvd.nist.gov)?

CVE-2023-26136 is a vulnerability detected in Node.js, a third-party component used by Qlik Sense Enterprise on Windows. Security scans may flag the vulnerability in a Qlik Sense Enterprise on Windows environment. 

While Qlik was not directly impacted, the affected third-party component has been updated across supported versions.

Qlik Sense versions up to the following would be flagged by security scans: 

• Qlik Sense Enterprise on Windows May 2024 patch 23
• Qlik Sense Enterprise on Windows November 2024 patch 17
• Qlik Sense Enterprise on Windows May 2025 patch 5 

Resolution

Upgrade to any of the following (or later) versions:

• Qlik Sense Enterprise on Windows May 2024 patch 24
• Qlik Sense Enterprise on Windows November 2024 patch 18
• Qlik Sense Enterprise on Windows May 2025 patch 6 
• Qlik Sense Enterprise on Windows November 2025 IR, and all subsequent versions, such as May 2026 IR and upward

In some instances, the Qlik Sense patch installer updates service binaries but does not remove leftover node_modules folders from previous installations. The old request/node_modules/tough-cookie directories may still exist on disk even though the running service no longer uses them.

If you notice stale folders post-upgrade:

1. Run the following PowerShell script as Administrator to clean up stale folders:
   
   

   # Qlik Sense - tough-cookie stale folder cleanup
   # Run as Administrator after upgrading to v14.231.26 or later
   # Take a backup or snapshot before running
   Write-Host "Starting tough-cookie cleanup..." -ForegroundColor Cyan
   # Step 1 - Stop Service Dispatcher (this will stop all dependent Qlik Sense
   services)
   Stop-Service -Name "QlikSenseServiceDispatcher" -Force -ErrorAction
   SilentlyContinue
   Write-Host "Stopped: QlikSenseServiceDispatcher" -ForegroundColor Yellow
   Start-Sleep -Seconds 5
   # Step 2 - Remove tough-cookie directories
   $paths = @(
   "C:\Program Files\Qlik\Sense\ConverterService\node_modules\tough-cookie",
   "C:\Program
   Files\Qlik\Sense\DownloadPrepService\node_modules\request\node_modules\tough
   cookie",
   "C:\Program
   Files\Qlik\Sense\MobilityRegistrarService\node_modules\request\node_modules\tough
   cookie",
   "C:\Program
   Files\Qlik\Sense\NotifierService\node_modules\request\node_modules\tough-cookie"
   )
   foreach ($path in $paths) {
   if (Test-Path $path) {
   Remove-Item -Path $path -Recurse -Force
   Write-Host "Removed: $path" -ForegroundColor Green
   } else {
   Write-Host "Not found (already clean): $path" -ForegroundColor Gray
   }
   }
   Write-Host "`nCleanup complete. Restart Service Dispatcher manually to bring all
   services back online." -ForegroundColor Cyan​

   This script may need to be re-run after any future Qlik Sense Enterprise on Windows patch or reinstallation, as the installer may restore these directories.

   The script is provided as is and to be used at your own risk.

2. Restart the Qlik Sense Service Dispatcher service

Internal Investigation ID(s)

• SUPPORT-2237

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Configuration:

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they 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 applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

The Qlik Sense on Windows Content Monitor is intended for Qlik Administrators. Its purpose is to monitor and analyze your Qlik Sense content, including app usage, resource consumption, and data sources. This helps with governance, optimization, and identifying unused content.

Requirements

• Platform: Qlik Sense Enterprise on Windows
• Version: November 2025 onwards 
• Availability: Bundled with installation from version November 2025 onwards
• If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page)
  • This must be manually installed, and a weekly reload is recommended.
  • The downloaded version is supported from Qlik Sense version Feb 2020.

Core Documentation

All technical details can be found in the two attached documents. These are your primary resources.

Qlik Sense Content Monitor User Guide

• • What it covers: A detailed, sheet-by-sheet explanation of the entire app. It describes what every KPI, chart, and table means for sections like "Weekly Summary," "Snapshot," "Applications," "Sessions," "Task Executions," "File Inventory," and "Infrastructure."

  • Use Case: 

    • Guiding a customer on how to read and interpret the data.

    • Answering customer questions like, "What does the 'Session Concurrency' sheet show?" or "How do I read the 'File Inventory' sheet?"

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

• • What it covers: This is the primary guide for setup and reload issues. It contains:

    • Detailed definitions for all script parameters (e.g., vCentralNodeHostName, vVirtualProxyPrefix, vServerLogFolder).

    • Performance tuning options (e.g., vFileScanMaxDuration, vAppRetrievalLoop, exclusion lists).

    • A "Trial Mode" section is used for troubleshooting initial reload failures.

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows