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

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

The Job design appears as follows:

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

The detailed error messages in the log:

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

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

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

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

Cause

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

Resolution 

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

For more information about the tRESTClient component, see tRESTClient.

Environment

• Talend ESB 8.0.1

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

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

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

Resolution

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

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

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

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

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

Cause

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

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

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

Internal Investigation ID(s)

QB-28905

Environment

• Qlik Cloud

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

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

Source: learn.microsoft.com

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

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

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

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

After enabling QUOTA_LIMITS_HARDWS_MAX_ENABLE as per Microsoft's guidelines:

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

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

To note:

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

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

Example:

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

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

Internal Investigation IDs:

QLIK-96872

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

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

Resolution

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

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

Cause

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

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

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

Related Content

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

Environment

Talend Studio 

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

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

As a consequence:

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

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

Resolution

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

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

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

Environment

Qlik Cloud 

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

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

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

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

Content:

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

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

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

For more information, refer to the GitHub Repository.

Features

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

Note on manual install

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

Part Two: Creating and setting up analytics data connections

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

Snowflake connection

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

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

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

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

   Finally, you need to name the connection as follows:

   • Connection Name: SNOWFLAKE_MONITORING_DATA
     
     
   
   

    

Note on Snowflake authentication

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

REST connection to repository

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

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

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

Note on update compatibility

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

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

The application has the following two variables:

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

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

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

   

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

Summary

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

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

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

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

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

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

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

Resolution

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

Environment

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

Related Content

Support Case: 00049024

This article is specific to Qlik Sense Enterprise on Windows.

Enable Audit Logging:

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

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

To read who has deleted an app:

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

Environment

Qlik Sense Enterprise on Windows 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

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

What is API rate limiting?

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

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

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

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

Environment:

Qlik Cloud 

How do I handle rate limiting in my applications?

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

How does API rate limiting in Qlik Cloud work?

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

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

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

Why is API rate limiting important to me?

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

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

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

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

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

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

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

Examples:

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

Environment

• Qlik Cloud

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

Resolution

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

On Linux

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

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

On Windows

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

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

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

Environment

• Talend Administration Center 8.0.1

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

[ Fig.1 ]

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

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

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

Failed to load visualization: 'kpi'

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

Resolution

Please apply the following instruction in your HTML file to the head-element :

<meta charset="utf-8"> 

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

Environment

Qlik Cloud

Related Content 

2.0.1 Add the script configuration for qlik-embed

When you use the tHttpClient/tRest/tRestClient component to pull Bloomberg numbers (URL ended with .csv extension) over API, the data is giving garbled characters.

 

Resolution

Using the proper operation tFileFetch component to download online application/csv file into a local temp folder firstly, and then combining with tFileInputDelimited to read data. 

The job design should be: tFileFetch-->onSubjobok-->tFileInputDelimited-->Further processing

Cause

As the target source URL ends with .csv,  it should be considered as a download operation for application/CSV type

 

Related Content

For more information about how to retrieve a file from an HTTP website and read data from the fetched file, please refer to this documentation

Fetching data through HTTP

Environment

• Talend Studio 
• Talend Data Integration 

• A Service Account Owner (SAO) is the only user who has admin rights to manage Qlik Sense Enterprise SaaS and Qlik Sense Business subscriptions on my Qlik portal (e.g. subscribe, renew, upgrade/downgrade number of users, access to personal information, and subscription details, payment details and invoices).

Relevant resources:

How to Access My Qlik Portal
Managing Your Subscription in My Qlik

Who is the default Service Account Owner?

• For subscriptions purchased through Qlik Sales or via a Qlik Partner:
  The default Service Account Owner is the Sold To contact email address on the quote linked to your purchased order. If you don’t know who the Sold To is, please reach out to your dedicated Qlik Sales Representative or Qlik Partner.
   
• For subscriptions purchased directly from My Qlik portal:
  The default Service Account Owner is the email address linked to the Qlik Account you have used to purchase your subscription online on my Qlik Portal. If you can’t remember the email address linked to your Qlik Account, see How to create a case to contact Qlik Support.

Is the Service Account Owner also the Tenant Admin?

• The Service Account Owner is the Tenant Admin by default. One exception is if the Tenant Admin was already changed in the past to someone else (see: Managing tenant admins).

Can I change the Service Account Owner?

• Yes, you can change the Service Account Owner(SAO) associated with your purchased subscription.

How to change the Service Account Owner (SAO)?

• The change is a manual process and requires you to contact Qlik Support (see How to contact Qlik Support). When raising such a request, please make sure to provide the below information:
  
  
  • Reason for change
  • Old email/New email
  • Subscription ID/License key
  • Tenant URL

Please do the following before requesting the change:

• Advise NEW SAO to register for a Qlik account
• Advise NEW SAO to log in at least once to  myqlik.qlik.com/portal
• Advise OLD SAO to transfer the Tenant admin rights to NEW SAO

When changing the Service Account Owner, does the Tenant Admin automatically change?

• No, the Tenant Admin will not change. If a change of Tenant Admin is needed, the current Tenant Admin will need to invite the new Tenant Admin and give him/her Tenant Admin Role in the Management Console. It is always recommended but not a requirement to assign two Tenant Admins per subscription. If one Tenant Admin leaves the company, the other one will still be able to administrate the tenant. If there is only one Tenant Admin who has left the company, please contact Qlik Support for further assistance (see How to contact Qlik Support)
  
  Additional Note:
  
  If the old Tenant Admin stored apps in his/her personal space, it is important for the new Tenant Admin to do either (a) or (b):
  1. Update who is the apps’ owner (See Changing app owners Changing app owners)
  2. Publish and share apps on a shared space (See Working in shared spaces)

Areas that are particularly sensitive when you remove a user:

• All private content on published apps will be lost. There is no API method to transfer ownership
• The connections created by the OLD SAO will be deleted and this will have to be recreated.
  • All data connections with credentials. These will all need to have their credentials updated once the data connection ownership is transferred

How to change the Tenant Admin?

Does the Tenant Admin need to consume a Professional or Analyzer user?

When you did update the context parameters and republish the Studio artifact to TMC for the requirement of updating your job context parameters , however, the context parameters are in fact not updated after re-running the task. What is the problem with?

Resolution

To have a TMC task following the context changes of a Studio job, the parameter "Override parameter values with artifact defaults" must be enabled in the Task Configuration.

ArtifactVersion

The reason why this is not enabled by default is because task context parameters can be updated directly in TMC without interacting with Studio by editing the task as shown below:

EditTask

Cause

When a task is created for the first time, it will copy all the values from the artifact. These task values will always keep the same value and will not be overwritten/replaced by new values in the artifact.

Related Content

For more information about how to update the new promoted version, please refer to this documentation

updating-job-tasks-with-latest-artifact-version

Environment

Talend Cloud 

Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch. 

All Qlik Replicate versions older than the 2024.5 SP03 release are affected.

Environment

• Qlik Replicate 2024.5 SP02 and below
• Oracle Source Endpoint with Oracle 2024 July patch (version 19.24)

Resolution

Upgrade to Qlik Replicate 2023.11 SP05, or 2024.5 SP03 or later. 

Download the formal builds for 2023.11 and 2024.5 here:

Qlik Replicate 2023.11 SP05: https://files.qlik.com/url/qr2023110860sp05 (expires 1/31/2025)

Qlik Replicate 2024.5 SP03 link: https://files.qlik.com/url/qr2024050563sp03 (expires 1/31/2025)

If you have Qlik Enterprise Manager deployed, upgrade this as well. See Qlik Enterprise Manager fails adding a table to a task with SYS-E-HTTPFAIL, no rest handler for url for download links.

Cause

The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly. 

Internal Investigation ID(s)

RECOB-8698

Reference:

Oracle Database 19c Release Update July 2024 Known Issues

As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.

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

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

Table of Content

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

To access your subscription

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

Manage Payment Method and Billing Information

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

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

Managing the Number of Paid Seats

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

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

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

4. Follow the onscreen instructions. 
   

Undoing the Seat Reduction

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

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

Cancelling a Subscription

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

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

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

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

Undoing the Cancellation

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

1. Click Undo Request in your subscription overview
   
   
   

    

2. Check I understand and click Confirm. 

This article describes an example of how to disable custom connectors for a particular user group for Qlik Sense.

The example is provided as is. Further customisation or adaptation to a specific use case scenario can be obtained by engaging Qlik's Professional Services. 

Setup example

• Domain\alex: Domain user account, belong to Windows user Group “Sydney”
• Domain\bob: Domain user account, belong to user Group “Sydney”
• Domain\craig: Domain user account, belong to none of user Group
• Above three users account are already fetched into Qlik Sense via UDC and Token is assigned.

Goal

• Users in user group “Sydney” CANNOT create “custom” data connection.
• Users in other group CAN create “custom” data connection.

Steps

1. Go to QMC > Security Rules
2. Select Security Rule Name DataConnection and press Edit button.
3. Tick Disable and press Apply button.
   
   
   
   
4. Press Create new button to create a new Security rule. Enter below.
   
   

   Name: DisableCustomConnectors
   Description: This custom rule disables Custom Connectors for user group “Sydney”
   Resource filter: DataConnection_*
   Action: Create
   Condition: ((resource.type!="folder" and resource.type!="Custom") and (user.group="Sydney"))
   Context: Only in hub

   
   
   
   
5. Press Apply button 
6. Press Create new button to create new Security rule. Enter below and press Apply button.
   
   

   Name: DataConnectionForNormalUsers
   Description: This custom rule is for Data Connections except User Group “Sydney”. Custom Connection creation enabled.
   Resource filter: DataConnection_*
   Action: Create
   Condition: ((resource.type!="folder" and user.group!="Sydney"))
   Context: Only in hub

   
   
   
   
   
7. Press Apply button
    

Upgrading Qlik NPrinting fails with:

Conflicting -boot options

An identical error is thrown when uninstalling Qlik NPrinting, even when following the How to uninstall Qlik NPrinting instructions. 

Environment

• Qlik NPrinting any version

Cause

The failure occurs during the Messaging service stop and start process.

Resolution

To resolve the issue with the Messaging service close and start process, create a variable which sets the correct configuration for the Qlik NPrinting server and allows us to bypass the problematic initialization code blocking the upgrade:

1. Set the system environment variable RABBITMQ_NODENAME with value rabbit@localhost
   The variable must be created if it does not exist.
   See How to Edit Environment Variables on Windows 10 or 11 for an example of how to modify a System Variable in Windows. 
2. Upgrade Qlik NPrinting