Qlik View Licensing Agenda License Types Defined How
- Slides: 16
Qlik. View Licensing
Agenda • License Types Defined • How Do They Work Together? • When Would I Use Them? • Scenarios
License Types - Defined Client Access License (CAL): • Purchased with Qlik. View Server and tied to the serial number • CAL’s are Server Based – Not Client Based • CAL’s are specific to one (1) Qlik. View Server • Cluster Licensing is available for sharing licenses across Servers Qlik. View has 4 Types of Client Access Licenses (CALs) • Named User • DOC • Session • Usage
License Types - Defined Named User CAL • Based on User or Machine Identity • Can access unlimited Qlik. View Documents on 1 Qlik. View Server • User will always have access to Qlik. View Documents DOC CAL • Allows one user to open one Document • License is perpetual • License is associated with a Document and user • Sold in increments of 100
License Types - Defined Session CAL • Allows 1 User to have access to 1 Qlik. View Document (Session) • Not tied to a User or Machine (First come, first serve) • User can access Qlik. View Documents as long as a Session CAL is available • Every Document that is opened takes 1 Session CAL (i. e. , If I have 2 Qlik. View Documents open at the same time, I will use 2 Session CAL’s) Usage CAL • Allows 1 User to have access to 1 Qlik. View Document (Session) for 1 hour over a 28 day period • Not tied to a User or Machine • User can access Qlik. View Documents as long as a Usage CAL is available How Do These Work Together? ?
How Do These Work Together? Often times it makes sense to combine the different CAL’s in a single installation based on user requirements. When CAL’s are combined, this is the order in which they are evaluated: 1. If there is a dedicated Named User CAL for the connecting Client – it will be used 2. If there is a Doc Cal for this user – it will be used 3. If there is an available Session CAL – it will be used 4. If there is an available Usage CAL – it will be used 5. If none of the above are available – access is denied
When would I use them? Named User CAL: • Commonly deployed for users within an organization that need dedicated access to Qlik. View • Include Qlik. View Developers, Power Users, and sometimes Executive level Managers Document CAL: • Commonly deployed for organizations that have Qlik. View deployed departmentally and users within each department only need access to specific Qlik. View documents • Very flexible – DOC CAL’s allow for many combinations • Very Cost-effective way to expand Qlik. View usage departmentally • Include users within departments that ONLY need access to applications specific to their departmental responsibilities
When would I use them? Session CAL: • Commonly deployed for organizations that have a larger user base and are looking for a cost-effective way to deploy Qlik. View • Similar to concurrent licensing but is a 1: 1 ratio between CAL and documents. (1 user opens 1 document = 1 Session CAL, 1 User opens 2 documents = 2 Session CALs) • Deployed for frequent Qlik. View users that don’t need dedicated access • Include Business Analysts and Mid-Management
When would I use them? Usage CAL: • Commonly deployed within organizations to handle “overflow” users during peak usage times • Very cost-effective for large organizations that have many “casual” users • Allows access to 1 Qlik. View Document for 1 hour within a 28 day period • Good for handling users that only need infrequent access to QLik. View (i. e. viewing month-end reports)
Scenarios The following scenarios are simply example licensing configurations to give you an understanding of when to use the different options. There is really no “right” answer and each organization will have its’ own configuration based on their specific needs. We will work with you to determine the best mix of licensing options to ensure you have the most optimum and cost-effective license configuration.
Scenarios Scenario #1 50 users total. All need frequent access to Qlik. View documents (1 -2 per day). 1 User that will develop/maintain Qlik. View applications. 49 Dedicated Qlik. View Users 50 Named User CALs Qlik. View Server 1 Qlik. View Developer
Scenarios Scenario #2 100 users total. 25 of which need frequent access to Qlik. View documents (1 -2 per day). 2 Users will develop/maintain Qlik. View applications. The rest will use Qlik. View on average 1 -2 times per week 2 Qlik. View Developers 23 Dedicated Qlik. View Users 25 Named User CALs 9 Session CALs (Shared 8: 1) 75 Frequent Qlik. View Users Qlik. View Server
Scenarios Scenario #3 200 users total. 25 of which need frequent access to multiple Qlik. View documents (12 per day). 2 Users will develop/maintain Qlik. View applications. 75 Users will access multiple Qlik. View documents on average 1 -2 times per week. 55 Users are in the Sales Department and need access to only the Qlik. View Sales application. 45 Users are in the Finance Department and need access to only the Qlik. View Finance application. 2 Qlik. View Developers 23 Dedicated Qlik. View Users 25 Named User CALs 9 Session CALs (Shared 8: 1) Qlik. View Server 100 DOC CALs 75 Frequent Qlik. View Users 55 Sales Department Users 45 Finance Department Users
Scenarios Scenario #4 100 users total. 25 of which need frequent access to Qlik. View documents (1 -2 per day). 3 Executives that will have a Qlik. View dashboard on their Desktop. 2 Users will develop/maintain Qlik. View applications. The rest will use Qlik. View on average 1 -2 times per week. During End-of-Month close, usage of Qlik. View increases with users viewing Qlik. View reports. 2 Qlik. View Developers 3 Executives 23 Dedicated Qlik. View Users 30 Named User CALs 7 Session CALs (Shared 10: 1) 75 Frequent Qlik. View Users 5 Usage CALs (Overflow) Overflow Users Qlik. View Server
Scenarios Scenario #5 500 users total. 50 Applications across 2 clustered Qlik. View Servers. Users need to have access to all Qlik. View applications. 100 users are frequent Qlik. View users (1 -2 documents per day). 3 Users will develop/maintain Qlik. View applications. The rest will use Qlik. View on average 1 -2 times per week. Plans are to expand to 1000 users within the next year. 3 Qlik. View Developers 97 Dedicated Qlik. View Users 100 Named User CALs (Clustered) 30 Session CALs (Shared 13: 1) (Clustered) 400 Frequent Qlik. View Users 50 Usage CALs (Overflow/Expansion) Overflow/Expansion Users 2 Qlik. View Servers (Clustered)
Questions? The Power of Simplicity Next Generation Business Intelligence
- Qlikview license types
- Qlikview sap connector
- Collection of well defined objects
- Agenda sistemica y agenda institucional
- Qlik salesforce connector
- Qlik gold client
- Mongodb qlik
- Link table qlikview
- Qlik oem
- Qlik support portal
- Qlik gold client
- Qlik sense tips
- Qlik nprinting api
- Qlik capitalize
- Qlik
- Qlikview sap connector
- Qlik best practices