Analyzer capacity license & Signed License Key (JWT) - Issues

[witty]

So recently we decided to add a Capacity (6min Bundle License - not token) to our site and received our license as a signed license key and activated. (Running Feb 2019)

• https://help.qlik.com/en-US/sense/February2019/Subsystems/ManagementConsole/Content/Sense_QMC/analyz...
• https://support.qlik.com/articles/000072102

Now the issue is that the LEF information is gone  under site management; so you cannot review what the effective details are. Then also the License monitor app does not show any of the minute bundles being available so we have no clue if its "active" As far as I know there is no public interface to control/monitor this properly...

So now how do I make License access rules without allocating full seat/full time Analyser ones? Any one tried and done this? The recommended QRS api methods look the same from a JSON perspective as the ones created through the UI so we assume it will be assigning the real ones - which means we would be freezing those in for 7 days testing that. However we want to control those manually and only assign the minute ones based on rules.

We reviewed this: https://www.youtube.com/watch?v=VRfI3siVZOY

But that was not really clear which license to apply - is it the resource filter that controls that?

Is this the correct one?

License.AnalyzerTimeAccessType_...

License.AnalyzerTimeAccessType_*

In the Youtube comments it says this rule is deployed during install/upgrades but that is not true for us on 13.9.2

[witty · Accepted solution]

So our main issue has been this:

https://support.qlik.com/QS_CaseWizardKnowledgeArticle?id=kA53z000000fzCKCAY

This was added recently:

If you have access to the LEF for the license, for analyzer capacity to function you need both:

ANALYZER_TIME;1000;;
ANALYZER_TIME_UNIT;6;;

We were missing the Unit - BE CAREFUL before applying a signed license key that is broken - it does not allow you to refresh/update manually and you will have to wait until it happens - so we are told.

[witty]

In the end we acquired a 2nd JWT key and were able to force the update by swapping the keys back and forth.