QMC resources overview
All resources that are available in the QMC are described briefly in the following table.
Resource | Description |
---|---|
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 an app from the Qlik Sense hub, if you have the appropriate access rights. Apps are published to streams from the QMC, which is a part of Qlik Sense. To publish an app that is created in a Qlik Sense Desktop installation, you must first import it, by using 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. |
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. Information noteIf 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.
|
App objects |
You can manage the following app objects:
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 in 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. Information noteAll 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.
|
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:
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:
|
Users |
Users are imported from a user directory via a user directory connector in the QMC. |
Audit |
On the QMC audit page, you can query for, and audit, the security rules or sync 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 a user or users should be granted for a resource. |
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 these values can be used in the security rule for a resource. |
License and tokens |
The License Enabling File (LEF) determines the number of tokens that you can allocate to different access types. An access type allows the users to access streams and apps within a Qlik Sense site. You can adjust the token usage according to the usage need over time. |
Extensions |
Extensions can be used to visualize data, for example, in an interactive map where you can select different regions. |
Tags |
You create QMC tags and apply them to resources to be able to search and manage the environment efficiently from the resource overview pages in 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, Local Users, and ODBC. 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. |
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. Information noteIn a multi-node installation, you manage the whole Qlik Sense site from the QMC on the central node.
|
Engines |
The Qlik Sense Engine Service (QES) is the application service that handles all application calculations and logic. |
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. |
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. The QRS also manages the synchronization in multi-node Qlik Sense sites. 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). |
Sync rules | The sync rules 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. |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!