Skip to main content Skip to complementary content

Data Movement gateway prerequisites and limitations

This section describes the prerequisites for using Data Movement gateway as well as any limitations you should be aware of.

System requirements

Data Movement gateway should be installed on a Linux machine located in the data center or in a VPC (Virtual Private Cloud) network. Do not use a machine that already has Qlik Replicate installed on it.

  • Unless you are installing as root, you need sudo permission to run the Data Movement gateway RPM.

  • To register a gateway on the tenant, you need tenant admin access.

Tip noteFor optimal performance, install the Data Movement gateway on a server that is as close as possible to your data source.

Supported Linux platforms

Data Movement gateway is certified for installation on Red Hat 8.x (64-bit) and Red Hat 9.x (64-bit).

Information noteAlthough Data Movement gateway is certified on Red Hat, it is also supported on corresponding and compatible Linux distributions.

Ports

Port HTTPS/TCP-443 should be opened for outbound communication to <tenant-id>.<region>.qlikcloud.com.

Recommended hardware

The recommended hardware is outlined in the table below.

Recommended hardware configurations
  Basic System Large System Extra-Large System Notes:

Processor

Quad core

Quad core base

Dual-core per task

8-core base

Quad core per task

Additional cores are useful in any of the following situations:

  • Many tasks running in parallel
  • Full-load performance priority
  • Multiple full-load processes running in parallel

Memory

8 GB

32 GB

64 GB

More memory is useful in any of the following situations:

  • Many tasks running in parallel
  • Long-running transactions on the source endpoint (for example, monthly batch processing)
  • Many active users on the source system

Disk requirements (SSD is recommended for optimal performance)

320 GB

500 GB

RAID

500 GB

RAID

A faster disk is useful in any of the following situations:

  • Long-running source transactions that may not fit into memory
  • Using tasks that are set up to continue processing during target outage

A larger disk is required in any of the following situations:

  • Using tasks that are set up to continue processing during target outage
  • Very large source transactions that do not fit into memory

RAID is recommended for system recovery in case of disk failure for all configurations.

Network

1 Gbps

10 Gbps

Two 10 Gbps

-

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!