QMC resources overview

All resources that are available in the QMC are described briefly in the following table.

Resource Description

w Apps

A Qlik Sense app is a task-specific, purpose-built application. The user who creates an app is automatically designated as the owner of the app. An app can be reused, modified, and shared with others.

You can create and publish apps to streams from the Qlik Sense hub, if you have the appropriate access rights. Apps can also be published from the QMC. To publish an app that is created in a Qlik Sense Desktop installation, you must first import it, from the QMC. The security rules applied to the app, stream, or user, determine who can access the content and what the user is allowed to do. The app is locked when published. Content can be added to a published app through the Qlik Sense hub in a server deployment, but content that was published with the original app cannot be edited.

Content libraries

A content library is a storage that enables the Qlik Sense users to add shared contents to their apps.

The user who creates the content library automatically becomes the owner of that library. The library and the library objects can be shared with others through security rules defined in the QMC.

8 Data connections

Data connections enable you to select and load data from a data source. All data connections are managed centrally from the QMC. Data connections are created in the Qlik Sense data load editor. The user who creates a data connection automatically becomes the owner of that connection and is by default the only user who can access the data connection. The data connection can be shared with others through security rules defined in the QMC.

When you import an app developed on Qlik Sense Desktop, existing data connections are imported to the QMC. When you export an app from a server, existing data connections are not exported with the app.

Note: If the name of a data connection in the imported app is the same as the name of an existing data connection, the data connection will not be imported. This means that the imported app will use the existing data connection with an identical name, not the data connection in the imported app.
8 Analytic connections

Analiz bağlantılarını kullanarak harici analizi, iş keşfinizle tümleştirebilirsiniz. Analiz bağlantısı, harici bir hesaplama altyapısını çağırarak komut dosyalarında ve grafiklerde kullanabileceğiniz ifadeleri genişletir (bunu yaptığınızda hesaplama altyapısı, sunucu tarafı uzantısı (SSE) olarak hareket eder). Örneğin, R için bir analiz bağlantısı oluşturabilir ve verileri yüklerken istatistiksel ifadeleri kullanabilirsiniz.

4 App objects

You can manage the following app objects:

  • Sheets
  • Stories

The user who creates an app is automatically designated as the owner of the app and its app objects. The app objects are published when the app they belong to is published. The users can add private app objects to the apps and share them by publishing the app objects from Qlik Sense.

ã Streams

A stream enables users to read and/or publish apps, sheets, and stories. Users who have publish access to a stream, create the content for that specific stream. The stream access pattern on a Qlik Sense site is determined by the security rules for each stream. By default, Qlik Sense includes two streams: Everyone and Monitoring apps.

An app can be published to only one stream. To publish an app to another stream, the app must first be duplicated and then published to the other stream.

Note: All authenticated users have read and publish rights to the Everyone stream and all anonymous users read-only rights.Three of the predefined admin roles (RootAdmin, ContentAdmin, and SecurityAdmin), have read and publish rights to the Monitoring apps stream.

 

x Tasks

Tasks are used to perform a wide variety of operations and can be chained together in just any pattern. The tasks are handled by the Qlik Sense Scheduler Service (QSS). There are two types of tasks:

  • Reload
  • User synchronization

Execution of a task is initiated by a trigger or manually from the tasks overview page. You can create additional triggers to execute the task and there are two types of triggers: 

  • Scheduled
  • Task event
y Users

Users are imported from a user directory via a user directory connector in the QMC.

f Audit

On the QMC audit page, you can query for resources and users, and audit the security rules, load balancing rules, or license rules that have been defined in the Qlik Sense system.

Ä Security rules

The Qlik Sense system includes an attribute-based security rules engine that uses rules as expressions to evaluate what type of access users should be granted for a resource.
f Custom properties

You create a custom property to be able to use your own values in the security rules. You define one or more values for the custom property, and use these in the security rule for a resource.

ä License management

The License Enabler File (LEF) defines the terms of your license and the access types that you can allocate to users. There are two major license types: one that is user-based and one that is token-based.

  • User-based license: you can allocate professional access and analyzer access. The LEF determines the distribution of the two access types.
  • Token-based license: you can allocate user access and login access. The LEF determines the number of tokens that you can allocate to the two access types.

In addition to these two types there is the analyzer capacity license that is similar to analyzer access regarding available features, but where consumption is time based (analyzer time).

An access type allows users to access streams and apps within a Qlik Sense site.

Note: If you want to set up Qlik Cloud Services or Qlik Sense Enterprise for elastic deployments, please contact your Qlik representative or Qlik Support to obtain a valid license for the setup.
g Extensions

Extensions can be several different things: A widget library, a custom theme, or a visualization extension, used to visualize data, for example, in an interactive map where you can select different regions.

z Tags

You create tags and apply them to resources to be able to search and manage the environment efficiently from the resource overview pages in the QMC.

On-demand apps Selection and template apps, as well as on-demand apps are published to streams from the QMC.
â User directory connectors

The user directory connector (UDC) connects to a configured directory service to retrieve users. The UDCs supplied with the Qlik Sense installation are Generic LDAP, Microsoft Active Directory, ApacheDS, ODBC, Access (via ODBC), Excel (via ODBC), SQL (via ODBC), and Teradata (via ODBC).

Note: No UDC is required for a local user to log on to Qlik Sense. However, for the local user to be able to access apps, you need to allocate access. You can use professional access rules or analyzer access rules (user-based license) or user access rules or login access rules (token-based license) to allocate access. Alternatively, a local user can first log on to be recognized as a user, and then be allocated tokens.

You create new user directory connectors in the QMC.

ã Monitoring apps A stream that contains the governance apps License Monitor and Operations Monitor that present data from the Qlik Sense log files.
v Service cluster

On a multi-node site, the service cluster stores configurations, such as persistence type, database connection, and static content folder, for all nodes. All nodes are linked to the service cluster so that the settings can be unified.

v Nodes

A node is a server that is using the configured Qlik Sense services. There is always a central node in a deployment and nodes can be added for different service configurations. There is always a repository on every node.

A Qlik Sense site is a collection of one or more server machines (that is, nodes) connected to a common logical repository or central node.

Note: In a Shared Persistence multi-node installation, you can make one or more nodes failover candidates. In the case of a central node failure, a failover candidate will assume the role of central node.
Note: In a multi-node installation, you manage the whole Qlik Sense site from the QMC on the central node. You can access the QMC from rim nodes, but requests from the QMC towards the repository are routed to the repository on the central node.
{ Engines

The Qlik Sense Engine Service (QES) is the application service that handles all application calculations and logic.

p Printing The Qlik Sense Printing Service (QPR) manages the export and printing of objects to PDF or image files.
å Proxies

The Qlik Sense Proxy Service (QPS) manages the Qlik Sense authentication, session handling, and load balancing.

å Virtual proxies One or more virtual proxies run on each Qlik Sense Proxy Service (QPS), making it possible to support several sets of site authentication, session handling, and load balancing strategies on a single proxy node.
á Schedulers

The Qlik Sense Scheduler Service (QSS) manages the scheduled tasks (reload of Qlik Sense apps or user synchronization) and task chaining. Depending on the type of Qlik Sense deployment, the QSS runs as master, slave, or both on a node.

H Repositories

The Qlik Sense Repository Service (QRS) manages persistence and synchronization of Qlik Sense apps, licensing, security, and service configuration data. The QRS attaches to a Qlik Sense Repository Database and is needed by all other Qlik Sense services to run and to serve Qlik Sense apps. In addition, the QRS stores the Qlik Sense app structures and the paths to the binary files (that is, the app data stored in the local file system).

ÓDistribution policies

Distribution policies are used to determine whether a published app can be distributed to deployments in Qlik Sense Enterprise for elastic deployments or Qlik Cloud Services. To be distributed, a published app must have a distribution policy connected to it.

ô

Load balancing rules

The load balancing define the nodes' access rights to resources.

® Certificates

Qlik Sense uses certificates for authentication. A certificate provides trust between nodes within a Qlik Sense site. The certificates are used within a Qlik Sense site to authenticate communication between services that reside on multiple nodes.