In this example we will review ways that the API can be used to work with Named CALs with a couple of examples attached.
Note - Under the terms of the QlikView Licence Agreement, Named CALs are intended to be persistant for a user i.e. they should not be shared or deleted unless that user leaves an organisation or role.
Working with Named CALs
Named CALs are allocated user and stored in .pgo files on the QlikView sever. Using the API this data can be consumed and edited to export/add/delete Named CALs. In these examples we will mainly be working with the AssignedNamedCAL object.
First off all you need to connect to the management API and handle the Service Key process:
To begin we need to reference the QlikView server we want to connect to so we can read its settings. ServiceInfo is an array of all the services of a given type, so if you had more than one QV Server you would need to use the right one, for now we will assume its just one.
Finally save the new CAL Configuration to the server
The CALConfigurationobject contains all of the settings associated with server wide licences, that is Named, Session and Usage CALs. You can view a lot more information by browsing through the various properties of this object.