What is a CAL
A QlikView license is referred to as a Client Access License (commonly called as CAL). To access the QlikView Dashboards deployed in QlikView Server, users need a Client Access License (CAL). The CALs are purchased with QlikView Server and tied to the QlikView Server Serial Number. A CAL is never transferred to a client, but a client uses the CAL when connecting to the server or, if a cluster license is used, a specific QlikView Server cluster. CALs cannot be transferred between different QlikView Server clusters. Developers can work with the QlikView documents by leasing a license from the Server.
You can read this post about how to lease the license.
Types of CALs
Qlik offers different license types depending on the usage. Following are the CAL types available for QlikView deployment
- Named CAL
- Document CAL
- Session CAL
- Usage CAL
A Named CAL is assigned to a User who can access unlimited QlikView documents deployed in one QlikView Server. A Named CAL can be transferred to another user, but it takes 24 hours to quarantine before the Named CAL can be assigned to another user. There is no time limit for the user to access the Dashboard.
Named User CAL is used as a dedicated user license, means a user has the privilege to access as many documents as he/she likes. This license can also be used for the local QlikView Desktop client for development of applications by leasing the license from Server. This is highest form of license.
Named CALs are generally used in the following scenarios
- Is used for users within an organization that need dedicated access to QlikView.
- For QlikView Developers, Power Users, and sometimes Executive level Managers who needs access to all the Dashboards.
- Power users, Business Analysts, Project Managers and Testers
A Document CAL allows one user to open ONE QlikView Dashboard deployed in QlikView Server. The license is perpetual and will allow the user to open a single document into perpetuity. If User wants to access multiple Dashboards then multiple Document CALs (One for each Dashboard) need to be assigned. A Document CAL can be transferred to another user, but it takes 24 Hours quarantine before the transfer.
Document CALs are generally used in the following scenarios:
- Commonly for organizations that have QlikView deployed departmentally and users within each department only need access to specific QlikView documents
- Very flexible – DOC CALs allow for many combinations
- Very Cost-effective way to expand QlikView usage departmentally
- Include users within departments that ONLY need access to applications specific to their departmental responsibilities
A Session CAL allows any user, identified or anonymous/unidentified user to access Qlikview Dashboards deployed in the Server for a minimum period of 15 minutes. This type CAL is not tied to user or a machine, and it serves in First Come First Serve basis. For Session CALs each client (Browser) is referred to as unique instance (for example, the Ajax Client, Qlikview Desktop, or IE Plugin) on the user’s machine. The Sessions that end in less that 15 minutes still consumes minimum 15 minutes and it terminates after the 15th minute. There is no maximum session length, but this can be configured in Qlikview Server.
Session CALs are generally used in the following scenarios
- Commonly deployed for organizations that have a larger user base and are looking for a cost-effective way to deploy QlikView
- Similar to concurrent licensing but is a 1:1 ratio between CAL and documents.
- Deployed for frequent QlikView users who don’t need dedicated access
- Include users in support functions and at times Mid-Level Management
A Usage CAL allows any user to access one QlikView Dashboard deployed in QlikView Server from one client for a period of 60 minutes per 28-day period. If a user exceeds the 60 minute time limitation, the user will have consumed two Usage CALs without any warning being given to the user. The Usage CALs is refreshed for every 28 days.
The Usage CAL is designed to accommodate overflow usage during peak times. It is not tied to a User or Machine.
Usage CALs are generally used in the following scenarios
- Commonly deployed within organizations to handle overflow users during peak usage times
- Very cost-effective for large organizations that have many casual users (i.e. viewing month-end reports)
In the second part, we’ll see the CAL Access Flow…