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

Multi-cloud services

You have several options when deploying a Qlik Sense Enterprise on Windows environment. For an overview of the Qlik Sense multi-cloud architecture and your different deployment options, see Qlik Sense deployments in a multi-cloud environment. The services that you need to run in a multi-cloud deployment can be categorized as follows.

Typically the services running in a QCS deployment are similar to those running in a Qlik Sense Enterprise on Kubernetes deployment but are not accessible, because Qlik manages the infrastructure. You can connect to QCS SaaS but do not have the same configuration options as a Kubernetes deployment.

Services on Windows deployments

The services listed below are required if you use the multi-cloud capabilities in a Qlik Sense Enterprise on Windows deployment.

Service Description
App Distribution Service Distributes apps and associated metadata to defined distribution targets, based on policy-based app distribution rules.

Hybrid Deployment Service

Stores configuration details including credentials and URLs for all target environments in a multi-cloud deployment.

Hybrid Setup Console Service

Multi-cloud Setup Console UI functions for managing target environments configured in a multi-cloud deployment including credentials and service URLs.
Resource Distribution Service Publishes installed extensions and themes to the Resource Library in each cloud environment.

Services on Kubernetes and Qlik Cloud Services deployments

The services that you run in Qlik Sense Enterprise on Kubernetes can vary depending on your deployment requirements.

Service Description  
Chronos Scheduler back end service.  

Cloud hub

Serves the hub functionality to users in Qlik Cloud Services and Qlik Sense Enterprise on Kubernetes.

 

Collections

Organizes and structures content supplied to the hub. It also applies access control rules.  

edge-auth

Service that works together with external Identity Providers to authenticate users upon entry to the deployment. Also manages tickets that authorize secure access to internal resources.  

elastic-infra

A collection containing non-Qlik services: MongoDB, Redis, and ngingx-ingress. It bootstraps an elastic-infra deployment on a Kubernetes cluster using the Helm package manager. It starts up the basic resources needed to connect all the components and functionality required in a cloud environment.  

Engine

Handles all application calculations and logic.  

Feature Flags

Responsible for toggling features on and off in advanced scenarios.  

Licenses

The license service is used to enforce user licensing in Qlik Cloud Services and Qlik Sense Enterprise on Kubernetes.  
Locale Handles user locale selection for the client.  

Mira

Provides a discovery service for Engines in the deployment, their current health, and availability of applications.  

Policy Decision

Processes a set of rules on Qlik Cloud Services and Qlik Sense Enterprise on Kubernetes that perform ABAC security evaluation against Qlik objects (for example, apps). It is sometimes referred to as the Rules Service. It uses a REST API for the rules engine and management API for rule based policies and replaces the QRS Rules Engine, Policy Decision Service.

 

qix-sessions

Responsible for routing user session traffic to the Engine services.  

Resource Library

A general-purpose resource storage service for supporting content such as themes and extensions.

 

Tenant

Used to store and return tenant (user) information.  

User

Responsible for managing and retrieving user information.  

Sense Client

The Desktop and web browser instance of the Qlik Sense client run by developers on Qlik Sense Enterprise and by consumers on QCS and Qlik Sense Enterprise on Kubernetes.

 

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?