Logs are an important aspect of any production system. Logs can help you pinpoint the root cause of issues in any application, and gathering all this crucial data into a single dashboard substantially increases productivity.

Some of the benefits of log management and monitoring are:

• Centralize log data

• Improve system performance

• Time-efficient monitoring

• Efficient issue troubleshooting

• Assess application health

• Diagnose and identify runtime errors

This document describes the various ways and methods of how log management and monitoring can be done in Talend Cloud, for example, leveraging Elasticsearch, Logstash, and Kibana (ELK) and Talend Activity Monitoring Console (similar to on-premises in Talend Administration Center).

Content:

• Observability Metrics with Talend Cloud and Remote Engine
• Methods of Logging
• Viewing and searching the Job logs from Talend Management Console
• Logs in Talend Remote Engines
• Saving execution logs to the Amazon S3 bucket
• Redirecting the logs using Filebeat
• Redirecting the logs to JMS
• Studio Logs
• Methods of Monitoring
• Kibana dashboard
• Activity Monitoring Console using a visualization tool
• Activity Monitoring Console in Talend Studio
• Appendices
• Conclusion

Observability Metrics with Talend Cloud and Remote Engine

In addition to the methods listed in this article, see also:  How to configure observability metrics with Talend Cloud and Remote Engine. 

Methods of Logging

Talend Cloud offers two types of logs:

• Execution logs: the task and plan logs provide details about the execution, such as messages, severity, timestamps, and versions. These logs can be used to analyze and debug tasks or plans.

• Engine logs: can be configured to give technical details at INFO, WARN, ERROR, or FATAL log level.

These logs are accessible in several ways. This article shows two examples for redirecting the logs to Filebeat and Java Message Service (JMS). However, you can redirect the Remote Engine logs to the tool of your choice, like Splunk or Datadog.

Viewing and searching the Job logs from Talend Management Console

1. Go to OPERATIONS.

2. Filter on the environment/workspace/operator/time period at the top of the page.

   

3. Select the corresponding status of the execution to retrieve the logs for the following:

   • Current

   • Failed

   • Rejected

   • Terminated

   • Successful

4. Expand the task execution to view details and possible actions.

5. Click VIEW LOGS.

6. Download the logs from Talend Management Console.

   1. Go to OPERATIONS.

   2. Filter on the environment/workspace/operator/time.

   3. Select the task execution to download and VIEW LOGS.

   4. Select DOWNLOAD > All to download all the logs independent of the filter selection.

   5. Select DOWNLOAD > Filter results to only download the results displayed for the current filters.

   6. To download a single log, click the Download icon above the log content.

       

Logs in Talend Remote Engines

• Every time a task/plan is executed from Talend Management Console, a check happens on the Remote Engine to see if the executables are available.

• If the binary exists, then it is executed; otherwise, the Remote Engine extracts the binary from the Repository. The binaries are stored in <Remote engine installation directory>\TalendJobServersFiles\archiveJobs.

  

• The execution logs are stored on the Remote Engine server in <remote engine installation directory>\TalendJobServersFiles\jobexecutions\logs.

• Each Job execution log folder has two files:

  • StdOutErr: this file contains log details corresponding to the console. The details from this file are retrieved and displayed in Talend Management Console logs.

  • Resuming: this file contains details of the events such as JOB_STARTED, SYSTEM_LOGS, and JOB_ENDED.

    

• Talend Remote Engine utilizes Apache Karaf containers. You can utilize these Karaf logs to get the details about your infrastructure like Remote Engine, Remote Engine Cluster, and Remote Engine connection to Talend Cloud. These logs are located under <remote engine installation directory>\data\log.

   

Saving execution logs to the Amazon S3 bucket

Currently, this feature is only available for Talend Cloud on AWS. For more information on how to configure the bucket, see Saving execution logs to an external Amazon S3 bucket in the Talend Help Center.

Saving logs to external AWS S3 buckets is the best way to gather and analyze Job logs, especially if you are using cloud engines.

1. Go to CONFIGURATION > MANAGEMENT CONSOLE.

2. Enable EXPORT LOGS.

   

3. On the Management Console Export Logs page, click the Cloud Formation template link to download the Talend Cloud AWS CloudFormation template.

   

4. Open your AWS account in a new tab, then start the Create Stack wizard on the AWS CloudFormation Console. In the Specify template section, select Upload a template to Amazon S3, then select the template provided by Talend Cloud.

   

5. Define the External ID, S3 bucket name, and S3 prefix.

   

6. Click Create. The stack is created. Copy the Role ARN key value from the Outputs tab.

7. Enter the details (Role ARN, External Id, and Bucket Name) from the steps above into the Talend Management Console.

8. The logs are saved to the S3 bucket.

    

Redirecting the logs using Filebeat

Filebeat is a lightweight collector for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them to either Elasticsearch or Logstash for indexing.

Filebeat can be used to redirect the Remote Engine logs to Elasticsearch.

There are numerous ways to redirect the logs. The previous section showed you how to redirect the logs to an S3 bucket. This section shows another category where Filebeat can be configured to redirect the on-premises Elasticsearch. However, you can setup Filebeat or another collector like App Metrics or Telegraf, according to your needs.

1. Download Filebeat from https://www.elastic.co/fr/downloads/beats.

   For more information, see the Getting Started with Filebeat documentation.

2. Edit the filebeat.yml configuration file to reflect the log files.

   - type: log
    # Change to true to enable this input configuration.
    enabled: true
    Paths that should be crawled and fetched. Glob based paths.
    paths:
       #- /var/log/*.log
        - C:\TalendRemoteEngine-240\TalendJobServersFiles\jobexecutions\logs\*\*
    
   output.elasticsearch:
     # Array of hosts to connect to.
     hosts: ["localhost:9200"]
    
   setup.kibana:
     # Kibana Host
     # Scheme and port can be left out and will be set to the default (http and 5601)
     # In case you specify and additional path, the scheme is required: http://localhost:5601/path
     # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
     host: "localhost:5601"

3. Install Filebeat by running the following commands:
   
   .\install-service-filebeat.ps1

   

4. To set up an index from Elasticsearch, use the following commands to create a template, set up a dashboard, and start Filebeat as a service:

   .\filebeat.exe setup --index-management -E output.logstash.enabled=false - E 'output.elasticsearch.hosts=["localhost:9700"]'
   
   Invoke-RestMethod -Method Delete "http://localhost:9200/filebeat-*"
   
   .\filebeat.exe export template --es.version 7.5.0 | Out-File -Encoding UTF8 filebeat.template.json
   
   Invoke-RestMethod -Method Put -ContentType "application/json" -InFile  filebeat.template.json -Uri http://localhost:9200/_template/filebeat-7.5.0
   
   .\filebeat.exe setup --dashboards
   
   Start-Service filebeat

   

5. Review the commands and their results in the Filebeat_commands file attached to this article.

6. Start Filebeat so that the logs are sent to your Elasticsearch engine.

    

Redirecting the logs to JMS

1. JMS is an API that provides the facility to create, send, and read messages. It provides loosely coupled, reliable, and asynchronous communication. JMS is also known as a messaging service.

2. Remote Engine logs can be routed to JMS. Once the logs are in JMS, they can be read and processed into another system like ELK.

3. Edit the remote-engine-installation/etc/org.talend.eventlogging.sender.jms.cfg file located in your Remote Engine installation folder.

   Your configuration should look similar to this:

   # JMS connection url
   sender.destination.jms. url = failover:(https://log.eu.cloud.talend.com:443)
   
   # Name of JMS queue
   sender.destination.jms.queue=event.logging.server
   
   # JMS Username
   sender.destination.jms.username = ################################
   
   # JMS Password
   sender.destination.jms. password = ################################
   
   sender.destination.jms.pool.maxConnections = 8

   

    

4. Update the destination.jms.url parameter to your JMS broker, in this case, localhost.
   
   

   # JMS connection url
   sender.destination.jms. url = failover:(tcp://localhost:61616)

   

    

5. Login to the ActiveMQ admin console. You should see a new queue, in this case, logging.server.

6. Open the logs to validate that the logs are the same as those on the Remote Engine.

    

Studio Logs

Talend Studio can be configured to store Job execution, statistics, performance information, and detailed technical logs. As described earlier in this article, these logs are extra information that can be enabled. The logs can be stored in delimited files or database tables.

The Job executions are monitored using three files or tables:

• Collection of logs

• Component statistics

• Data flow volume

1. To store this data, you need to create three files or database tables, respectively, using the schema of the tLogCatcher, tStatCatcher, and tFlowMeterCatcher components (available in the Palette of your Talend Studio).

   Note: For more information, see Creating files or database tables in the Talend Help Center.

2. To collect these logs, the Stats & Logs settings at the project-level, or the tStatsCatcher, tLogCatcher, and tFlowMeterCatcher components in individual Job need to be enabled.

   • To enable at the project-level, select File > Edit Project Properties > Project Settings. Expand the Job Settings node, then select Stats & Logs. Configure it either to a file or DB.

     

   • To enable at the Job-level, select the Job tab, then click Stats & Logs.

     

      

You can use the tStatCatcher, tLogCatcher, and tFlowMeterCatcher components as needed in the Job and link it to the relevant output (file or DB). After the data is available in the file or DB, you can use the Talend Activity Monitoring Console to analyze the data.

Methods of Monitoring

Now that you have seen the various ways to store Talend Logs, take a look at the different monitoring methods. You can monitor the Talend execution, engine, and project logs in one or all of the following:

Kibana dashboard

• A Kibana dashboard is a collection of visualizations, searches, and maps, typically in real-time. Dashboards provide at-a-glance insights into your data and enable you to drill-down into the details.

• After you have the logs stored in your Elasticsearch engine, utilize the indexes to create a dashboard in Kibana.

• You can create as many templates as needed to monitor the Jobs, status, time details, and more.

Activity Monitoring Console using a visualization tool

• Talend Activity Monitoring Console is an add-on tool integrated into Studio for monitoring Talend Jobs and projects.

• After Studio is configured, use the Activity Monitoring Console (as described in the Studio Logs section of this article), to visualize the data.

• The Activity Monitoring Console can only connect to the configured DB/File. It cannot connect to a Remote Engine or any other types of Logs. Thus it would only show the exact metrics, logs, stats that are generated and loaded into the DB/File.

• Talend Activity Monitoring Console helps Talend product administrators or users to achieve improved process performances through a convenient graphical interface and a supervising tool.

• As the logs are stored in either DB/File, plugging it to an external visualization tool like Tableau or MicroStrategy, becomes very easy.

• The following example shows two reports:

  1. Error message by the components in a Job:

     

      

  2. Success/Failure for each Job in 2019 along with the execution details:

     

      

Activity Monitoring Console in Talend Studio

The Activity Monitoring Console dashboards can be accessed using Talend Studio.

• You can access the reports dashboard in the Activity Monitoring Console perspective.

  For more information, see Accessing the monitoring console from the Studio available in the Talend Help Center.

• The following views can be created in the DB.

  • Jobs view

  • History and Detailed history views

  • Meter log view

  • Main chart view

  • Job Volume view

  • Logged Events view

  • Error report view

  • Threshold Charts view

Appendices

ELK with Talend Cloud

This blog is available at https://www.talend.com/blog/2019/09/09/elk-with-talend-cloud/

Introduction to Talend Activity Monitoring Console

Available in the Talend Help Center at https://help.talend.com/reader/aDkYRyut3Bh1Oo4YpBffEg/KtKEN~LTk82alp6_uaMrsg

Redirecting Talend Cloud logs to a JMS

Available in the Talend Community Knowledge Base (KB) at https://community.talend.com/t5/Design-and-Development/Redirecting-Talend-Cloud-logs-to-a-JMS/ta-p/152486

Conclusion

In summary, the various logging and monitoring capabilities offered by Talend are:

• Viewing logs in Talend Management Console
• Accessing the Remote Engine logs and pushing them to ELK
• Routing Remote Engine logs to Logstash/Elasticsearch using Filebeat
• Accessing Job logs from the AWS S3 bucket and pushing them to ELK (very useful if cloud engines are being used)
• Enabling statistics on Job execution (tStatCatcher, tLogCatcher, tFlowMeterCatcher) at project-level or Job-level then saving it to DB/Files (this data can be utilized using the Activity Monitoring Console in Talend Studio)
• Enabling data from DB/File for the Activity Monitoring Console to be visualized using external tools such as Tableau and MicroStrategy
• Routing the Remote Engine logs using JMS
• Routing the Remote Engine logs using Filebeat

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

Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433.

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

Qlik NPrinting installs Erlang OTP as part of the RabbitMQ installation, which is essential to the correct functioning of the Qlik NPrinting services.

RabbitMQ does not use SSH, meaning the workaround documented in Unauthenticated Remote Code Execution in Erlang/OTP SSH is already applied. Consequently, Qlik NPrinting remains unaffected by CVE-2025-32433.

All future Qlik NPrinting versions from the 20th of May 2025 and onwards will include patched versions of OTP and fully address this vulnerability.

Environment

• Qlik NPrinting

This article is currently under review.

This article explains how to extract changes from a Change Store and store them in a QVD by using a load script in Qlik Analytics. 

The article also includes

• An app example with an incremental load script that will store new changes in a QVD
• Configuration instructions for the examples

Scenario

This example will create an analytics app for Vendor Reviews. The idea is that you, as a company, are working with multiple vendors. Once a quarter, you want to review these vendors.

The example is simplified, but it can be extended with additional data for real-world examples or for other “review” use cases like employee reviews, budget reviews, and so on.

The data model

The app’s data model is a single table “Vendors” that contains a Vendor ID, Vendor Name, and City:

Vendors:
Load * inline [
"Vendor ID","Vendor Name","City"
1,Dunder Mifflin,Ghent
2,Nuka Cola,Leuven
3,Octan, Brussels
4,Kitchen Table International,Antwerp
];

The Write Table

The Write Table contains two data model fields: Vendor ID and Vendor Name. They are both configured as primary keys to demonstrate how this can work for composite keys.

The Write Table is then extended with three editable columns:

• Quarter (Single select)
• Action required? (Single select)
• Comment (Manual user input)

Prerequisites

• A shared space
• A managed space (optional but advised for the tutorial)
• A connection to the Change-stores API to the Analytics REST connector in the shared space. A step-by-step guide on creating this connection is available in Extracting write table changes with the REST connector in Qlik Cloud.

Steps

1. Upload the attached .QVF file to a shared space
2. Open the private sheet Vendor Reviews
3. Click the Reload App (A) button and make sure data appears (B) in the top table
   

   
   

4. Go to Edit sheet (A) mode
5. Drag a Write Table Chart (B) on the top table, and choose the option Convert to: Write Table (C).
   
   This transforms the table into a Write Table with two data model columns Vendor ID and Vendor Name.
   
   
   

    

6. Go to the Data section in the Write Table’s Properties menu and add an editable column
   
   
   

    

7. This prompts you to define a primary key inside the table. Click Define (A) in the table and use both Vendor ID and Vendor Name as primary keys (B).
   
   You can also just use Vendor ID, but we want to show that this also supports composite primary keys.
   
   
   
   
   
   
8. Configure the editable column:
   
   
   • Title: Quarter
   • Show content: Single selection
   • Add options for Q1Y26 through Q4Y26.
     
     Tip! Also add an empty option by clicking the Add button without specifying a value.
     
     
     

      

9. Add another Editable column with the below configuration
   
   
   • Title: Action required
   • Type: Single select
   • Options:  Yes and No
     
     

     

10. Add another Editable column with the below configuration
    
    
    • Title: Review
    • Type: Single select
    • Options:  Yes and No
      
      
      
      
11. The Write Table is now set up.
    
    Go to the Write Table’s properties and locate the Change store (A) section. Copy the Change store ID (B).
    
    
    

     

12. Leave the Edit sheet mode. Then add changes for at least two records. Save those changes.
    
    
    

     

13. Go to the app’s load script editor and uncomment the second script section by first selecting all lines in the script section (CTRL+A or CMD+A) (A) and then clicking the comment button (B) in the toolbar.
    
    
    

     

14. Configure the settings in the CONFIGURATION part at the end of the load script
    
    
    

     

15. Update the load script with the IDs of the editable columns.
    
    The easiest solution to get these IDs is to test your connection. Make sure the connection URL is configured to use the /changes/tabular-views endpoint and uses the correct change store ID.
    
    
    

     

16. Copy and paste the example load script (for the editable columns only) and paste it in the app’s load script SQL Select statement that starts on line 159:
    
    
    

     

17. Replace the corresponding * symbols in the LOAD statement that starts on line 176:
    
    
    

     

18. Choose which records you want to track in your table by configuring the Exists Key on line 216.
    
    This key will be used to filter the “granularity” on which we want to store changes in the QVD and data model, as the load script will only load unique existing keys (line 235).
    
    
    • $(vExistsKeyFormula) is a pipe-separated list of the primary keys.
    • In this example, Quarter is added as an additional part of the exists key to keep track of changes by Quarter.
    • Optionally, this can be extended with createdBy and updatedAt to extend the granularity to every change made:
      
      
      

       

19. Reload the app and verify that the correct change store table is created in your data model. The second table in the sheet should also successfully show vendors and their reviews.

Environment

• Qlik Cloud Analytics

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

At Qlik Connect 2025 I hosted a session called "Top 10 Visualization tips". Here's the app I used with all tips including test data.

Tip titles, more details in app:

• Open ended buckets
• Cyclic reset
• "Hidden" columns
• Labels in different sizes
• Others by Ack%
• Highlight over threshold
• Tooltip to other things
• Bar codes revisited
• Table tooltips
• More Pivot tooltips
• Max min
• Gradients and opacity with SVG
• Cluster map layer
• Standard deviation band
• Band chart in table
• Table with scaling text
• Font size for highlight
• Labels on bars
• Renaming map labels
• "Extra" columns in Pivot
• Vertical waterfall revisited
• Trellis respond to selection
• Radar with more than one measure
• Button with two lines of text
• Currencies
• Date range sliders
• Dotted line on forecast
• Nav menu tooltips
• Blinking KPI
• Color table headers

I want to emphasize that many of the tips were discovered by others than me, I tried to credit the original author at all places when possible.

If you liked it, here's more in the same style:

• 24 days of visualization Season III, II, I
• Top 10 Tips Part X, IX, VIII, VII, VI, V, IV, III, II , I 
• Let's make new charts with Qlik Sense
• FT Visual Vocabulary Qlik Sense version
• Similar but for Qlik GeoAnalytics : Part III,  II, I

Thanks,
Patric

During Change Data Capture (CDC) replication, the target Oracle database experienced a transient CPU spike.

Database performance monitoring identified that the high CPU consumption was driven by the following automated bulk query generated by Qlik Replicate:

UPDATE /*+ PARALLEL(tempview) */ ( SELECT /*+ PARALLEL("CDC"."CATB_ENTRIES_DECOUPLING") PARALLEL("QLIK_TARGET"."attrep_changes69C66930_0000001") */ ...

The underlying cause of the resource spike was the execution of this query using aggressive Oracle PARALLEL hints, which exhausted available target DB CPU/memory resources.

Resolution

To prevent future resource contention and CPU/memory alerts in the target database, parallelism hints must be disabled or tuned within Qlik Replicate. This involves modifying two internal parameters across the Full Load and CDC stages: bulkUseParallel and directPathParallelLoad.

bulkUseParallel is for CDC / Change Processing and is enabled by default (true). It instructs Qlik Replicate to inject the Oracle PARALLEL hint into bulk DML statements for better target performance.

Setting it to false stops queries such as UPDATE /*+ PARALLEL(tempview) */ ... from executing in parallel, preventing CPU spikes.

This may cause a slight performance degradation during high-volume CDC processing.

directPathParallelLoad is for Full Load and enabled by default (true). It enables Direct Path loading using parallel processing only during the initial Full Load phase. It has no impact on the daily CDC.

Setting it to false proactively protects the DB during table reloads.

Will likely increase the time required to complete Full Load operations.

How to set the Internal Parameters in Qlik Replicate:

1. Navigate to Manage Endpoint Connection → Targets and select your Endpoint
2. Open the Advanced tab and select Internal Parameters
3. Add bulkUseParallel and directPathParallelLoad
4. Untick the Value checkbox to disable them
   
   
   
   
5. Click OK

Environment

• Qlik Replicate

1. Take a backup of the app and data associated with the app:
   1. Export the existing Operations Monitor app via the QMC (Apps > More actions > Export). Backup to a safe location.
   2. Backup the QVD files in the Central Node Log directory (C:\ProgramData\Qlik\Sense\Log by default)
   3. Verify you have an Operations Monitor QVF file in the DefaultApps section of the Qlik installation directory (C:\ProgramData\Qlik\Sense\Repository\DefaultApps by default). Ask support for a copy for your version of Qlik Sense if you cannot locate the file.
   4. Write down any reload tasks associated with the app so that you can restore them later
   5. Write down the original owner of the app (should be the internal repository user, INTERNAL\sa_repository)
2. Remove the Operations Monitor App and associated data files:
   1. Delete the Operations Monitor app via the QMC (Apps > Delete). This removes both the app and associated reload tasks.
   2. Delete the QVD files associated with the Operations Monitor App (governance*.qvd) in the Central Node Log directory (C:\ProgramData\Qlik\Sense\Log by default)
3. Restart all Qlik Sense services.
4. Re-import the Operations Monitor App from the installation directory:
   1. Locate the default Operations Monitor app in the DefaultApps section of the Qlik installation directory (C:\ProgramData\Qlik\Sense\Repository\DefaultApps by default)
   2. Import the app via the QMC (Apps > Import)
   3. Change ownership of the app to the same user as before (should have been the internal repository user, INTERNAL\sa_repository)
   4. Recreate any reload tasks noted from step 1
5. Reload the app, and verify the app works as expected.

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

When performing an Export of a Native Map in Qlik Sense only the points are being shown and not the actual background.

Current export result (Satellite background image is missing):

Or the map is entirely blank:

Environment

• Qlik Sense Enterprise on Windows 

Resolution

The port 443 to  imagery provider services.arcgisonline.com is probably blocked
Check and open port 443  (scroll down to "Web browser ports" and check "map").

Publishing an app in a Qlik Sense Enterprise on Windows (client-managed) environment may fail with the error:

Quota is exceeded

Resolution

Reduce the size of files attached to the app. Alternatively, delete unnecessary files you have attached to it.

You can review what files you have attached to the app from the Qlik Sense Management Console:

1. Open the Qlik Sense Management Console in a supported browser
2. Go to Apps
3. Locate and highlight the app you cannot publish 
4. Click Edit
   
   
   
   
5. Open the App content menu tab on the right side of the screen; this will provide an overview of your attached files and how large they are. 
   
   You can now choose to review the files and reduce them in size, or:
6. Choose the file you wish to delete and click Delete
   
   

Cause

The maximum file size of an individual file attached to an app is 50 MB, while the maximum total size of files attached to the app (including image files uploaded to the media library) is 200 MB.

See Attaching data files and adding the data to the app for details.

Related Content

Attaching data files and adding the data to the app | Qlik Sense on Windows Help

Environment

• Qlik Sense Enterprise for Windows

There are two different ways to check the patch version of your Qlik Talend JobServer:

• Log in to your Qlik Talend Administration Center (TAC) and navigate to Conductor (A) > Servers (B)
  
  The patch level can be found below the Server Version (C) column, as shown below.
  
  
  
  The version will not be listed for any JobServers that are disconnected from Qlik Talend Administration Center. 
  
  

• On the server that JobServer is installed, navigate to <JobServer>/agent

  • If the version of Talend JobServer is TPS-6002 (R2025-04) or higher, the patch level for JobServer can be found in the branding.properties file. 
    
    

  • If the branding.properties file is missing, then a lower version of Jobserver is being used. The full version can be found in <JobServer>/agent/lib and reviewing the org.talend.remote file extension name:
    
    Example: org.talend.remote.server-8.0.2.20250129_0823_patch indicates the patch level is R2025-01 (TPS-6002)
    
    

Environment

• Qlik Talend Administration Center

After recreating the Amazon EMR cluster and updating the Storage Zone configuration in Qlik Compose with the new EMR master IP, the connection validation failed with the following error:

Storage Zone connection failed  
COMPOSE-E-ENGCONFAI  
Java connection failed  
SYS-E-GNRLERR, Required driver class not found:  
com.simba.hive.jdbc41.HS2Driver

This issue caused the Storage Zone connection to fail, impacting data pipeline operations.

Resolution

1. Verify that the required Hive JDBC driver (HiveJDBC41.jar) is present in the following directory on the Qlik Compose Agent server:
   
   <Compose Install directory>/java/jdbc/
   
   
2. Restart the Qlik Compose Agent service to ensure the driver is loaded:
   
   

   sudo service compose-agent stop
   sudo service compose-agent start

3. Validate the service is running:
   
   

   sudo service compose-agent status

4. Retest the Storage Zone connection in Qlik Compose UI, which succeeded after the restart.

Cause

The Hive JDBC driver (HiveJDBC41.jar) required for connecting to EMR HiveServer2 was either:

• Missing from the Compose Agent jdbc directory, or
• Added but not loaded because the Compose Agent service was not restarted

Qlik Compose does not dynamically load new JDBC drivers. The driver becomes available only after restarting the Compose Agent service.

See Prerequisites | Qlik Compose.

Environment

• Qlik Compose

QEM API used: PatchEndpoint
Endpoint for patching: SQL Server

The following error occurs when trying to update the PatchEndpoint endpoint with the prop value seen for the fields. The prop value seen for this endpoint is DO.SqlserverSettings.server.

{"error_code":"AEM_PATCH_ENDPOINT_INNER_ERR","error_message":"Failed to patch replication endpoint \"HS_MSSQL_ISOPROD\" from server \"dev\". Error \"SYS-E-HTTPFAIL, Failed to apply json-patch.\", Detailed error: \"SYS,GENERAL_EXCEPTION,Failed to apply json-patch,Failed to apply patch remove/replace for item '/db_settings/DO.SqlserverSettings.server'; item does not exist; Failed to apply json patch\"."}

Resolution

The correct prop value in this instance is 'server' for the server field. The prop value in this endpoint contains the combined value of the parent prop, while other endpoints will separate the parent prop value into its own parameter.

Sample JSON file with the correct prop value:

[
{ "op":"replace", "path":"/db_settings/server",
"value":"server_ip_address_here" }
]

Cause

SQL Server endpoint elements did not separate the parent prop value, leading to a misleading element inspection. The last part of the prop value is all that is needed for the JSON file.

Environment

• Qlik Enterprise Manager

Qlik Software Windows executables (such as Qlik Talend Studio, Talend Installers, Qlik NPrinting) come with an embedded digital signature, which signals Windows (and any security software) that the executable has been verified.

The digital signature is typically valid for 2 to 3 years before requiring renewal.

However, when reviewing the signature, it may show that it was revoked by the issuer around April 28th of 2026, even though it should still be valid for another 6-12 months.

Consequently, security software may block any executable that does not have a valid or current digital signature, leading to users being unable to launch the installed Qlik software.

Resolution

While proceeding by bypassing the signature check is an option, it is not always a feasible workaround. Qlik is actively replacing the affected installation files with executables that include both the digital signature and a new (valid) countersignature. 

Re-downloading the installation package from the Qlik Download page will resolve the issue in most instances. 

• Qlik Sense Enterprise on Windows and Desktop May 2026 IR
• Qlik Sense Enterprise on Windows November 2024 Patch 28 (release expected May 27th)
• Qlik Sense Enterprise on Windows May 2025 Patch 20 (release expected May 27th)
• Qlik Sense Enterprise on Windows November 2025 Patch 10 (release expected May 27th)

Not all files have been replaced at this point. Specifically, major releases (IR) are still undergoing processing.

To prevent this from recurring, Qlik has updated its digital signing processes.

If your product is not available on the Qlik Download page (such as Qlik Talend Studio), contact Qlik Support to receive the newly compiled executable (R2024-05 through R2026-05). 

Cause

The revocation of the digital signature was due to identifying a countersignature that did not have a timestamp set. 

Internal Investigation ID(s)

ITSYS-16864

Environment

• Qlik Products

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: 

Qlik Sense February 2022 to Qlik Sense November 2024.

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

• (Limitation removed in QPI 2.1 | Release Notes) Cannot migrate a 14.17 embedded database to a standalone
• (Limitation removed in QPI 2.1 | Release Notes) 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 

Purpose

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

Background

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

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

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

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

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

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

Driver Installation

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

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

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

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

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

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

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

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

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

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

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

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

 Oh no, the heart rate is going up again. 

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

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

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

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

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

Challenge 

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

Related Content 

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

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

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

Is there any option to find out, which Browser, OS, Device and IP address of our users using to log in to Qlik Sense production system? Can this data be found in the Qlik Sense monitoring apps or Qlik Sense logs?

Note that this article covers the historic analysis of data and does not include how to identify access live and have Sense react accordingly. 


Environments:

Method 1, using the Qlik Sense Proxy logs

This method requires for the Proxy log files logging level to be increased, and for Extended Security Environment to be enabled. Extended Security Environment has consequences in the environment, such as disabling the potential of sharing sessions across multiple devices. See the Qlik Online help for details. 

Settings to Enable:

• In the Qlik Sense Management Console, select the required Proxy
• Navigate to Logging
• Set the Audit Log level to Debug
• In the Qlik Sense Management Console, select the required Virtual Proxy
• Navigate to Advanced
• Enable "Extended Security Environment"

The proxy will now log additional information in: 
C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\[Server_Name]_Audit_Proxy

Example Output:

Audit.Proxy.Proxy.Core.Connection.ConnectionData [X-Qlik-Security, OS=Windows; Device=Default; Browser=Chrome 67.0.3396.99; IP=::ffff:172.16.16.100; ClientOsVersion=10.0; SecureRequest=true; LicenseContext=UserAccess; Context=AppAccess; ] || [X-Qlik-User, UserDirectory=DOMAIN; UserId=administrator]

For more information on where to find the logs see
How To Collect Qlik Sense Log Files

Method 2, using the Qlik Sense HubService logs

A much more lighter-weight approach than method 1 would be to parse the HubService logs in C:\ProgramData\Qlik\Sense\Log\HubService. No additional settings are required. 

Example Output:

::ffff:192.168.56.1 - - [31/May/2019:12:36:40 +0000] "GET /about HTTP/1.1" 304 - "https://SERVERNAME/hub/?qlikTicket=9mDlmVfE-E1Nc3RT" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"