QLIKVIEW LICENSEQlikView Technical Reference DocumentMarch

QlikView LicenseThis document explains the license details for each component of a QlikView deploymentand it discusses how the different license types work together by providing some guidelines.This document is not intended to provide guidance on how to license a QlikView deploymentand it does not have any information on pricing. It is advisable to work with the accountexecutive or with the QlikTech sales representative to determine the best licensing optionsfor your deployment.The following part of the paper explains the two basic license types: client and server, givingan overview of how they work together and finally covering some scenarios that illustrate theuse of different licensing approaches.What is QlikView Client Access License?A QlikView license is referred to as a Client Access License (CAL). The licenses (CALs) areserver based, meaning they reside on and are administered by the QlikView Server and notthe QlikView Desktop client. Server based CALs are tied to the serial number of the serverwhere QlikView resides. CALs are specific to a single QlikView Server or, if a cluster licenseis used, a specific QlikView Server cluster. CALs cannot be transferred between differentQlikView Servers or Server Clusters. Please also note that the CALs require the QlikViewServers within a cluster to be within the same geographical and physical location and withinthe same network sub-net/segment.QlikView offers four different license types or CALs: Named User, Document, Session,and Usage. The following section explains each of these and covers how they work.NAMED USER CALA Named User CAL is assigned to a unique and identified user. A user who is assigned to aNamed User CAL has access to any QlikView application as authorized by the organization’ssecurity policies in QlikView. A Named User CAL may be unassigned and reassigned toanother user pursuant to the software licensing agreement, in which case there is a 24-hourquarantine period before the Named User CAL can be reused and transferred to anotheruser. To use a Named User CAL, the client user must be identified via an authenticated username or by machine id (QlikView does not authenticate users and it works in conjunctionwith either the O/S via Windows Active Directory or a 3rd Party authenticating agent viaa ticket exchange between the web server and QlikView Server such as Kerberos, SiteMinder, or others). Please note that an IP address is not a valid form of identification fora Named User CAL.QlikView License 2

NAMED USER CAL LEASINGNamed User CALs are also used for offline analysis and development. In order to licenselocal desktop clients for this, the users can download a CAL from the server. This processis called ‘leasing a Named User CAL’ from the QlikView Server. With a leased Named UserCAL, the QlikView Desktop Client is able to view local as well as Server hosted documents.Please refer to the QlikView License Lease Tech Brief document for further information onhow to lease a license from a QlikView Server.DOCUMENT CALA Document CAL allows one user to open one QlikView application. The license isperpetual and will allow the user to open a single QlikView application into perpetuity.One user can consume more than one Document CAL if they need to access additionalQlikView applications. The combination of a user would be stored in QlikView Server likeNamed users but associated with a QlikView application instead of all of the applicationsavailable on the server or in the cluster. A Document CAL may be transferred to anotheruser pursuant to the software licensing agreement, in which case there is a 24-hourquarantine before the Document CAL can be transferred to another user. To use aDocument CAL, the client user must be identified via an authenticated user name (WindowsActive Directory or through a ticket exchange between the web server and QlikView Server).The purpose of the Document CAL is to provide a mechanism by which licensees canlicense the use of a single QlikView application. To prevent the combination of many datamodels in a single application, there are restrictions in the QlikView applications that canbe used with the Document CAL. The Document CAL can only be used with applicationsthat have a single contiguous data model and do not contain any chasm traps betweentables. QlikView applications with multiple logical islands are normally not allowed.Multiple logical islands are only allowed, if the additional tables are unconnected andcontain only few records or a single column. In addition, the QlikView application maynot contain any loosely coupled tables where there are circular references between thetables in the data structure.SESSION CALThe Session CAL is used for sharing QlikView Licenses. It is similar to concurrent licensingbut there are some subtle differences. A Session CAL is not tied to an individual user ormachine but allows for both authenticated and “anonymous” users. Since the Session CALsare shared, if a user logs into QlikView and there are no Session CALs available, theiraccess will be denied. The minimum session time for a Session CAL is 15 minutes, whichmeans that sessions that end in less than 15 minutes will still consume the session until the15 minute mark is passed; those which terminate after 15 minutes will consume their actualsession length. By default, there is no maximum session length, but this can be configured.QlikView License 3

USAGE CALThe Usage CAL is designed to accommodate “overflow” usage during peak times. UsageCAL allows any user, identified or anonymous/unidentified, to access only one QlikViewapplication, residing on the server or server cluster to which the Usage CAL is assigned.A Usage CAL allows one user to have access to one QlikView application for up to 60minutes. If a user exceeds the 60 minute time limitation, the user will have consumed twoUsage CALs without any warning being given to the user. Usage CALs are continuouslyrecharged every 28 days (at a pace corresponding to 1/28 of the total number of UsageCALs assigned to the QlikView Server per day).How to Assign Licenses?QlikView Management Console (QMC) is the management component of the QlikViewenvironment giving the administrators full access to all possible settings for QlikView Serverand the Publisher module including licensing. The licenses tab on QMC is used to manageQlikView Server License, Publisher license and all of the client access licenses (CALs).The assignment of the Named CALs to users can be managed on the “Assigned CALs” subtab of the Licenses tab. On this tab, it is possible to manually assign the Named CALs tousers. It is also possible to automatically assign Named CALs by using the “Allow dynamicCAL assignment” check box found under the General tab. When this option is checked, theNamed CALs would be assigned to users based on first come first served basis. The usercan also lease a Named CAL from a QlikView Server. More information on leasing a licensefrom a QlikView Server can be found in the QlikView License Lease Tech Brief document.To manage the assignment of Document CALs, the Document CALs sub tab under UserDocuments tab on QMC can be used. This is the manual way of assigning a Document CALto a user for a specific QlikView application. Please note that assigning of a CAL does notimply access to the QlikView application. To automate this process, “Allow dynamic CALassignment” option can be checked. This would allow dynamic allocation of Document CALsto that specific QlikView applications. It is also possible to develop a custom code to automatethe Document CALs assignment by using the QlikView Server APIs.Session CALs and Usage CALs are automatically assigned to the users in a first comefirst served basis.QlikView License 4

When different CAL types are combined on the same server and the “allow dynamic CALassignment” options are checked, the order of priority in the CAL assignment is done as follows:1. If there is a dedicated Named User CAL for the connecting client, it is used.2. If there is a dedicated Document CAL for the connecting client, it is used.3. If a new Named User CAL can be assigned to the connecting client, it is used.4. If a new Document CAL can be assigned to the connecting client, it is used.5. If there is an available Session CAL, it is used.6. If there is an available Usage CAL, it is used.How to Manage Licenses?The licenses tab of QlikView Management Console (QMC) is used to manage QlikViewServer License, Publisher license and all of the client access licenses (CALs).The General sub tab has information about the number of assigned licenses from theavailable licenses for each type of CALs. The identification option can be used to identifythe users either by user name or by machine name. This option is only relevant for theallocation of Named CALs. Please not that when identification by user option is checked,it is possible for a user to lease the same license twice. This flexibility allows a user to usethe same license from two different machines.Figure 1. Client Access Licenses tab on the QlikView Management ConsoleQlikView License 5

The Assigned CALs sub tab is used to manage the assignment of Named CALs. Theinformation that is displayed on this sub tab includes the name of the user, last time thelicense is used and if the license for the user is under quarantined until a specific time. Thequarantined until option is used when a license is marked to be deleted. This option allowsto hold the CAL-to-user association for 24 hrs period. During this time period the CAL-touser association can be undeleted by clicking the restore icon.The History sub tab provides information on the lease licensed activities. By using the Limitationstab, it is possible to limit the number of CALs that can be used in the QlikView environment.How Do These License Types Work Together?Since most organizations have many different users with different Business Discoveryneeds, it is common that they will need a combination of QlikView licenses. A given instanceof QlikView Server can carry any combination of the CAL types. The order of priority in theCAL assignment is explained in the “How to Assign Licenses” section of this paper whendifferent CAL types are combined on the same server.Usage ScenariosIn this section of the paper, we will discuss when to use different license types based onthe users needs.NAMED USER CALThe Named User CAL is typically used for users that need dedicated access to QlikViewapplications. These are normally used for QlikView Developers, Power Users, and sometimesexecutive level managers, as well as a QlikView Developer who is in charge of creating andmaintaining the QlikView Applications. These users will usually be using QlikView every dayso there should be always a license available to them. The executive level managers may notreference the QlikView applications every single day, but it is a good practice to make surewhen they do need to look at it that they have a dedicated license.DOCUMENT CALDocument CALs are used when department-specific applications are deployed and the userswithin these department only need access to these applications. For example, there maybe 100users 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 Document CAL is a cost-effectiveway to deploy to these users. Document CALs are very flexible in that they allow for multiplecombinations of usage; 1 User can open 100 different documents or 100 users can open 1document, or 50 users can use a sales application and 50 Users can use a Finance Applicationetc. The combination of Users and Documents must equal the number of Document CALs, i.e.,100 Doc CALs equates to any number of Users and Documents that equal 100.QlikView License 6

SESSION CALSession CALs are a cost-effective way to deploy QlikView to a larger user base. SessionCALs provide for anonymous users (meaning a Session CAL is not tied to an individualuser). Session CALs are shared licenses that are normally used to accomodate lessfrequent QlikView users (users that will access QlikView couple times per week).Determining how many users can be supported by 1 Session CAL will vary dependingon your user community and the frequency and the duration of their usage.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 canshare a pool of Session CAL licenses.USAGE CALWhile it is recommended to try and identify the different user types and match them to theappropriate 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 orpromotional 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 groupsof users. A Usage CAL will allow a user to access one QlikView application for up to onehour within a 28 day period. While Usage CALs are a very cost-effective way to handleoverflow usage, it is important to understand their limitations and plan your licensingstrategy accordingly.QlikView License 7

Licensing Configurations ExamplesThe following part of the paper examines the different licensing scenarios. They are simpleexamples of licensing configurations to give an understanding of when to use the differentoptions. There is really no “right” answer and each organization has its’ own configurationbased on their specific needs. Please work with your account executive to determine thebest mix of licensing options to ensure you have the most optimum and cost-effectivelicense configuration.SCENARIO #1In scenario #1, there are 50 users that will be accessing the QlikView applications on adaily basis. One of these 50 users will be in charge of creating the QlikView applications.Figure 2. Scenario One Licensing Configuration 2012 QlikTechSince each person is considered a dedicated user of QlikView, Named CALs are recommendedso that these users are assured of dedicated access to the QlikView applications.QlikView License 8

SCENARIO #2In scenario #2, there are 100 users. 25 of these 100 users need frequent access to QlikViewapplications (once or twice per day). 2 Users will develop and maintain QlikView applications.The rest of the users will use QlikView applications on average 1-2 times per week.Figure 3. Scenario Two Licensing Configuration 2012 QlikTechIn this scenario, there is a mix of frequent and infrequent QlikView users. Of the 100 totalusers, 25 of them will be using QlikView applications every day. To make sure that theseusers will always have access to their QlikView applications, the recommendation is to useNamed CALs for them. The other 75 users are more infrequent users of QlikView and willonly access QlikView applications 1-2 times per week on average. These users can sharea pool of Session CALs. It is very important to understand the number of concurrent userswhen deciding on the number of session CALs. In this scenario, It has been determined thatno more than 8 of these users will be accessing the QlikView applications at the same time.Using an 8:1 ratio, it has been determined that 9 Session CALs should be sufficient for theremaining 75 users.QlikView License 9

SCENARIO #3In this scenario, there are 200 users. 25 users need frequent access to multiple QlikViewapplications (once or twice per day). 2 users will develop and maintain QlikView applications.75 users will access multiple QlikView applications on average 1-2 times per week. 55 usersare in the Sales Department and need access to only the QlikView Sales application. 45 usersare in the Finance Department and need access to only the QlikView Finance application.Figure 4. Scenario Three Licensing Configuration 2012 QlikTechQlikView License 10

Of the 200 total users, 25 of them will be using QlikView applications every day. It isrecommended to make sure that these users will always have access to their QlikViewapplications so we will use Named CALs for them. 75 users are more infrequent users ofQlikView applications and will only access 1-2 times per week on average but need accessto multiple applications. For these users, it makes sense to share a pool of Session CALs.It has been determined that no more than 8 of these users will be accessing QlikViewapplications at the same time. Using a 8:1 ratio, it is determined that 9 Session CALs shouldbe sufficient. The remaining 100 users are made up of 55 users in the Sales Departmentthat only need access to the QlikView Sales application and 45 users in the FinanceDepartment that only need access to the QlikView Finance application. For these users,DOC CALs are the most cost-effective way of deploying QlikView.QlikView License 11

SCENARIO #4This scenario introduces Usage CALs into the configuration. There are 100 users in total. 25of these users will need frequent access to QlikView applications (once or twice per day). 3Executives will have a QlikView dashboard application on their Desktop. 2 users will developand maintain QlikView applications. The rest will use QlikView applications on average 1-2times per week. During end of month close, usage of QlikView applications increases.Figure 5. Scenario Four Licensing Configuration 2012 QlikTechIn this scenario, 30 users will need their own Named CALs (there are 25 users who need frequentaccess to QlikView applications, there are 3 Executives who will have a QlikView dashboardapplication on their desktop and 2 users who will develop and maintain QlikView applications).The other 70 users will be infrequent users (accessing QlikView applications 1-2 times per week).The estimation is that there will only be 10 of these users acessing QlikView applicationsat the same time. These users can be accomodated with Session CALs using approximately a10:1 ratio. Another factor to consider with this sceanrio is the end of month processing, whichcauses an increase on the QlikView application usage. Once end of month processing is finished,the usage goes back to previous levels. The most cost effective way to handle these usage peaksand ensure that everyone has access to the QlikView applications is to implement 5 Usage CALs.QlikView License 12

SCENARIO #5This scenario represents more of an enterprise implementation of QlikView. There is a largenumber of users with many QlikView applications spread across 2 clustered servers. In aclustered licensing environment, licenses can be shared across multiple servers (Please note thatthe CALs require the QlikView Servers within a cluster to be within the same geographical andphysical location and within the same network sub-net/segment.). This prevents having to haveduplicate applications on each server as well as not having to purchase duplicate licenses. Thelicensing is no different than the previous scenarios: frequent QlikView users will have NamedUser CALs and the rest will share 20 Session CALs. This customer doesn’t have a good handleyet on how many users might be accessing QlikView applications at the same time via a SessionCAL, so a 13:1 ratio is used and an additional 50 Usage CALs is used for overflow.Figure 6. Scenario Five Licensing Configuration 2012 QlikTechAs new users come on board, they can utilize the Session CALs. Recommended license typesfor growth are Named User CALs and Session CALs. The Ops Monitor application, whichis a free QlikView application can be used to get an idea of QlikView usage and make thedetermination as to how many additional licenses, and what types, need to be purchased.QlikView License 13

LICENSING CONFIGURATIONS SUMMARYQlikView‘s licensing strategy makes it very flexible to accommodate all types of users withinan organization. QlikTech understands that every organization will have many different userswith different needs when it comes to Business Discovery. QlikView makes it very easy toadd additional licenses as the need for Business Discovery increases by not requiring buylicenses in blocks in advance.QlikView Server LicensingThis section of the paper explains the licensing for different type of QlikView Server.QLIKVIEW ENTERPRISE EDITION (EE) SERVERQlikView Enterprise Edition Server is designed to be used in large and complex deploymentsand provides features such as unlimited documents, server-based collaboration, integrationwith third-party security systems, server clustering, and cluster licensing. The minimumconfiguration of a QlikView EE Server is ten Named User Client Access Licenses (CALs).QLIKVIEW SMALL BUSINESS EDITION (SBE) SERVERQlikView SBE Server is designed to be used in smaller deployments. The minimum configurationof a QlikView SBE Server is five Named User CALs. The maximum configuration is 25 namedCALs, 100 Document CALs.QLIKVIEW INFORMATION ACCESS SERVER (IAS)QlikView IAS is a QlikView Server that is licensed for an uncapped number of users, butlimited to a single QlikView application. QlikView IAS runs in anonymous mode and must bepublically accessible without authentication (on the public Internet), that is, it must not beplaced behind a firewall. No QlikView client can access QlikView IAS — the user interfacemust be built by the end user either manually or by using QlikView WorkBench.QLIKVIEW EXTRANET SERVER (QES)QES allows end users to deploy QlikView solutions to their extranet. QES is based on QlikViewEE Server, but only supports up to three QlikView applications. The server can be deployedwith a combination of Session and Usage CALs. QES supports mobile clients and can bedeployed in clustered environments. The AJAX client or a customized AJAX client can beused via QlikView WorkBench, which is included in QES.In addition to the editions of QlikView Server described above, there is also a numberof additional, server-related products that can be purchased with QlikView Server.QlikView License 14

QLIKVIEW TEST SERVERQlikView Test Server is a license that provides an environment separate from productionto use for data validation, application testing, and preparation/migration of QlikViewapplications to new versions and/or releases of QlikView. QlikView Test Server comes intwo editions, QlikView EE Test Server and QlikView SBE Test Server, both of which havethe same features and limitations as the corresponding production servers. Please note thatthe watermark “Test” is superimposed on all charts and added to all object captions on theQlikView applications that are opened on a QlikView Test Server. There is no license leasefrom QlikView Test Server.QLIKVIEW PUBLISHERQlikView Publisher is a license that adds significant functionality to the standard reloadcapability of QlikView Server. QlikView Publisher includes functionality to handle fieldlevel security and access control from central administration software like Window ActiveDirectory or Novell LDAP. QlikView Publisher is also needed to support complex distributionmodels for QlikView applications. In addition, each license of QlikView Publisher allowsan additional node/server for reload, distribution, or security management in a multi-node/server deployment. With the additional component QlikView Publisher Report Distribution, anyQlikView application report can be distributed as a .pdf file to a folder or via email or SMTP.As the number of QlikView applications increase, it is possible to expand the QlikViewPublisher deployment by either buying additional (separate) Publisher license(s), or bybuying additional distribution service(s) for the existing QlikView Publisher. For most ofthe cases, it makes more sense to purchase additional distribution services and haveone distributed QlikView Publisher. Each of these additional distribution services can bedeployed to separate servers providing scalability on the QlikView application refreshesand distributions. All of the Publisher distribution services are managed from the sameQlikView Management Console providing ease of maintenance and management.There are also cases where multiple separate QlikView Publishers would make sense.For example, if the QlikView deployment is geographically distributed and each locationhas their own data sources, it would make sense to deploy separate QlikView Publisherat each of these geographic locations. It is recommended to work with the QlikViewarchitecture experts to decide on the best deployment architecture based on yourenvironment and Business Dicovery needs.QLIKVIEW WORKBENCHQlikView WorkBench (an add-on to QlikView EE Server) is a development tool for creatingweb mash-ups with QlikView. It features drag and drop editing capabilities within theMicrosoft Visual Studio development environment and allows for custom web interfacesand integration with third-party services. Please note that QlikView WorkBench is notavailable for use with QlikView SBE Server.QlikView License 15

QLIKVIEW WEB PARTS FOR MICROSOFT SHAREPOINT QlikView Web Parts (an add-on to QlikView EE Server) for Microsoft SharePoint allowsfor rapid deployment of QlikView objects within Microsoft SharePoint portal environments.Please note that QlikView Web Parts are not available for use with QlikView SBE Server.Features and LimitationsThe table below summarizes the features and limitations of each edition of QlikView Server.”Y” represents a supported feature and ”N” represents a non supported med User CALsYY (max 25)NNSession CALsYNY (unlimited)YUsage CALsYNNYDocument CALsYY(max 100)NNExternal UsersAllowedNNYYAJAX (and mobiledevices via ernet ExplorerPluginYYNNInstalled QlikViewClientYYNNLicensingClientsQlikView License 16

ScalabilityCan be clustered(additional serverlicense required)YNYYUnlimitedDocumentsYYN(1 only)N (3documentsonly)Third Party SecurityIntegrationYNNYDynamic DataUpdate (Real TimeServer) (additionallicense required)YNY(included)YLicense Lease(offline access,Named User ts, sheetobjects, and inputfields)YYNNSessionCollaborationYYNYQlikView Publisherand PDF generation(additional licenserequired)YYNNQlikView Connectorfor use with SAPNetWeaver (additional licenserequired)YYYYIntegrationFeaturesQlikView License 17

Test Server OptionYYYYCan be embedded inMicrosoft SharePoint(QlikView WebParts for MicrosoftSharePoint)(additional licenserequired)YNYYBuild (additional licenserequired)YNY(included)Y(included)Section AccessYYNYDocument MetadataService (DMS)YNNYActive Directory/NTFSYYNYAnonymous UserY (withSessionCALs)NY(mandatory)NSecurityService (DMS) 2012 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile andother QlikTech products and services as well as their respective logos are trademarks or registered trademarks of QlikTech International AB. All other company names, productsand services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice. This publicationis for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The onlywarranties for QlikTech products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein shouldbe construed as constituting any additional warranty.QlikView License 18

QlikView Management Console (QMC) is the management component of the QlikView environment giving the administrators full access to all possible settings for QlikView Server and the Publisher module including licensing. The licenses tab on QMC is used to manage QlikView Server License, Publisher license and all of the client access licenses (CALs).