Follow

Connect to Qlik Sense Enterprise

Here we will explain what is needed to make a connection to a Qlik Sense Enterprise server work. This will be for both Semantic Qlik models and Qlik models. There is two ways to do this and both will be explained below.

Prerequisites for access

First off we need some things set up before we can get it to work.

Ports

There is a list of ports that needs to be opened through the firewall. You can read about which ones are used here Server-Deployment-Ports. Though in general you only need to make rules for these.

For Proxy connections

  • 80 (HTTP) - Optional
  • 4248 (HTTP Windows Authentication) - Optional
  • 443 (HTTPS)
  • 4244 (HTTPS Windows Authentication)

For Certificate connections

  • 4747 (QES Listen Port)
  • 4748 (From QRS)

Create a inbound rule for these on the server where Qlik Enterprise is installed. Though this is not needed if you have TX DH located on the same server.

Users

Your users need ContentAdmin rights to deploy and execute models.

1.PNG

The user also needs rights to create files in a folder if you use QVD files. In this case for the svc_qlik user as well.

4.PNG

Proxy

You can create your own proxy to connect to and the things you need to set up are these. It needs a unique Description name with no blank spaces, a unique Session cookie header name and the load balancing needs to point to the server node.

13.PNG

It also needs to be associated by the proxy server.

16.PNG

Though as standard the default one can be used if TX DH is to be used on the same server.

14.PNG

Certificate

To use the certificate, you need to export it. Add a password and press export. It will be stored in this path "C:\ProgramData\Qlik\Sense\Repository\Exported Certificates". Go there and copy it and store it on a location that is available for all users of the program, so not "Documents", but a specific Qlik folder on the C drive.

12.PNG

SQL Server

There are some services that are running.

10.PNG

The user that runs the engine service needs read rights on the DWH table.

15.PNG

Lastly the servername cannot be localhost and ., it needs to be the hostname instead.

Connect with a proxy setup

When you set it up, you use the correct protocol, add the server name, the port, the virtual proxy you made and the account you want to run as.

11.PNG

Test the connection to see if it works.
Remember the servername cannot be localhost and ., it needs to be the hostname instead.

3.PNG

You can leave the port and virtual proxy prefix empty, the port expects 443 when you use HTTPS and will use this if it is empty and the default virtual proxy is empty in its name.

Below is how it is set up in a semantic model. Also it is using the default settings. Remember that the file path needs to be available for all users that will execute this program.

2.PNG

Then you can deploy and execute your qlik models.

Connect with a certificate setup

The setup needs a port, a user account, the certificate that was exported and the password you gave it. Port 4747 is default and it is what is chosen if the field is left empty.

6.PNG

Test the connection to see if it works.
Lastly the servername cannot be localhost and ., it needs to be the hostname instead.

3.PNG

Below is how it is set up in the semantic model.

17.PNG

Then you can deploy / execute your Qlik models.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.