Businesses commonly enforce strict firewall policies that block external access to their data sources. This presents a challenge when such businesses need to access their data from the cloud for analytics. Qlik Data Gateway - Direct Access overcomes this challenge by eliminating the need to open inbound firewall ports. Operating behind your organization’s firewall, the Direct Access gateway allows Qlik Sense SaaS applications to securely access behind-the-firewall data, over a strictly outbound, encrypted, and mutually authenticated connection.
The Direct Access gateway should be installed on a Windows Server 2016/2019 machine behind your firewall, that is able to access your data source.
Do not use a server that already has Qlik Sense Enterprise on Windows or Qlik DataTransfer installed.
Tip noteFor optimal performance, install the Direct Access gateway on a server that is as close as possible to your data source.
Required software
- Windows Server 2016/2019
Two different Microsoft .NET versions should be installed:
Microsoft Visual C++ 2015-2022 Redistributable (x64). The Direct Access gateway setup will prompt you to install the redistributable if it detects that it is not currently installed.
Other requirements:
- Authorized login to a Qlik Sense Business or Qlik Sense Enterprise SaaS tenant. If authorization is required, contact your tenant Administrator (typically the individual who executed the initial license agreement).
- Ensure installations of required .NET versions
- Download and install QlikData Gateway from SaaS to gateway server. (
- Software can be downloaded at your tenant under Management Console > Data Gateways with the Deploy button)
- Run below steps from CMD as Admin:
cd C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent
connectoragent qcs set_config --tenant_url <<tenant url here>>
connectoragent qcs generate_keys
connectoragent qcs get_registration
4. Create Gateway from Mgmt Console (paste key from get_registration command above)
5. Run below steps from CMD as Admin:
connectoragent service start
Internal ports
Below is a list of ports used for communication by internal data gateway processes. If any of these ports is being used by another application, reconfigure the other application or uninstall it.
- 5000 (Connector Agent REST API)
- 3005 (ODBC Connector REST API)
- 9027 (DCAAS REST API)
- 50060 (ODBC Connector gRPC)
To check internal port use:
# For Windows PowerShell users
PS C:\> Test-NetConnection -InformationLevel detailed -ComputerName hostname -Port 5900