Configure and Run the Qlik Cloud Connector

Configure and run the Qlik Cloud connector to import usages, filter spaces, and review object mappings and release history.

3 min read

This article explains how to use Qlik Cloud connector for DataGalaxy.

This connector is available in the following modes:

Desktop mode ✅SaaS Online mode ✅

Connector Overview

The connector allows importing metadata from a Qlik Cloud tenant. The retrieved objects and their correspondences in DataGalaxy are detailed in the following table:

Qlik Cloud ObjectDataGalaxy ObjectComments
(none)Application (root)A root level application is created during the import (to be named during setup) in the Uses module.
SpaceApplicationEach Qlik Sense Space is imported as a child application. The list of Spaces to be imported can be filtered (see the regex parameters below), all Applications in the scanned Spaces will be imported
ApplicationDashboardOnly published applications are taken into account
TableDatasetThe tables part of the data model of the application
FieldUsage fieldEach field available in the data model of the application, in a table
Master Item (Measures, Dimensions)Usage fieldEach Measures and Dimensions in the semantic layer of the application

Step 1: Installation

  • Download DataGalaxy connector from the portal (see here)
  • Extract the connector archive in the directory of your choice
  • Download the Qlik Cloud plug-in from the portal and copy it into the /lib directory of the connector

Step 2 : Running Qlik Cloud connector

  • After starting the connector, access Uses type connectors:
  • If it has been correctly installed, the Qlik Cloud plug-in appears in the list

The following information is requested:

ParameterMandatoryDescription
ServerYesQlik Cloud tenant address
AuthenticationYesChoose between legacy API Key and recommended OAuth M2M client
TokenYes (API Key)A valid Qlik Cloud token with permissions on the API and on each Space / Application to scan
Client IDYes (OAuth)Client ID of your M2M client with user_default + admin.apps:read + admin.spaces:read scopes (user_default can be omitted if you don't import Master Items)
Client secretYes (OAuth)Client secret of your M2M client
Root application nameYesRoot application name in the DataGalaxy Uses module, which will be used to store all Qlik Cloud applications. If the application does not exist, it will be created during the import.
Managed SpaceYesCheck this if you want to scan the Managed Spaces
RegexNoTo filter the Spaces to scan, provide a regular expression which should match with the names of the Managed Spaces you want to import. If you want to import only one specific Space, provide the name of the Space. If nothing is provided, all the Spaces will be imported. Example : ^[^#].*$ to import all the Managed Spaces whose name doesn't start with #.
Shared SpaceYesCheck this if you want to scan the Shared Spaces
RegexNoSame parameter as above but for filtering the Shared Spaces

Once this information has been filled in, you must test the connection in order to start the import procedure.

Technical Information

Qlik Cloud connector uses the Qlik Cloud REST APIs (https://qlik.dev/apis/rest/items) and the JSON-RPC API for reading the model of each application.

Releases

DatePlugin versionDataGalaxy releaseDesktop connector version (minimum)Description
27/10/20263.2.0v3.440.06.2.3Map missing attribute Expression for measures; New OAuth M2M auth mechanism; Optimizations in JSON RPC
29/09/20263.0.23.423.06.2.2New internal implementation to fix security vulnerabilities
01/09/20263.0.1v3.409.06.1.5Fixed an issue with the logs for online imports
21/05/20262.0.8v3.340.05.15.7Fix error message for authorization issue
24/03/20262.0.7v3.323.15.15.7Fixed a bug related to verbose logs
03/12/20252.0.6v3.286.45.15.3Fixed some issues related to Web Socket requests
23/08/20242.0.1v3.69.05.2.3Updated the logger to show more information when using verbose mode
26/07/20242.0.0v3.62.05.0.3Migrated from java 11 to java 17

Read more

Related articles

Was this page helpful?