Which services should be running on a Consumer Node in a Qlik Sense environment?

In a Qlik Sense environment, a Consumer Node is tasked primarily with handling user access and interactions, meaning it needs to manage incoming user requests effectively. The essential services that should be running on a Consumer Node include the Engine service, Proxy service, and Repository service.

The Proxy service acts as the entry point for all client requests. It authenticates users and routes requests to the appropriate services, which is vital for smooth operation in a multi-node setup. The Engine service processes the data requests and executes the business logic once the Proxy has directed the request correctly. The Repository service handles the application and user data, allowing for centralized management and governance.

Thus, having the Engine, Proxy, and Repository services running ensures that the Consumer Node can effectively facilitate user interactions by managing authentication, processing data, and overseeing data integrity and access control. The interactivity and responsiveness expected in a Consumer Node depend on these services' operational capability.