Deployment scenarios for Qlik Web Connectors

There are many ways to deploy the Qlik Web Connectors within your organization. On this page, we show you four common deployment scenarios.

Note: In the scenarios where the same machine hosts Qlik Web Connectors and the Qlik server, Qlik Web Connectors must run on the default port number 5555.

One machine

In this example, a single machine hosts Qlik Web Connectors and the Qlik server. Developers make API calls through the Qlik Web Connectors and they deploy apps to the server. End users can access apps from the same machine but only developers have login credentials for the Qlik Web Connectors.

Single server deployment

A deployment scenario where Qlik Web Connectors and the Qlik server are installed on the same machine, and only one set of users have Qlik Web Connectors login credentials.

Separate machines

This is very similar to the first example, the only difference being that the Qlik Web Connectors and Qlik server are installed on separate machines. The Qlik Web Connectors machine could also be in a DMZ with access to the internet, as in the Closed network example.

Multiserver deploy

A deployment scenario where Qlik Web Connectors and the Qlik server are installed on separate machines, and only one set of users have Qlik Web Connectors login credentials.

Cloned test and production environments

In this example, the Qlik Web Connectors are running on the same machine as the Qlik server, which is cloned for test and production environments. Developers can make API calls and deploy apps to both environments. End users access apps from the production environment.

In a cloned deployment

A deployment scenario in which the Qlik Web Connectors are hosted on the same machine as the Qlik server. The server configuration is cloned for test and production.
Note: We recommend that you have a process in place to mirror the test and production servers, including users who are setup on the test server.

Closed network

In this example, the Qlik Web Connectors are installed on a machine that is located inside a demilitarized zone (DMZ) with internet access. The developers, the end users, and the Qlik server are located inside a closed internal network. In this deployment configuration, the developers and the server make requests to the machine hosting the Qlik Web Connectors. The Qlik Web Connectors can make external and internal API calls from the DMZ but developers deploy apps only to the internal server. End users access apps on the internal server.

Closed network deployment

A deployment scenario in a closed network. The Qlik Web Connectors are hosted on a single machine capable of making external API calls. The QlikView server does not have internet access.
Note: The Qlik server could be hosted on the same machine as the Qlik Web Connectors in the DMZ.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?