Qlik Analytics Platform overview
The Qlik Analytics Platform (QAP) is a developer platform for building custom analytic applications based on rich frontend and backend APIs.
It gives you full API access to the Qlik associative engine to build rich and smart data-driven analytic applications. You can take advantage of the Qlik Analytics Platform and build web applications for extranet and Internet deployment, for example.
Components of the Qlik Analytics Platform
The Qlik Analytics Platform consists of the following components:
- Qlik Management Console (QMC) and Dev Hub
-
Qlik Sense APIs and SDKs
Information noteAs the App Integration API relies on the Qlik Sense Hub, it is not available in a QAP environment. - Qlik associative engine and Qlik Sense supporting services
Licensing model
This section describes the differences between the licensing for Qlik Sense Enterprise and Qlik Analytics Platform. The Qlik Analytics Platform is licensed on capacity (CPU cores) in the deployment.
Tokens and access passes
The Qlik Analytics Platform license does not make use of tokens and access passes.
Capacity-based licensing
The Capacity-based licensing property group contains the properties for controlling the distribution of CPU cores in the Qlik Sense system. With this license you can optimize your system and balance load by configuring the number of cores to use on a CPU.
| Property | Description |
|---|---|
| Available cores (from license) |
Total number of cores that is available for allocation. Specified by the license. |
| Active cores (this engine) | Number of cores that is active on this engine. |
| Cores allocated (all engines) |
Total number of cores that has been allocated for all engines.
|
| Cores to allocate (this engine) |
Number of cores to be allocated for the currently selected engine. You can enter a larger number than specified by the license, but you will still only be able to use the number of cores that the license specifies. |
Distribution of engine cores
By default, the engine cores are evenly distributed on the nodes within the site. If the number of cores available via the license is uneven in relation to the number of nodes in the site, the extra cores are distributed as follows: the first one to the node acting as Central node and the second one to the next node available.
Example: Four cores distributed on two nodes
The default distribution of four cores on two nodes is two cores on the Central node and two cores on the Rim node.
Example: Eight cores distributed on three nodes
The default distribution of eight cores on three nodes is three cores on the Central node, three cores on Rim node A and two cores on Rim node B.