QlikView Licensing Overview

QlikView 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 QlikView Server and tied to the serial number• CAL’s are Server Based – Not Client Based• CAL’s are specific to one (1) QlikView Server• Cluster Licensing is available for sharing licenses across Servers

QlikView has 4 Types of Client Access Licenses (CALs)

• Named User• DOC• Session• Usage


Named User CAL•Based on User or Machine Identity•Can access unlimited QlikView Documents on 1 QlikView Server•User will always have access to QlikView 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


Usage CAL•Allows 1 User to have access to 1 QlikView Document (Session) for 1 hour over a 28 day period•Not tied to a User or Machine•User can access QlikView Documents as long as a Usage CAL is available

How Do These Work Together??

Session CAL•Allows 1 User to have access to 1 QlikView Document (Session)•Not tied to a User or Machine (First come, first serve)•User can access QlikView Documents as long as a Session CAL is available•Every Document that is opened takes 1 Session CAL (i.e., If I have 2 QlikView Documents open at the same time, I will use 2 Session CAL’s)

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 QlikView • Include QlikView Developers, Power Users, and sometimes Executive level Managers

Document CAL: •Commonly deployed for organizations that have QlikView deployed

departmentally and users within each department only need access to specific QlikView documents •Very flexible – DOC CAL’s 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


Session CAL: • 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. (1 user opens 1 document = 1 Session CAL, 1 User opens 2 documents = 2 Session CALs)

• Deployed for frequent QlikView users that don’t need dedicated access • Include Business Analysts and Mid-Management


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 QlikView Document for 1 hour within a 28 day period

•Good for handling users that only need infrequent access to QLikView (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 #150 users total. All need frequent access to QlikView documents (1-2 per day). 1 User that will develop/maintain QlikView applications.

1 QlikView Developer

49 Dedicated QlikView Users

QlikView Server

50 Named User CALs

Scenarios

Scenario #2100 users total. 25 of which need frequent access to QlikView documents (1-2 per day). 2 Users will develop/maintain QlikView applications. The rest will use QlikView on average 1-2 times per week

QlikView Server


2 QlikView Developers

75 Frequent QlikView Users

25 Named User CALs

9 Session CALs(Shared 8:1)

Scenarios

Scenario #3200 users total. 25 of which need frequent access to multiple QlikView documents (1-2 per day). 2 Users will develop/maintain QlikView applications. 75 Users will access multiple QlikView documents on average 1-2 times per week. 55 Users are in the Sales Department and need access to only the QlikView Sales application. 45 Users are in the Finance Department and need access to only the QlikView Finance application.

45 Finance Department Users55 Sales Department Users

100 DOC CALs

QlikView Server




25 Named User CALs


Scenarios

Scenario #4100 users total. 25 of which need frequent access to QlikView documents (1-2 per day). 3 Executives that will have a QlikView dashboard on their Desktop. 2 Users will develop/maintain QlikView applications. The rest will use QlikView on average 1-2 times per week. During End-of-Month close, usage of QlikView increases with users viewing QlikView reports.

QlikView Server




30 Named User CALs


5 Usage CALs(Overflow)

3 Executives

Overflow Users

Scenarios

Scenario #5500 users total. 50 Applications across 2 clustered QlikView Servers. Users need to have access to all QlikView applications. 100 users are frequent QlikView users (1-2 documents per day). 3 Users will develop/maintain QlikView applications. The rest will use QlikView on average 1-2 times per week. Plans are to expand to 1000 users within the next year.

2 QlikView Servers(Clustered)



100 Named User CALs

(Clustered)

30 Session CALs(Shared 13:1)(Clustered)

50 Usage CALs(Overflow/Expansion)

Overflow/Expansion Users


The Power of Simplicity

Next Generation Business Intelligence

Questions?

Date post:	07-Nov-2014
Category:	Documents
Upload:	divya-rao
View:	218 times
Download:	4 times