Agenda License Types Defined How Do They Work Together? When Would I Use Them?Scenarios

License Types - DefinedClient Access License (CAL):

Purchased with QlikView Server and tied to the serial number CALs are Server Based Not Client Based CALs are specific to one (1) QlikView Server Cluster Licensing is available for sharing licenses across ServersQlikView has 4 Types of Client Access Licenses (CALs)

Named User DOC Session Usage

License Types - DefinedNamed User CALBased on User or Machine IdentityCan access unlimited QlikView Documents on 1 QlikView ServerUser will always have access to QlikView Documents

DOC CALAllows one user to open one DocumentLicense is perpetualLicense is associated with a Document and userSold in increments of 100

License Types - DefinedUsage CALAllows 1 User to have access to 1 QlikView Document (Session) for 1 hour over a 28 day periodNot tied to a User or MachineUser can access QlikView Documents as long as a Usage CAL is availableHow Do These Work Together??Session CALAllows 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 availableEvery 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 CALs)

How Do These Work Together?Often times it makes sense to combine the different CALs in a single installation based on user requirements. When CALs are combined,this is the order in which they are evaluated:If there is a dedicated Named User CAL for the connecting Client it will be usedIf there is a Doc Cal for this user it will be usedIf there is an available Session CAL it will be usedIf there is an available Usage CAL it will be usedIf 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 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

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 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 dont 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 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)

ScenariosThe 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.

ScenariosScenario #150 users total. All need frequent access to QlikView documents (1-2 per day). 1 User that will develop/maintain QlikView applications.

ScenariosScenario #150 users total. All need frequent access to QlikView documents (1-2 per day). 1 User that will develop/maintain QlikView applications.

Solution:50 Named User CALs. Since all users are frequent users of QlikView and will be accessing 1-2 apps per day, Named CALs are recommended so that these users are assured of dedicated access to QlikView.

Scenario #1

ScenariosScenario #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

ScenariosScenario #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

Solution:25 Named CALs Dedicated access9 Session CALs Shared access using an 8:1 ratio

The 25 users that need frequent access will use the Named User CALs.The other 75 will share the Session CALs. Using an 8:1 ratio (meaning 1 Session CAL will support 8 Users) 8x9=72.

ScenariosScenario #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.

ScenariosScenario #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.

Solution:25 Named CALs Dedicated access9 Session CALs Shared access using an approximate 8:1 ratio100 DOC CALsThe 25 frequent users will use the Named Cals. The 75 users will share 9 Session CALs (using a 8:1 ratio). The remaining users (55 Sales Department and 45 Finance Department) will consume the 100 DOC Cals.

ScenariosScenario #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.

ScenariosScenario #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.

Solution:30 Named CALs Dedicated access7 Session CALs Shared access using an approximate 10:1 ratio5 Usage CALsThe 25 users, 3 Executives and 2 Developers will use the Named User CALs. The rest will share the Session CALs. Using an approximate 10:1 ratio (meaning 1Session CAL will support 10 Users) 7x10=70.The 5 Usage CALs will be used to handle the increased QlikViewUsage during Month-End processing.

Scenarios

ScenariosScenario #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.

ScenariosScenario #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.

Solution:100 Named CALs in a clustered environment Dedicated access30 Session CALs in a clustered environment- approximate 13:1 ratio50 Usage CALs - in a clustered environmentSince all users need access to the 50 Applications, a clustered license model will be used. The combination of Named, Session and Usage CALs provide for flexibility and growth. Named and Session CALs are recommended as the user community grows.

Scenarios

The Power of Simplicity

Next Generation Business IntelligenceQuestions?

**Today we will be discussing the different license options available with QlikView. We will start by defining what a QlikView license is and the three different license types available. We will then discuss how the different license types work together and provide you with some guidelines as to when you would use the different types. We will then go over several licensing scenarios and apply our knowledge of the different license types to these scenarios in order to come up with a proper licensing configuration.*A QlikView license is referred to as a Client Access License (commonly called a CAL). The licenses (CALs) are server based, meaning they reside on the QlikView Server and not the client, and are tied to the serial number of the server that QlikView resides on. CALs are usually specific to a single QlikView Server but Cluster Licensing is available for large organizations that need to implement a multi-server environment and want to share licenses across multiple QlikView Servers.

QlikView offers three different license types or CALs: Named User, Session, and Usage. Lets take a look at each of these and explain how they work .*The Named User CAL, as the name implies, is a license that is tied directly to a USERID or physical computer. Users are defined on the QlikView Server and authenticated when they log on. A user that is assigned a Named User CAL has access to any QlikView application that they have security authorization for. A Named User CAL gives the QlikView user dedicated access to any QlikView documents.

A Document CAL allows one user to open one document. The license is perpetual and will allow the user to open a single document into perpetuity. The combination of a user would be stored in QlikView Server like Named users but associated with a document instead of the full server.

*The Session CAL is used for sharing QlikView Licenses. It is similar to concurrent licensing but there are some subtle differences. A Session CAL is not tied to an individual user or machine but allows for anonymous users. A session refers to the time that a user is viewing a single QlikView document. Therefore if a user has 2 QlikView documents open at the same time, they will be using 2 Session CALs. Since the Session CALs are shared, if a user logs into QlikView and there are no Session CALs available, their access will be denied.

The Usage CAL is designed to accomodate overflow usage during peak times. It is not tied to a User or Machine. A Usage CAL allows 1 user to have access to 1 QlikView Document (session) for 1 hour over a 28 day period. Once this limit has been met, the Usage CAL becomes inactive and is not reset until the 28 day period has passed.

Lets take a look at how these license types work together.*Since most organizations have many different users with different needs for a Business Intelligence tool, it is common that they will need a combination of QlikView licenses. Below is the order in which the licenses are evaluated when a user logs on to the QlikView Server.

Once they have logged on and been authenticated, QlikView first checks to see if there is a Named User CAL for this user. If there is, the Named User CAL will be used. If there is no Named User CAL for this connecting user, QlikView will check to see if there is an available DOC CAL. If one is available, it will be used. If there is no DOC CAL for this connecting user, QlikView will check to see if there is an available Session CAL. If one is available, it will be used. If the connecting user does not have a Named CAL and a Session CAL is not available, QlikView will check to see if there is a Usage CAL available and use it. If there are no licenses available, the connecting user will be presented with a message saying there are no available licenses and access will be denied.

Next we will discuss when to use the different license types based on the users needs.*The Named User CAL is typically used for users that need dedicated access to QlikView documents. These are normally used for QlikView Developers, Power Users, and sometimes Executive Level managers. A QlikView Developer is in charge of creating and maintaining the QlikView Applications. They will usually be using QlikView every day so will need to be sure that there is always a license available to them. The same goes for Power Users. This type of user will access QlikView on a daily basis and use the QlikView application to analyze the business. This user may also be creating ad-hoc analysis or be tasked with creating documents for other users. They will also need dedicated access to QlikView. In terms of Executive Level management, often times executives will utilize QlikView to have a dashboard that allows them to keep track of their Key Performance Indicators (KPIs). They may not reference the dashboard every single day, but you want to make sure when they do need to look at it that they have a dedicated license.

Document CALs are used when department-specific applications are deployed and the users within these department ONLY need access to these applications. For example, I may have 100 users in the Finance Department that need to access only the QlikView Financial application. Since this is the only application that they need to access, a DOC CAL is a cost-effective way to deploy to these users. DOC CALs are very flexible in that they allow for multiple combinations of usage:

1 User can open 100 different documents or100 Users can open 1 Document or50 Users can use a Sales Application50 Users can use a Finance Application etc....

The combination of Users and Documents must equal the number of DOC CALs, i.e., 100 Doc CALs equates to any number of Users and Documents that equal 100.

*Session CALs are a cost-effective way to deploy QlikView to a larger user base. Session CALs provide for anonymous users (meaning a Session CAL is not tied to an individual user). Session CALs are shared licenses that are normally used to accomodate less frequent QlikView users (users that will access QlikView 1-2 times per week). A Session CAL is tied to a QlikView document meaning that 1 opened QlikView document will use 1 Session CAL license. If the same user has 2 QlikView documents open at the same time, 2 Session CALs will be used. Determining how many users can be supported by 1 Session CAL will vary depending on your user community, but a general rule of thumb is to start with an 8:1 ratio (meaning 1 Session CAL will be sufficeient to support 8 QlikView users). This ratio may be lower or higher depending on the needs within an organization.

Business Analysts and mid management are usually good candidates for Session CALs. These individuals usually do not have the need to access QlikView on a daily basis so can share a pool of Session CAL licenses.

*While it is recommended to try and identify the different user types and match them to the appropriate license type, there are times when additional users will be accessing QlikView. This usually happens during peak times such as Month-End closing, Year-End Processing or Promotional Campaigns- all activities that will boost the usage of QlikView. For these times, Usage CALs can be utilized to accomodate these overflow users.

Usage CALs have a time limit and should not be used to accomodate individual or groups of users. A Usage CAL will allow a user to access 1 QlikView document for up to 1 hour within a 28 day period. While Usage CALs are a very cost-effective way to handle overflow usage, it is important to understand their limitations and plan your licensing strategy accordingly.*Disclaimer slide Your actual mileage may vary*This is a straightforward scenario. We have 50 users that will be accessing QlikView on a daily basis (including 1 individual that will be in charge of creating the QlikView applications). Since each person is considered a dedicated user of QlikView, it makes sense to use the Named User CALs so each user is guranteed access to QlikView.*This is a straightforward scenario. We have 50 users that will be accessing QlikView on a daily basis (including 1 individual that will be in charge of creating the QlikView applications). Since each person is considered a dedicated user of QlikView, it makes sense to use the Named User CALs so each user is guranteed access to QlikView.*This is a straightforward scenario. We have 50 users that will be accessing QlikView on a daily basis (including 1 individual that will be in charge of creating the QlikView applications). Since each person is considered a dedicated user of QlikView, it makes sense to use the Named User CALs so each user is guranteed access to QlikView.*In this scenario, we have added a mix of frequent and infrequent QlikView Users. Of the 100 total users, we know that 25 of them will be using QlikView every day. We want to make sure that these users will always have access to their QlikView documents so we will use Named CALs for them. The other 75 users are more infrequent users of QlikView and will only access QlikView 1-2 times per week on average. For these users, it makes sense for them to share a pool of Session CALs. It has been determined that no more than 8 of these users will be accessing QlikView at the same time. Using an 8:1 ratio, we determine that 9 Session CALs should be sufficient for the remaining 75 users.*In this scenario, we have added a mix of frequent and infrequent QlikView Users. Of the 100 total users, we know that 25 of them will be using QlikView every day. We want to make sure that these users will always have access to their QlikView documents so we will use Named CALs for them. The other 75 users are more infrequent users of QlikView and will only access QlikView 1-2 times per week on average. For these users, it makes sense for them to share a pool of Session CALs. It has been determined that no more than 8 of these users will be accessing QlikView at the same time. Using an 8:1 ratio, we determine that 9 Session CALs should be sufficient for the remaining 75 users.*In this scenario, we have added a mix of frequent and infrequent QlikView Users. Of the 200 total users, we know that 25 of them will be using QlikView every day. We want to make sure that these users will always have access to their QlikView documents so we will use Named CALs for them. 75 users are more infrequent users of QlikView and will only access QlikView 1-2 times per week on average but need access to multiple applications. For these users, it makes sense for them to share a pool of Session CALs. It has been determined that no more than 8 of these users will be accessing QlikView at the same time. Using a 8:1 ratio, we determine that 9 Session CALs should be sufficient. The remaining 100 users are made up of 55 people in the Sales Department that ONLY need access to the Sales application and 45 people in the Finance Department that ONLY need access to the Finance application. For these users, DOC CALs are the most cost-effective way of deploying QlikView.*In this scenario, we have added a mix of frequent and infrequent QlikView Users. Of the 100 total users, we know that 25 of them will be using QlikView every day. We want to make sure that these users will always have access to their QlikView documents so we will use Named CALs for them. The other 75 users are more infrequent users of QlikView and will only access QlikView 1-2 times per week on average. For these users, it makes sense for them to share a pool of Session CALs. It has been determined that no more than 8 of these users will be accessing QlikView at the same time. Using an 8:1 ratio, we determine that 9 Session CALs should be sufficient for the remaining 75 users.*This scenario introduces Usage CALs into a configuration. We know that 30 users will need their own Named CALs. We have also determined that the other 70 users will be infrequent (accessing QlikView 1-2 times per week). In addition, we are estimating that there will only be 10 of these users on at the same time. We can accomodate these users with Session CALs using approximately a 10:1 ratio. We also know that during end-of-month processing that the QlikView usage goes up. Once end-of-month processing is finished, the usage goes back to previous levels. The most cost-effective way to handle these usage peaks and ensure that everyone has access to QLikView is to implement 5 Usage CALs.*This scenario introduces Usage CALs into a configuration. We know that 30 users will need their own Named CALs. We have also determined that the other 70 users will be infrequent (accessing QlikView 1-2 times per week). In addition, we are estimating that there will only be 10 of these users on at the same time. We can accomodate these users with Session CALs using approximately a 10:1 ratio. We also know that during end-of-month processing that the QlikView usage goes up. Once end-of-month processing is finished, the usage goes back to previous levels. The most cost-effective way to handle these usage peaks and ensure that everyone has access to QLikView is to implement 5 Usage CALs.*This scenario introduces Usage CALs into a configuration. We know that 30 users will need their own Named CALs. We have also determined that the other 70 users will be infrequent (accessing QlikView 1-2 times per week). In addition, we are estimating that there will only be 10 of these users on at the same time. We can accomodate these users with Session CALs using approximately a 10:1 ratio. We also know that during end-of-month processing that the QlikView usage goes up. Once end-of-month processing is finished, the usage goes back to previous levels. The most cost-effective way to handle these usage peaks and ensure that everyone has access to QLikView is to implement 5 Usage CALs.*This scenario represents more of an Enterprise implementation of QlikView. We have a large number of users with many QlikView applications spread across 2 clustered servers. In a clustered licensing environment, licenses can be shared across multiple servers. This prevents having to have duplicate applications on each server as well as not having to purchase duplicate licenses. The licensing is no different than the previous scenarios: frequent QlikView users will have Named User CALs and the rest will share 20 Session CALs. This customer doesnt have a good handle yet on how many users might be accessing QlikView at the same time via a Session CAL, so we will use a 13:1 ratio and provide an additional 50 Usage CALs for overflow.

As new users come on board, they can utilize the Session CALs. Recommended license types for growth are Named User CALs and Session CALs. They can use the Ops Monitor in QlikView to get an idea of QlikView usage and make the determination as to how many additional licenses, and what types, need to be purchased.*This scenario represents more of an Enterprise implementation of QlikView. We have a large number of users with many QlikView applications spread across 2 clustered servers. In a clustered licensing environment, licenses can be shared across multiple servers. This prevents having to have duplicate applications on each server as well as not having to purchase duplicate licenses. The licensing is no different than the previous scenarios: frequent QlikView users will have Named User CALs and the rest will share 20 Session CALs. This customer doesnt have a good handle yet on how many users might be accessing QlikView at the same time via a Session CAL, so we will use a 13:1 ratio and provide an additional 50 Usage CALs for overflow.

As new users come on board, they can utilize the Session CALs. Recommended license types for growth are Named User CALs and Session CALs. They can use the Ops Monitor in QlikView to get an idea of QlikView usage and make the determination as to how many additional licenses, and what types, need to be purchased.*This scenario represents more of an Enterprise implementation of QlikView. We have a large number of users with many QlikView applications spread across 2 clustered servers. In a clustered licensing environment, licenses can be shared across multiple servers. This prevents having to have duplicate applications on each server as well as not having to purchase duplicate licenses. The licensing is no different than the previous scenarios: frequent QlikView users will have Named User CALs and the rest will share 20 Session CALs. This customer doesnt have a good handle yet on how many users might be accessing QlikView at the same time via a Session CAL, so we will use a 13:1 ratio and provide an additional 50 Usage CALs for overflow.

As new users come on board, they can utilize the Session CALs. Recommended license types for growth are Named User CALs and Session CALs. They can use the Ops Monitor in QlikView to get an idea of QlikView usage and make the determination as to how many additional licenses, and what types, need to be purchased.*In summary, QlikView s licensing strategy makes it very flexible to accommodate all types of users within an organization. We make it very easy to add additional licenses as you need them by not requiring you to buy licenses in blocks. There are no minimum or maximum number of licenses you can purchase.

QlikView understands that every organization will have many different users with different needs when it comes to using a Businesss Intelligence tool. Like our motto The Power of Simplicity QlikView offers a very straightforward licensing model that provides the flexibility to address the needs of your user community for both the present and the future.