Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
This article documents how to convert a Direct Task into a Log Stream Task without reloading the target.
Re-enter the Password
Qlik Support advises using the driver version for your endpoints that was certified for the version of Qlik Replicate you are using. The use of a driver running a different version than what was certified can lead to unpredictable results.
Before troubleshooting a potential defect, always ensure a supported driver is in use.
However, it is acceptable in most cases to use a later patch for the driver so long as it is the same major version. For example:
The current release of Qlik Replicate is May 2024. It requires ODBC driver version 18.3 for Microsoft SQL Server source and target. The other currently supported Qlik Replicate releases, November 2023, May 2023, and November 2022, all were certified with driver version 18.1.
However, the driver version 18.3 can be used.
Generally speaking, if the version of the driver is the same and has only been patched (as is the case between driver 18.1 and 18.3) we do not anticipate any issues using it with November 2023, May 2023 and November 2022 versions. If an issue is encountered on these versions with ODBC driver version 18.3, please open a support case.
This is generally true with using a patched version of the certified driver for other databases/endpoints as well, but there might be exceptions. Some endpoints mandate only specific versions for the driver. If there is a doubt, please open a support case.
From R2024-05, Java 17 will become the only supported version to start most Talend modules, enforcing the improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions. In 2025, Java 17 will become the only supported version for all operations in Talend modules.
Starting from v2.13, Talend Remote Engine requires Java 17 to run. If some of your artifacts, such as Big Data Jobs, require other Java versions, see Specifying a Java version to run Jobs or Microservices.
Content
Qlik Talend Module | Patch Level and Version |
Studio | Supported from R2023-10 onwards |
Remote Engine | 2.13 or later |
Runtime | 8.0.1-R2023-10 or later |
For Windows users, please follow the JDK installation guide (docs.oracle.com).
For Linux users, please follow the JDK installation guide (docs.oracle.com).
For MAC OS users, please follow the JDK installation guide (docs.oracle.com).
When working with software that supports multiple versions of Java, it's important to be able to specify the exact Java version you want to use. This ensures compatibility and consistent behavior across your applications. Here is how you can specify a specific Java version on the following products (such as build servers, shared application server, and similar):
For Studio users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps:
-vm
<JDK17 HOME>\bin\server\jvm.dll
For Remote Engine (RE) users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
For Runtime users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
If Runtime is not running as a service:
With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
Windows users use <tac_installation_folder>\apache-tomcat\bin\setenv.bat
Follow the steps below to configure the JobServer to use the new Java version.
Navigate to the JobServer Configuration:
Go to the <JobServerRootDir>\conf directory, where <JobServerRootDir> is the path to your Talend JobServer installation.
Open the Configuration File for Editing:
Locate the TalendJobServer.properties file and open it with a text editor of your choice.
Set the Java 17 Executable Path:
Find the line dedicated to the Job launcher path within the file. You will modify this line to point to the Java 17 executable.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH="C:\\Program Files\\Java\\jdk-17\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/lib/jvm/java-17-openjdk/bin/java
Replace the example paths with the actual path where Java 17 is installed on your system. Ensure to point directly to the Java executable within the bin directory of your JDK installation.
Save Your Changes:
After editing, save the TalendJobServer.properties file.
Restart Talend JobServer:
For the changes to take effect, restart your Talend JobServer.
After completing these steps, Talend JobServer will utilize Java 17 for executing Jobs, ensuring compatibility with the latest Java version supported by Talend modules.
For Java 17 users, Talend CICD process requires the following Maven options:
set "MAVEN_OPTS=%MAVEN_OPTS% --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
For Java 17 users, Talend CICD process requires the following Maven options:
export MAVEN_OPTS="$MAVEN_OPTS \ --add-opens=java.base/java.net=ALL-UNNAMED \ --add-opens=java.base/sun.security.x509=ALL-UNNAMED \ --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
<name>TALEND_CI_RUN_CONFIG</name> <description>Define the Maven parameters to be used by the product execution, such as: - Studio location - debug flags These parameters will be put to maven 'mavenOpts'. If Jenkins is using Java 17, add: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED </description>
Overview
Enable your Remote Engine to run Jobs or Microservices using a specific Java version.
By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 and onwards, Java 17 is mandatory for engine startup. However, when it comes to running Jobs or Microservices, you can specify a different Java version. This feature allows you to use a newer engine version to run the artifacts designed with older Java versions, without the need to rebuild these artifacts, such as the Big Data Jobs, which reply on Java 8 only.
When developing new Jobs or Microservices that do not exclusively rely on Java 8, that is to say, they are not Big Data Jobs, consider building them with the add-opens option to ensure compatibility with Java 17. This option opens the necessary packages for Java 17 compatibility, making your Jobs or Microservices directly runnable on the newer Remote Engine version, without having to go through the procedure explained in this section for defining a specific Java version. For further information about how to use this add-opens option and its limitation, see Setting up Java in Talend Studio.
Procedure
c:\\Program\ Files\\Java\\jdk11.0.18_10\\bin\\java.exe
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=c:\\jdks\\jdk11.0.18_10\\bin\\java.exe
ms.custom.jre.path=C\:/Java/jdk/binMake this modification before deploying your Microservices to ensure that these changes are correctly taken into account.
For Java Option Command --add-opens, using SPACE or = depends on OS, JDK version or the place where you setup, there are 3 cases:
1. support both SPACE and =
2. support SPACE only
3. support = only
Example:
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
The following error message appears repeatedly in the logs.
2024-01-20 08:50:10 ERROR RepoProjectRefresher -
2024-01-10 16:58:47 ERROR GC - D:\Talend\7.3.1\tac\apache-tomcat\temp\_git\
The main reason for the log type is that the RepoProjectRefresher faces out of memory issues. By default, TAC automatically caches/checks out the project source code into the tac\apache-tomcat\temp folder. When the source code accumulation is large, the RepoProjectRefresher module will consume a lot of memory. When maximum value is reached, a GC error will occur and a GC error log will be generated.
Note: The RepoRefresher cache functionality has been deprecated in the latest version of TAC v8.0.1
Disable the Git caching mechanism for the TAC project by following these steps:
update t731.configuration set value='true' where configuration.key='git.whiteListBranches.enable';
update t731.configuration set value='\"Technical labels of project\",\"Active branch name\"' where configuration.key='git.whiteListBranches.list';
Downloading a Tabular Reporting On-Demand report fails with:
There was an error downloading the report
For tabular reporting to be able to use a chart, the chart must be on a public sheet.
If the object is already in a public sheet, Tabular Reporting may not recognize the Qlik Sense theme used. To resolve this, change the currently used Qlik Sense Theme to, for example, the Horizon or Sense Classic theme and try again.
This Techspert Talks session covers:
- What to plan for
- Migration Pathways
- Cloud Best Practices
Chapters:
Resources:
After Talend Cloud License Renewal, Talend 7.3 and earlier license versions is active in Talend Cloud subscription page, but the license still shows as expired when signing into Talend Studio 7.3 or prior versions.
You can use your login username and password or username & personal access token to fetch the license in Talend Studio. Please select the correct Server URL based on your region (AWS-region or Azure).
Old license file before the renewal is still located in the Talend Studio directory. Possible corruption of the license file due to size of file.
https://help.talend.com/en-US/studio-user-guide/7.3/launching-talend-studio?ver=5
At Qlik Connect 2024 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:
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:
Thanks,
Patric
After installing Qlik Sense Enterprise on Windows and adding the scheduler functionality, the engine service stops right after start with no logs written in the Engine logs.
This applies to Windows Server 2022.
Verify if TLS 1.3 has been enabled.
Neither the listed versions of Windows, nor Qlik Sense Enterprise on Windows support TLS 1.3. See Supported TLS and SSL Protocols and Ciphers.
Always take backups of your Windows Registry before proceeding. Manage the change with your Windows System Administrator if needed.
Once verified, disable TLS 1.3:
Alternatively:
TLS 1.3 is supported in Windows 11 and Windows Server 2022, but its not fully supported in Qlik Sense Enterprise on Windows yet. As a result your service will fail on startup.
Tabular Reporting events in the management console not showing for all the users in the tabular reporting recipient list
When section access is used in a Qlik App, ensure to add all required recipients/users to the section access load script
For example, users in the Recipient import file should ideally match the users entered to the Section Access load script of the app.
This generally permits users to view management console details such as 'Events' assuming those user also have the necessary 'view' permissions in the tenant in which the app exists
If some of the recipients in the tabular reporting recipient list do not have access to the Space/App - they won't be considered in the task execution because they fail the governance.
ie: Recipients/users that are not added to the load script will not have access to the app nor associated management console events.
This is expected behavior.
A Qlik app may show an Incomplete Visualization or Invalid Visualization error. This article covers the most common root causes.
Incomplete Visualizations:
Invalid Visualizations:
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
Verifying NPrinting connections shows all green check boxes.
However, when executing publish reports tasks, the task fails and we see failed to open document errors in NPrinting Engine or Scheduler log.
The column name text box in Qlik Replicate's Global Rule Filter is case-sensitive. If you do not match the case of the column name when running the task, the filter will not be applied to the target results.
There will be no error in the task log and no error presented onscreen. Instead, reviewing the resulting records will show that the filter was not applied and that all records are present.
Always case-match the column name in the source.
Data (global transformations only)
Starting from version "November 2021" (Version 2021.11), Qlik Replicate introduced support for log data encryption to safeguard customer data snippets from being exposed in verbose task log files. However, this enhancement also presented its own set of challenges, such as making it very difficult to read the logs and complicating troubleshooting processes, the steps of Decrypting Qlik Replicate Verbose Task Log Files takes time.
In response to customer feedback and feature requests, we implemented a new feature allowing users the flexibility to disable log encryption in Qlik Replicate. This enhancement was rolled out with the release of Qlik Replicate version 2023.5 GA. This article serves as a guide on how to effectively disable Task Log Data Encryption.
{
"port": 3552,
"plugins_load_list": "repui",
... ...
"enable_data_logging": true,
"disable_log_encryption": true
}
Important Note:
Please exercise caution as verbose task logs may contain sensitive end-user data, and disabling encryption could potentially lead to data leakage. Always ensure appropriate measures are taken to protect sensitive information.
How to Decrypt Qlik Replicate Verbose Task Log Files
Sometimes we need to join different tables in the source databases and filter records according to another table records values. In this article we are using Oracle source endpoint, to demonstrate how to build up such a task in Qlik Replicate.
In the below sample task, table testfilter will be replicated from Oracle source database to SQL Server target database. During the replication, the records which value is INACTIVE in table testfiltercondition will be filtered out and are ignored in both Full Load and CDC stages. The two tables are joined by the same primary key column "id".
In the above expression, the 2 tables testfilter and testfiltercondition are joined by the PK column "id" in function source_lookup.
#00145952
QnA with Qlik: Qlik Replicate Tips
By default, Qlik Replicate tasks do not automatically stop when disk space or memory has been completely used up. Resource Control must first be set up.
The tasks will log errors that disk space or memory is insufficient, but endpoints that write data to physical disk space can lead to missing data if there is no space to write the data files.
Set up Resource Control.
Qlik Replicate Resource Control
QB-24385