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.
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.
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.
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.
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.
