Once our Configurable ODBC connection in DSC is setup, we are ready to start assigning CALs to our documents.
First let’s take a look at the users coming from the DB. Go to QMC –> Users –> User Management. Click on the “Search in” drop down list. You should be able to see the ODBC connection we created. Then look for a user or type “*” in the search box to bring all users.
After having created our Entity and Group views, it is time to setup the Directory Service Connector in QMC.
Basically, Directory Service Connector keeps track of the users and it is needed for other management tasks that involve users, such as licence assignment.
In my example, we have all our users in a database. In order for Qlikview to access these users, we must setup a Configurable ODBC connection.
This series of posts are intended to help you integrate Single Sign On using an ODBC connection to a database. This database will contain the users used for authorization in Qlikview.
I will not be covering the authentication side of Single Sign On as it’s not related to Qlikview. However, information on how to create webtickets (necessary to implement single sign on) can be found in Qlikview Community.
What is Single Sign-On (SSO)?
Single Sign On is a user authentication process that allows said user to access different systems. By implementing SSO the user only enters one user and password. This will then authenticate the user against different system within an organization.
Implementing Single Sign On in Qlikview
Today a business user asked me if he could save selections so when he opens a document, he can get his defaulted selections.
The first thing I thought was to use an onOpen trigger. To my surprise, onOpen triggers don’t work in Ajax. A weak point about this solution, is that I wanted to create a table with users and predefined selections and select these onOpen based on the user.
After thiking a little bit more (yes, it sometimes good to think), I remembered the “Recovery Session” feature in Qlikview Server.
This option allows users to close a document and save their selections. When they reopen the document, the session will be recovered and all
selections will remain.
This option can be found in QMc: System –> Setup –> Choose Qlikview Server –> Documents –> Check option “Allow Session Recovery”
Qlikview Server files .pgo can give us valuable information. PGO (Persistent Group Object) files are created by Qlikview Server and stored or placed in our root folder. The files are locked while the Qlikivew Server is running. The different pgo files contain information about borrowed CALs, CALs in use, Server settings and ticket data.
These files can’t be accessed without first converting them to .xml files.
Creating a .xml copy of a .pgo file
1) Stop the Qlikview Server service from the.
2) Add PgoAsXmlAlso=1 right under [Settings 7] in the Setting.ini file located in %ProgramData%\QlikTech\QlikViewServer. The Setting.ini file should look like this:
3) Restart the Qlikview Server service
4) Go to the root folder where the .pgo files are. You will then see the .xml files.
I hope you find this useful.
Keeping track of licences in a big environment can be a bit of a hassle.
In case you didn’t know, we can literally loose licences if we don’t make sure to follow all the necessary steps before deleting or updating a file name.
But, how do we know we are missing licences?
The answer to this question, it’s very simple and easy to spot.
If you delete or change a file name before removing any licences assigned to this file, then those licences will be lost and you won’t be able to use them in any other application.
For example, let’s suppose we have a file “Qlikview Document.qvw” with 1 document CAL assigned to it. If we now go ahead and delete this file (without removing the licence), the licence will be lost and the file will show up in QMC in capital letters.
Whenever we see a file like this, we should know we need to take action.
The first thing would be to restore the file we just deleted. If someone else deleted the file, it’s probably that Read More…