AMC - Application Management Console, an alternative to the QMC for large Enterprise environments

[Mario_Petre]

The Application Management Console is provided as is. No ongoing support or development is offered.

What is it?

A content library deployable on any modern Qlik Sense environment to help facilitate application and stream management without accessing the QMC. It is optimised for speed and dramatically reduces the number of requests triggered against the Repository Service, helping with the site availability and performance.

Will it work with my version?

The AMC was designed to be version agnostic and backwards compatible, as it makes use of existing APIs and technologies the product already leverages. As it is delivered as a content library, there is nothing to install.

AMC will work with Qlik Sense September 2018 and newer.

Who is it for?

System administrators who wish to offer an alternative, better-performing way of managing Qlik Sense resources (apps, streams, data connections and custom properties) without accessing the QMC. The QMC, by default, will pull larger result sets from the Repository when requesting, for example, the list of apps and streams a content administrator can manage. This content must subsequently be filtered based on the user’s access level, defined via Security Rules. Complex environments often use large rule sets to govern this access. The AMC was designed to first evaluate which resources should be displayed, then only request those resources from the Repository. This has a positive performance effect, helping reduce the Repository workload as well.

Where can I find it?

The AMC is shipped with Qlik Sense Enterprise for Windows since the April 2020 Release. It can be found under the Tools folder in your base installation directory: C:\Program Files\Qlik\Sense\Tools\AppManagementConsole

How do I deploy it?

A “Readme” file with instructions is available in the path mentioned above, this will guide through setting this up in a Content Library. Security rules for AMC will use the QMC context, not Hub.
The AMC can be accessed from any node, not limited to the Central Node or your Default Proxy location, however all calls to the Repository will be routed through your Central Node (same as QMC).

Access Control

We recommend you explicitly lock out access to sections in the QMC for users who are supposed to be routed to the AMC, this will prevent them from side-stepping and performing high-cost actions in the QMC itself. Then include these users via the Content Library-specific rule that was created along with the library itself.
You may also consider redirecting users via a Reverse Proxy that may already exist in front of your Qlik Sense deployment, which can be configured to work on origin basis (as well as other parameters). Alternatively, you can also add custom Virtual Proxy with “amc” prefix to make navigating to it easier.

How to use it:

Related Content:

QMC performance – best practices