Understanding SLK and LEF license methods

[suportetts]

Hello Team! We've facing some question about licensing and compatibility to expand the disponibilization for our clients.

I found some articles explaining about this new kind of license called Signed License key (SLK). Today in our environment we use License Enabler File (LEF).

Those two kind of licensing can work together?

If yes, which impact we should prepare to face?
If no, what kind of changes should be done to adapt the environment in this new kind of licensing?

Best regards

[Jill_Masinde · Accepted solution]

@suportetts  Signed License key (SLK) and CAL both have License Enabler File (LEF) which lists the attributes of the licenses. 

SLK  license has access types (Professional, Analyzer, and Analyzer Capacity) and while CALs (User, Document, Session, and Usage which you currently have. 

You cannot combine the two licenses concurrently you can only use one or the other.

Use case depends on your environment.  As of the April 2019 releases of QlikView and Qlik Sense, QlikView customers can use a unified license in multiple deployments. A unified license shares the same signed key between:

• multiple Qlik Sense Enterprise deployments
• multiple QlikView Server deployments
• QlikView Server and Qlik Sense Enterprise deployments

The below article provides more depth about 2 licenses.

https://help.qlik.com/en-US/qlikview/May2022/Subsystems/Server/Content/QV_Server/QlikView-Server/QVS....