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.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
The task was published from Talend Studio using Java 17. The project properties within Talend Studio is currently set to Java 17 compatibility mode, and the Remote Engine is also utilizing Java 17. Nevertheless, the execution summary of the task indicates that Java 8 is being used.
The environmental setting JAVA_HOME of the Remote Engine from which it run is set for Java 8 home path. Some servers require multiple Java environments and have the Remote Engine's JDK set in the <Remote Engine Installation Home>/bin/setenv or the <Remote Engine Installation Home>/etc/wrapper file. The Job launcher will take it's lead from JAVA_HOME, thereby causing the Job to execute with Java 8.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/<JDK HOME>/bin/java
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Cloud.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud App Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Reload Analyzer.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Access Evaluator.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
This article shows how to use the Qlik Application Automation Monitoring App. It explains how to set up the load script and how to use the app for monitoring Qlik Application Automation usage statistics for a cloud tenant.
For more information and to download the app and usage instructions, see Qlik Application Automation monitoring app.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
The Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.
The internal parameter skipMscdcJobFitnessCheck implies that, if enabled, it will prevent or (skip) the Fitness Check from running. This is incorrect.
skipMscdcJobFitnessCheck controls the cdcJob portion of the Fitness Check. The Fitness Check itself will always run and cannot be stopped. Only the cdcJob check is skipped.
This means that task log entries such as "Failed in MS-CDC fitness check" will not be addressed by enabling skipMscdcJobFitnessCheck.
Qlik Replicate
SQL Server MS-CDC
Qlik Replicate: MSSQL-CDC source endpoint to Snowflake. We are encountering the following error: Failed in MS-CDC fitness check
Qlik Replicate: How to set Internal Parameters and what are they for?
Executing the Qlik Migration Tools leads to the following error on line 185 of 7_migrateapps.ps1:
Error: operation unsupported for server-type "cloud" (Qlik Cloud). Supported server-types are: ["windows"]
Example:
qlik context use $QlikWindowsContext | out-null qlik qrs app export create $appid --skipdata $SS --exportScope all --output-file $exportAppFile
Verify you have followed the required step-by-step configuration documented in Using qlik-cli with Qlik Sense Enterprise client-managed Repository API (QRS).
Specifically, do not forget to execute this cmd to add the Qlik Sense Enterprise on Windows server to qlik-cli. See Configure a context in qlik-cli for details.
Example:
##qlik context create QSEoW --server <server name> --server-type windows --api-key <JWT Token>
Possible causes:
Lines 184 and 185 test the connection as documented in Qlik-CLI: Test the connection and point to a misconfiguration of the context.
By accessing the tenant of the Qlik Sense SaaS editions, you may get the following error after trying to open an app.
"Unable to connect to the Qlik Sense engine. Possible causes: too many connections, the service is offline, or networking issues."
In the most common scenario, the error is related to an idle session timeout. If the error occurs after 20 min idle time, the only required action is to click "Refresh" in order to reconnect the client to Qlik Sense.
For this scenario, a more user-friendly message is planned for future Qlik Cloud releases.
It is recommended to try and establish if a network device between the browser and the Internet is causing the connection error if it occurs immediately or sooner than idle session timeout.
Connect to Qlik Cloud tenant from a different device or network
Check browser dev tools for more specific error messages
Qlik Sense uses WebSockets that enable communication between the web browser and Qlik Sense server. A Qlik Sense application gets generated with visualization objects and data via this communication.
The same technology is applied for web integration where Qlik Sense objects are embedded in other pages.
The root cause of this error is that the browser's WebSocket connection has been terminated for various reasons;
In this example, we load data from an Excel file hosted on SharePoint 365 using the Qlik Office 365 Sharepoint connector.
Environment:
For our example, we are using Qlik Sense Enterprise on Windows and the installed Qlik Web Connector for Office 365 Sharepoint. For more information on the Office 365 Sharepoint Qlik Web Connectors and for installation instructions, see: Office 365 Sharepoint and Installation Web Connectors.
Links provided in these examples are example links, not real links.
When running the Talend Installer with root user and sudo permission, the installation failed with an error:
Error: There has been an error.
Error running /bin/sh -c "/tmp/create_user_4ce8b0db.sh" : /bin/sh: /tmp/create_user_4ce8b0db.sh: Permission denied
Collaborate with the Linux administrator to temporarily remove nonexec from /etc/fstab, and once the installation is complete, you may reactivate the nonexec option out of security concern.
The /tmp folder was mounted with the nonexec option, which disables execution. By default, Talend will use the /tmp folder to extract the temporary installer file for execution.
To verify this, you can type
cat /etc/fstab
and find the line for
/dev/mapper/vgroot-lvtmp /tmp xfs nodev,nosuid,noexec 0 0.
With Qlik Sense's new feature, Chart-level scripts, Add prefix is used with LOAD to append values to the HC1 table, representing the hypercube computed by the Qlik associative engine.
Based on this documentation and using the attached CHART LEVEL SCRIPT_ADD RESIDENT Load.qvf, we would expect the table to have 12 entries (6 original and 6 new)
Example: as the hypercube already has 6 entries, we would expect 6 new entries to be added when using Add prefix.
ADD LOAD MyDim1 as MyDim1, MyDim2 as MyDim2, MyMeasure1*100 as MyMeasure1, MyMeasure2*1000 as MyMeasure2 RESIDENT HC1
The result only shows 6 rows, with only one of them being modified:
This is working as designed.
ADD LOAD RESIDENT will try to merge duplicate rows and the test cases expect this behavior.
To workaround this specific user case, add a blank space to one of the dimensions, as shown below:
ADD LOAD MyDim1&' ' as MyDim1, MyDim2 as MyDim2, MyMeasure1*100 as MyMeasure1, MyMeasure2*1000 as MyMeasure2 RESIDENT HC1;"
QB-27903
Based on Qlik Sense online documentation, a PUT statement can be used to access columns, rows i.e. to set a numeric value to the hypercube.
However, using a Dimension name in a PUT statement, the following error is thrown:
Load statement could not find target column [MyDim1] in hypercube
This is working as designed.
Put statements are not allowed to manipulate dimensions. The Qlik Sense online help will be updated to reflect this.
QB-27904
Based on Qlik Sense online documentation, PUT statement can be used to set some numeric value to the hypercube
But in the following example (see attached CHART LEVEL SCRIPT_Put Dimension_silently fails.qvf), PUT statement seems to do nothing i.e. when used, no error is returned and expected changes are not displayed
Put #hc1.dimension.1(rr) = 'myvalue_' & rr; Put #hc1.dimension.2(rr) = rr * 100;
This is working as designed.
Put statements are not allowed to manipulate dimensions. The Qlik Sense online help will be updated to reflect this.
QB-27952
This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.
If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.
Content
This document covers the following scenario:
Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.
These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8).
No further steps are required.
If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
Changing the Database Superuser Password without Qlik Sense Installed
After an upgrade to Qlik Replicate 2024.5, capturing changes (CDC) for a table defined as DDS on a DB2i Source leads to conversion errors with the NUMERIC Datatypes with precision and scale greater than zero.
Due to a change in Qlik Replicate's new version, this error causes the table defined in the task to have data issues with the value in the target showing 0 and not the correct value present in the Source.
Example: 100.000 (source) becomes 0 (target)
To verify the table defined in the task, have the DDL for the table confirmed, then check locate the below details in the DDL output from iSeries, helping you identify if this is a DDS defined table in the DB2i Source Environment:
RCDFMT
Example:
The DDS number definitions impacted have a SCALE > 0.
So take DDS 5S 2, or in SQL Numeric(5,2), a value like 123.45 will fail conversion and end up as 0.
No solution is currently available.
Postpone the upgrade or reload the affected table as a possible workaround.
A regression of the 2024.5 version of Qlik Replicate, affecting how the Datatype is parsed from the Journal/Receiver to the Target.
Selecting records using a specified record format name (RCDFMT parameter)
RECOB-8827
Renaming an Endpoint:
The only possible way to rename an endpoint is to duplicate an existing endpoint and change the name.
You need to reconfirm the password of any endpoints that was duplicated.
Renaming a Task Name:
The only way to rename a task is outline below:
The reason for this is because the task name is used throughout the replicate environment from the task directory on disk to the internal SQLite DB entries, as well as in the target DB control tables so changing the name is very complex for the Replicate architecture.
Three requirements need to be met in order to allow Anonymous users access to the Hub:
Useful information:
By default, anonymous access is disabled. The steps provided require a restart of the Proxy service after completion.
Anonymous users will need to have a license rule available for them which gives them either an Analyzer Capacity License or a Login Access Token. The instructions in this article will focus on Analyzter Capacity Licenses.
You can use the default Everyone stream, which has already been set up for anonymous access, or create your own.
We will create two rules. One to allow logged in (authenticated) users access and publishing permissions. One to allow anonymous user access, but no publishing permissons. Note that based on your requirements, this may need to modified.
We are now ready to test access.
When your Qlik Sense server is behind a proxy you will need to add the proxy in the License service:
Configuring a proxy for Qlik License Service communication in Qlik Sense Enterprise on Windows
Qlik Sense Enterprise on Windows
{"caller":"handler.go:53","errorMessage":"invalid license error, no license found, tenant not found","errorType":"LICENSES-ForbiddenRequest","level":"info","logTraceId":"XXXXXXXXXXd674e50adef83","statusCode":403,"timestamp":"2021-09-23T09:17:27.1566729Z"}
This 403 forbidden error doesn't tell us more than that something is forbidden.
If we want to check this Proxy and be sure it is really working from the Qlik Sense server, we can use PowerShell and test the connection.
If you are using a Proxy with no authentication required, you can use below command:
Where "myproxy" = the proxy IP address or hostname set in the Qlik Sense dispatcher service
And where "8080" = the port number used for the Proxy
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$Site="https://license.qlikcloud.com"
$Test=Invoke-WebRequest -URI $Site -Proxy 'http://myproxy:8080'
$Test.Links
If your proxy requires authentication, you can use below command (run PowerShell as Administrator).
Where "172.16.16.101" = the proxy IP address or hostname set in the Qlik Sense dispatcher service
And where "808" = the port number used for the Proxy
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
netsh winhttp set proxy "172.16.16.101:808"
$Wcl=New-Object System.Net.WebClient
$Creds=Get-Credential
$Wcl.Proxy.Credentials=$Creds
$Site="https://license.qlikcloud.com"
$Test=Invoke-WebRequest -URI $Site
$Test.Links
The above command will prompt a Window where you need to put the login name and the password for the proxy authentication.
The result of the two above PowerShell scripts should show below result:
If you have any other result like for example "Your system policy has denied the requested action", or "proxy denied access", or similar, contact your IT security team to allow access to https://license.qlikcloud.com (port 443) through your Proxy.
Cannot publish a Job to Talend Cloud from Talend Studio, the following message appears on the pop-up in Talend Studio:
Could not resolve dependencies for project <Project>.job:<JOB>:jar:0.1.0: The following artifacts could not be resolved: <Project>_jobs.code:routines:jar:8.0.1 (absent): Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.example.mse_jobs.code:routines:jar:8.0.1 has not been downloaded from it before. -> [Help 1]
Cause 1
Cause 2
Solution 1
Solution 2
Please note that merely editing the <Talend_Studio_Home>/path/Talend-Studio-xxx.ini file may not be sufficient. In cases where you are launching via a Windows/Mac/Linux GUI shortcut, please ensure that the -vm option is configured to point to the Java 17 bin.
Talend studio can't connect TAC at loading license page and Pop-Up window displays
"Studio can't access the resource from server, please check the resource url". If loading a local license, then studio can connect TAC successfully at the connection setting page .
Cause 1
Defect TUP-40730(Internal) was identified and addressed in November 2023 release of Studio
Cause 2
Potentially, there may be a network connection issue between studio and TAC due to firewall, proxy, VPN
Internal investigation ID TUP-40730
Content
Qlik Products have generally utilized license keys to enforce license entitlements and use rights. During activation, the licensed entitlement is downloaded to the product in the format of a Licensing Enabler File (LEF). Activation requires internet connectivity to the deployment and is triggered by entering a 16-digit serial number and a corresponding control number. Offline activation is also supported using a manual LEF by copying and pasting a text file into the activation user dialog. Communication is through an http protocol.
Introduced with the February 2019 release[GM1] of Qlik Sense Enterprise, Qlik has developed an alternative process for product activation. There have been several drivers for this change, including a move to an https protocol for a more secure connection between the Customer deployment and Qlik infrastructure. More information follows below.
To allow for Customers to make the decision when to move, Qlik has introduced the use of a Signed License Key to determine which activation method to use. Over time Qlik Licensing Service will replace the current activation process, but for now both methods of activations will work.
As mentioned above, Qlik has added one additional way to activate Qlik products.
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWT’s can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
Although JWT’s can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it. That is why we refer to this as the Signed License Key.
With the use of a Signed License Key, there are more Product and deployment offers to use.
All of the above is enabled by the use of the Signed License Key. This made possible as the local deployment will sync entitlement data with all deployment’s using the same Signed License Key through an online database, License Backend, hosted by Qlik within Qlik Cloud.
This is initiated by entering a Signed License Key to the Control Panel. The request is performed by the service Licenses using port 443 (https protocol procedures applies).
Signed license Key
|
Example data |
A Signed License Key based on one of Qlik’s internal keys.
|
eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCIsImtpZCI6ImEzMzdhZDE3LTk1ODctNGNhOS05M2I3LTBi MmI5ZTNlOWI0OCJ9.eyJqdGkiOiI2MjNhYTlhZi05NTBmLTQ3ZjctOGJmMC1mNGQzOWY0MmQ5N mMiLCJsaWNlbnNlIjoiOTk5OTAwMDAwMDAwMTI1MyJ9.YJqTct2ngqLfl2VP3jxW4RsDNK2MTL-BpJ WnBdIfF5gGbJcX0hc__tfIa2ab5ZrL9h6tsZxTwgucTFiRTAOz8PaOQP7JTnhPCyrBZwpnmhvCrSHx2 C-HbCARFUIueBzMg8fgvWH-3HxBuxx6jnDhekDTUbb12vBq7CySampJkgMT7QsDdUkeJy5E7O0U 8yhd1RtEDeuTbeX35eIdQUN4DyJWHHPiT9qZt1AV0_Ofe1iLKxYZMa5jC0kIsVwYnRCJzibZlrLE7mS VlNitxmcm8OoUrR_ZIk8VuOkoz_qqy8N_wwrt7FcT2slWz50XzuL8TIWY9mcGIL |
Assignment information (what user has what type of access assigned) is synchronized from the license service to license.qlikcloud.com every 10 minutes.
Changes to a license (such as adding additional analyzer capacity) can take up to 24 hours to be retrieved.
Data Element | Comment | Example Data |
Signed License Key | See above | |
Cause | Initial or Update | “Initial” |
User agent | build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, QV) | Licenses/1.6.4 (windows) QSEfW |
Data Element | Comment | Sample Data |
License definition | content variable based on product and entitlement | "name": "analyzer_time", "usage": {"class": "time", "minimum": 5}, "provisions": [{ "accessType":"analyzer"} ],"units": [{"count": 200, "valid": "2018-06-01/2018-12-31"}]}, "name": "professional", "usage": { "class": "assigned", "minimum": 1 }, "provisions": [{ "accessType": "professional" }],"units": [{ "count": 10, "valid": "" }]} |
(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)
Data Element | Comment | Sample Data |
Signed License Key |
See above | |
Array Element id | Used for internal match only | 1 |
Allotment name | alternatives are Analyzer_Time, Core_Time | “analyzer_time” |
Year/Month | YYYY-MM | 2018-11 |
Consumption | for this deployment since last sync | 242 |
Source | hashed ID to make each deployment unique, e.g. a Qlik Sense Enterprise on Windows and a Qlik Sense Enterprise on Kubernetes will have different Source ID's | fbe89d02-6d24-4595-915e-c52ce76f2195 |
User agent | same construct as for as activation request | Licenses/1.6.4 (windows) QSEfW |
Data Element | Comment | Sample Data |
Total consumption | Used by the Product for enforcement. Deny access will be executed if quota has been exceeded. Quota is set in the LEF. Additional quota for the month could be managed as Overage in the LEF. This would contain an Overage Value (COUNT) or the value YES. Total quota for the month is calculated as licensed quota + Overage quota. If the LEF contains the value YES, there will be no cap on the capacity for the Year/Month. |
12345 |
Data Element | Comment | Sample Data |
Signed License Key | See above | |
Allotment name | Professional / Analyzer | “professional” |
Subject | Domain / User ID; if this an add or delete transaction. By delete the subject will be removed immediately. An internal id will be used to secure sync to other deployments using the same Signed License Key. The internal id will disappear within 60 days after a delete transaction. (This information is stored for all assigned users until such a time that the assignment is deleted at which point it is deleted. The information is used for synchronizing assignments across deployments in order to facilitate the single-license-multi-deployment scenario. It is encrypted in transit and at rest.) |
“acme\bob”
(For information on how data is submitted and stored in the audit logs see here) |
User agent | Build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, QV) | Licenses/1.6.4 (windows) QSEfW |
Source | Hashed ID to make each deployment unique, e.g. a Qlik Sense Enterprise on Windows and a Qlik Sense Enterprise on Kubernetes will have different Source ID's | fbe89d02-6d24-4595-915e-c52ce76f2195 |
Sync metadata | Versioning information about the subjects and list of subjects to manage the synchronization process | { "source": "my assignments", "bases": [{ "license": "1234 1234 1234 1234", "version": 0 }], "patches": [{ "instance": "", "version": 0, "license": "1234 1234 1234 1234", "allotment": "analyzer", "subject": \\generated4, "created": "2019-04-18T10:01:35.024031Z" } |
Data Element | Comment | Sample Data |
Signed License Key | See above | |
Subject | Including subjects changed by other deployments | “acme\bob” |
Sync metadata | Versioning information about the subjects and list of subjects to manage the synchronization process | { "bases": [{ "license": "1234 1234 1234 1234", "version": 17 }], "patches": [{ "instance": "5382018630938057025", "version": 14, "license": "1234 1234 1234 1234", "allotment": "analyzer", "subject": ACME\\bob", "created": "2019-04-18T10:01:35.024Z", "rejection": "" }] |
This Reference Guide is intended solely for general informational purposes and its contents do not form part of the product documentation. The information in this guide is subject to change without notice. ALL INFORMATION IN THIS GUIDE IS BELIEVED TO BE ACCURATE BUT IS PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. Qlik makes no commitment to deliver any future functionality and purchasing decisions should not be based upon any future expectation.
This article provides a guide on installing Qlik Replicate on a docker image.
sudo rpm -qa|grep dockersudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-laster-logrotate docker-logrotate docker-engine
sudo yum install -y yum-utils device-mapper-persistent-data lvm2 sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo yum install --allowerasing docker-ce docker-ce-cli containerd.io sudo systemctl start docker sudo systemctl enable docker
/kit
" The /kit directory is a temporary folder used to store installation files. In the example below, the RPM file is areplicate-2024.5.0-357.x86_64.rpm
. Once the installation is complete, the entire /kit folder can be safely deleted.mkdir -p /kit/ar_docker
cd /kit
rpm2cpio areplicate-2024.5.0-357.x86_64.rpm | cpio -iv --make-directories --no-absolute-filenames -D ar_docker/ ./opt/attunity/replicate/addons/samples/docker/*
mv ./ar_docker/opt/attunity/replicate/addons/samples/docker/* ./ar_docker
rm -rf ./ar_docker/opt
cd /kit/ar_docker
cp ../areplicate-2024.5.0-357.x86_64.rpm .
./create-dockerfile.sh
/kit/ar_docker/Dockerfile
, from:
RUN yum -y install /tmp/areplicate-*.rpmto
RUN systemd=no yum -y install /tmp/areplicate-*.rpm
NOTE!
The parameter systemd=no is used to solve the below error you may hit during the docker build stage: This rpm is not supported on your system (no systemctl), exiting. error: %prein(areplicate-2024.5.0-357.x86_64) scriptlet failed, exit status 43
NOTE!
The password should not be empty and must be strong enough.
WARNING!
If you want to install ODBC Drivers, please make the corresponding ODBC Drivers rpm files are ready in this folder. If you want to skip the ODBC Drivers installation at present, rename or delete the file "drivers" in this folder.
docker build --no-cache -t johnw/replicate:2024.5 .where
/johnw/replicate:2024.5
is the image tag.Do not forget the last period "."
docker run -d --name ar --hostname cdc2 -e ReplicateRestPort=3552 -p 3552:3552 -v /dockermount/data/replicate/data:/replicate/data johnw/replicate:2024.5
Now Qlik Replicate is running in the docker and can be accessed from Qlik Replicate Console GUI.
Creating an OLE DB connection in Qlik Sense on-prem fails at the Test connection step with:
Test failed
To verify the connection is successful, first confirm the connection works using a UDL file. For step-by-step instructions refer to Test SQL database connectivity with test.udl file. Once you receive a Test connection succeeded with the UDL file, close all the prompts and open the file with a text editor. This file contains the new connection string.
For the test in our example, the only extra parameter enabled in the connection string that is not possible to put in the connection UI is Trust Server Certificate=True. All other values are set to empty or null and we exclude them.
With that information, you can now create a connection with the Engine API explorer:
Note: Make sure to keep the OLEDB CONNECT TO and the brackets in the connection string value.
JSON:
{
"handle": 1,
"method": "CreateConnection",
"params": {
"qConnection": {
"qId": "",
"qName": "OLEDBSQL",
"qConnectionString": "OLEDB CONNECT TO [Provider=MSOLEDBSQL19.1;Persist Security Info=False;Data Source=ServerNameorIP;Trust Server Certificate=True;]",
"qType": "OLEDB",
"qUserName": "user",
"qPassword": "Password",
"qModifiedDate": "",
"qMeta": {
"qName": ""
},
"qLogOn": 0
}
}
}
Limited options to add extra parameters to the OLE DB connection through the UI. The connection string field is only available in "Edit" mode, not in creation mode.
Test SQL database connectivity with test.udl file
Create a connection Method