Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
poppypearce
Creator
Creator

To Export License Details into Excel

Hi,

I want to export the License related details into excel from QMC. For example Username, License Assigned Date, Type of license, last used details.

Is there any option to export these details.

1 Solution

Accepted Solutions
Peter_Cammaert
Partner - Champion III
Partner - Champion III

Not really but you can try. The data is there but will be difficult to interprete in a correct way. In theory:

  • a Document CAL assignee only has access to the AccessPoint
  • a Named CAL assignee has access to the AccessPoint, and can use a licensed copy of QV Desktop if license leases have been enabled in QMC.

So the problem group might be the Named CAL users. You won't disable license leases because it's a global setting which effectively shuts off all development. If you enable license leases, then there is no foolproof method to block a certain user from leasing a license (unless your managed enterprise PCs disallow the installation of "foreign" software). And anybody can use QV Desktop in PE mode and develop documents with it anyway.

There is however a way out of this: if you enable the PGOAsXmlAlso setting in QlikView Server, you will get two usable pgo files in readable format:

  • CalData.pgo.xml                    contains all license assignments and the corresponding user names.
  • BorrowedCalData.pgo.xml     contains information about all active license leases and the corresponding user names. Those are probably the developers.

Named CAL users that are present in the first but not in the second are probably not developers.

Best,

Peter

[Edit] Please keep in mind that many concepts that administrators find self-evident, have no match anymore in QlikView world. A long time ago, there used to be a difference between AccessPoint users, Report developers and real developers, purely based on the type of client license they were using. Ever since the move to server-based license management, that difference has disappeared. A Named CAL user can be a developer, an accesspoint user (having access to 4 documents or more) or both. As I said before, even a PE user can be a developer, although in the long-run this will become extremely impractical...

View solution in original post

5 Replies
Chip_Matejowsky
Support
Support

Hey Poppy,

There isn't a built-in functionality to do this within QlikView Server. You can edit the QlikView Server's settings.ini file so that the .PGO files are written to an XML file (see thread PGO to XML QlikView 12), and you could then read the CalData.pgo.xml file contents for allocated CALs. Please note that enabling the PGO as XML functionality could result in a decrease in performance, so it isn't recommended to leave this setting in place permanently.

Hope this helps,

Chip

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
poppypearce
Creator
Creator
Author

Hi Chip,

Thanks a lot for your information.

I wanted to know the details of Doc Admin (Developers with Deployment Access) & the Normal Users(Developers), Usually All the Licenses will show as Named CAL in the Session Log, but incase if we want Detailed information like who are Developers and Who are Doc Admin's...is there a way to get this data from XML Files??

Regards,

Poppy

Chip_Matejowsky
Support
Support

Hi Poppy,

No there isn't a way to do that which I am aware of within QlikView. If that information is available in Active Directory (if that's what's used), then there should be some way to obtain it from there outside of QlikView.

Hope this helps,

Chip

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
poppypearce
Creator
Creator
Author

Hi Chip,

Thanks for the info.

is there any way to differentiate the users having access only to Accesspoint and users having access to both Accesspoint and Qlikview Desktop, how do we identify this??

Regards,

Poppy

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Not really but you can try. The data is there but will be difficult to interprete in a correct way. In theory:

  • a Document CAL assignee only has access to the AccessPoint
  • a Named CAL assignee has access to the AccessPoint, and can use a licensed copy of QV Desktop if license leases have been enabled in QMC.

So the problem group might be the Named CAL users. You won't disable license leases because it's a global setting which effectively shuts off all development. If you enable license leases, then there is no foolproof method to block a certain user from leasing a license (unless your managed enterprise PCs disallow the installation of "foreign" software). And anybody can use QV Desktop in PE mode and develop documents with it anyway.

There is however a way out of this: if you enable the PGOAsXmlAlso setting in QlikView Server, you will get two usable pgo files in readable format:

  • CalData.pgo.xml                    contains all license assignments and the corresponding user names.
  • BorrowedCalData.pgo.xml     contains information about all active license leases and the corresponding user names. Those are probably the developers.

Named CAL users that are present in the first but not in the second are probably not developers.

Best,

Peter

[Edit] Please keep in mind that many concepts that administrators find self-evident, have no match anymore in QlikView world. A long time ago, there used to be a difference between AccessPoint users, Report developers and real developers, purely based on the type of client license they were using. Ever since the move to server-based license management, that difference has disappeared. A Named CAL user can be a developer, an accesspoint user (having access to 4 documents or more) or both. As I said before, even a PE user can be a developer, although in the long-run this will become extremely impractical...