Skip to main content Skip to complementary content

Qlik Data Gateway - Data Movement overview

Connecting to data sources located behind your firewall must be done using Qlik Data Gateway - Data Movement.

Operating behind your organization’s firewall, Qlik Data Gateway - Data Movement allows you to move data from your enterprise data sources to cloud targets, over a strictly outbound, encrypted and mutually authenticated connection. By eliminating the need to open inbound firewall ports, Qlik Data Gateway - Data Movement provides a secure and trusted means for accessing your enterprise data.

Qlik Sense Enterprise SaaS Government note

Qlik Cloud Government supports using Qlik Data Gateway - Data Movement when the Linux platform where Qlik Data Gateway - Data Movement is installed is configured to run in a FIPS 140-2 approved mode of operation, also known as "FIPS mode".

Information noteThe Data Movement gateway documentation always reflects the capabilities of the latest application version. If you’re not using the latest version, your system administrator is encouraged to upgrade immediately. For information on upgrading, see Upgrading Data Movement gateway

Security

A unique key-pair is established for each Data Movement gateway server connected to the Qlik Cloud tenant. This key pair is used for authentication and for end-to-end data encryption on top of the HTTPS transport level encryption. Additionally, as communication with Qlik Cloud and data transfer is initiated via outbound ports only, you do not need to open any inbound ports to your corporate network.

Data Movement gateway architecture

Qlik Data Gateway - Data Movement Architecture

The high-level communication sequence is as follows:

  1. The Data Movement gateway establishes a mutually authenticated and encrypted connection to Qlik Cloud, using HTTPS.

  2. Qlik Cloud sends the landing task execution instructions to the Data Movement gateway, which in turn reports the task status to Qlik Cloud.

  3. The Data Movement gateway pushes the data from the enterprise data source to the data warehouse target.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!