QlikWorld 2020 Global Conference. Join us to discover how to get the most from your data. Act fast. Register now and save.

Enterprise deployment

You can configure a Qlik Sense enterprise deployment in a variety of different ways to suit the needs of your organization. For example, you can install Qlik Sense services to run on a single node or on multiple nodes for better performance and scalability. In a small single-node deployment, you deploy all services to a single server, which we do not recommend for larger organizations.

This section provides three examples of Qlik Sense deployments.

The following terms are used in the deployment scenarios:

  • Central node: the central point for managing all nodes in a site.
  • Scheduler or Reload node: reloads apps on a schedule, but does not serve content to users.
  • Consumer node: serves apps to users, but is not used to create, process, or reload data.
  • Development node: allows users to create and reload new apps, but does not serve normal consumer traffic.
  • Proxy node: provides load balancing of user traffic to other nodes but does not contain a Qlik Sense Engine Service (QES).
Note: An alternative to using a proxy node is to have a proxy installed on each consumer node and balance the traffic using a hardware load balancer.

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?