You are on page 1of 7

Doc: QV-Word_US_Letter.docx Version: 0.

2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 1
Client Access Licenses
To connect to a QlikView Server (QVS), each client needs a Client Access License (CAL). The CALs are
purchased with QlikView Server and tied to the 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. If a user
is required to work with documents residing in different clusters, a separate CAL is needed for each of the
clusters.
Note! The CALs require the QlikView Servers within a cluster to be within the same geographical and
physical location and within the same network sub-net/segment.
CAL Types
The CALs described below are used to provide users access to the various QlikView Servers identified in
Editions of QlikView Server.
Note! CALs are used for licensing only and they have nothing to do with user authentication for data
access purposes.
CAL Type Description
Named
User CAL
(an
identified
user on a
server)
A Named User CAL is assigned to a unique and identified user (see
Identification for information on how users are identified) who may access as
many QlikView documents as may reside on the server or server cluster to which
the Named User CAL is assigned. A Named User CAL may be transferred to
another user pursuant to the software licensing agreement, in which case there is
a 24-hour quarantine before the Named User CAL can be transferred to another
user. There is no time limit for how long a user assigned a Named User CAL can
access a QlikView document.
Document
CAL (an
identified
user within
a given
document)
A Document CAL is assigned to a unique and identified user (see Identification
for information on how users are identified) who may access only the one
QlikView document to which the Document CAL is assigned. Multiple
Document CALs can be assigned to a particular user. For example, if a user
connects to two QlikView documents, the user will have been assigned two
Document CALs. A Document CAL may be transferred to another user pursuant
to the software licensing agreement, in which case there is a 24-hour quarantine
before the Document CAL can be transferred to another user. There is no time
limit for how long a user assigned a Document CAL can access the QlikView
document to which the CAL is assigned.



Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 2
CAL Type Description
Session
CAL
A Session CAL allows any user, identified or anonymous/unidentified, on one
QlikView client to access as many QlikView documents as may reside on the
server or server cluster to which the Session CAL is assigned for a minimum
period of 15 minutes. For Session CALs, the QlikView client refers to each
unique instance of the QlikView client (for example, the AJAX client, QlikView
Desktop, or the Internet Explorer plugin) on the user’s machine. The minimum
session time for a Session CAL is 15 minutes, which means that sessions that
end in less than 15 minutes will still consume the session until the 15 minute
mark is passed; those which terminate after 15 minutes will consume their actual
session length. By default, there is no maximum session length, but this can be
configured.
Usage
CAL
A Usage CAL allows any user, identified or anonymous/unidentified, to access
only one QlikView document, residing on the server or server cluster to which
the Usage CAL is assigned, from one client (for example, the AJAX client,
QlikView Desktop, or the Internet Explorer plugin) for a time 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. Every 28 days, the Usage CAL is refreshed and the user may once again
view a new QlikView document for 60 minutes, using the same Usage CAL.
Usage CALs are continuously recharged (at a pace corresponding to 1/28 of the
total number of Usage CALs assigned to the QlikView Server per day).
Identification
To use a Named User CAL or a Document CAL, the client user must be identified via an authenticated
user name (Windows Active Directory or through a ticket exchange between the web server and QlikView
Server). An IP address is not a valid form of identification for a Named User CAL. The two methods of
identification cannot be mixed on the same instance of QlikView Server. Note that the user name
identification requires Windows authentication on AJAX clients, since machine name identification
cannot be used for these clients.
Any CAL used by an identified user may not be transferred to another user, unless the transfer is due to a
change in the employment status or work duties of the prior user, in which case there is a 24-hour
quarantine before the CAL be transferred to another user.
Document CAL Restrictions
The purpose of the Document CAL is to provide a mechanism by which licensees can license the use of a
single document. To prevent the combination of many data models in a single document, there are
restrictions in the documents that can be used with the Document CAL. However, the Named User CAL,
the Session CAL, and the Usage CAL can be used to open any functional QlikView document. The
Document CAL can only be used with documents that have a single contiguous data model and do not
contain any chasm traps between tables.



Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 3
Most common data models used in QlikView documents can be used for Document CALs. For instance,
proper star schemas and snowflake schemas typically have the field with the highest cardinality in the fact
table and the keys in dimensional tables have a lower cardinality. For snowflake schemas, the cardinality
decreases further when moving away from the fact table. Documents containing such models typically
fulfill the above demands and are well-suited for Document CALs.
Documents with multiple logical islands are normally not allowed. Multiple logical islands are only
allowed, if the additional tables are unconnected and contain only few records or a single column.
In addition, the document may not contain any loosely coupled tables.
Finally, the cardinality (that is, the number of distinct values) of the key fields must decrease when
moving away from the fact table.
Combining Different CALs
A given instance of QlikView Server can carry any combination of the CAL types listed in CAL Types.
When different CAL types are combined on the same server, 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.
7. If none of the above, access is denied.
License Lease
A QlikView client that does not have a registered license is allowed to connect to QlikView Server and
“borrow” a license, so that the user can work offline for a period of 30 days. The QlikView client must
then make an authenticated log on (not anonymous) and obtain a Named User CAL. Each time QlikView
is started, QlikView tries to contact QlikView Server and renew the license lease. If the client cannot
reach the server after 30 days, the license lease expires.
A license lease can only be used with QlikView Desktop and the Internet Explorer plugin. This means a
license lease cannot be obtained when using an AJAX client.
Cluster Licensing
A special type of license is available to allow multiple QlikView Server installations to share the same
license serial number and support shared CALs. The servers are automatically considered as clustered.
Note that this configuration affects networks where unauthorized license sharing between test and
production environments has been configured.



Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 4
Note! The CALs require the QlikView Servers within a cluster to be within the same geographical and
physical location and within the same network sub-net/segment.
Cold Standby Servers
QlikView Server license keys can be installed on as many servers as required provided that only the
licensed number of QlikView Servers are running at any given time. Thus, a cold standby environment
can be installed and ready-to-run, but cannot be live (that is, the Windows services cannot be started) and
in use prior to the live environment being shut down.
Editions of QlikView Server
QlikView Server comes in a number of editions designed for different organizations and purposes.
Upgrading is done through the license key.
Editions
The various editions of QlikView Server are listed below.
Edition Description
QlikView
Enterprise
Edition (EE)
Server
QlikView EE Server is designed to be used in large and complex deployments
and provides features such as unlimited documents, server-based collaboration,
integration with third-party security systems, server clustering, and cluster
licensing. The minimum configuration of a QlikView EE Server is five (5)
Named User Client Access Licenses (CALs).
QlikView
Small
Business
Edition
(SBE)
Server
QlikView SBE Server is designed to be used in smaller deployments. The
minimum configuration of a QlikView SBE Server is five (5) Named User
CALs.
QlikView
Information
Access
Server (IAS)
QlikView IAS is a QlikView Server that is licensed for an uncapped number of
users, but limited to a single QlikView document. QlikView IAS runs in
anonymous mode and must be publically accessible without authentication (on
the public Internet), that is, it must not be placed behind a firewall. No
QlikView client can access QlikView IAS – the user interface must be built by
the end user either manually or by using QlikView WorkBench.

Note! There is no license lease from QlikView IAS.




Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 5
Edition Description
QlikView
Extranet
Server
(QES)
QES allows end users to deploy QlikView solutions to their extranet. QES is
based on QlikView EE Server, but only supports up to three QlikView
documents. The server can be deployed with a combination of Session and
Usage CALs. QES supports mobile clients and can be deployed in clustered
environments. The AJAX client or a customized AJAX client can be used via
QlikView WorkBench, which is included in QES.

In addition to the editions of QlikView Server described above, there is also a number of additional,
server-related products, all of which are listed below.
Product Description
QlikView
Test Server
QlikView Test Server is a license that provides an environment separate from
production to use for data validation, application testing, and
preparation/migration of QlikView documents to new versions and/or releases
of QlikView.
QlikView Test Server comes in two editions, QlikView EE Test Server and
QlikView SBE Test Server, both of which have the same features and
limitations as the corresponding production servers. In addition, the watermark
“Test” is superimposed on all charts and added to all object captions.

Note! There is no license lease from QlikView Test Server.

QlikView
Publisher
QlikView Publisher is a license that adds significant functionality to the
standard reload capability of QlikView Server. QlikView Publisher includes
functionality to handle field level security and access control from central
administration software like Window Active Directory or Novell® LDAP.
QlikView Publisher is also needed to support complex distribution models for
QlikView documents. In addition, each license of QlikView Publisher allows
an additional node/server for reload, distribution, or security management in a
multi-node/server deployment.
With the additional component QlikView Publisher Report Distribution, any
QlikView document report can be distributed as a .pdf file to a folder or via
email or SMTP.
QlikView
WorkBench
QlikView WorkBench (an add-on to QlikView EE Server) is a development
tool for creating web mash-ups with QlikView. It features drag and drop
editing capabilities within the Microsoft Visual Studio® development
environment and allows for custom web interfaces and integration with third-
party services.

Note! QlikView WorkBench is not available for use with QlikView SBE
Server.




Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 6
Product Description
QlikView
Web Parts
for
Microsoft
SharePoint®
QlikView Web Parts (an add-on to QlikView EE Server) for Microsoft
SharePoint allows for rapid deployment of QlikView objects within Microsoft
SharePoint portal environments.

Note! QlikView Web Parts are not available for use with QlikView SBE
Server.

QlikView
Local Client
QlikView Local Client is a client with all functionality used to develop
QlikView documents. QlikView Local Client is deployed, if the end user
deploys local clients only.
QlikView
Personal
Edition
Anybody registered on QlikView.com is allowed to download QlikView and
develop QlikView documents for personal use. There are no restrictions to
QlikView Personal Edition except that it cannot open QlikView documents
created by other users or perform an import of an entire layout from an XML
file.
Features and Limitations
The table below lists the features and limitations of each edition of QlikView Server (Yes = supported, No
= not supported).
EE SBE IAS QES
Licensing
Named User CALs Yes Yes
(max
25)
No No
Session CALs Yes No Yes
(unlimited)
Yes
Usage CALs Yes No No Yes
Document CALs Yes Yes
(max
100)
No No
External Users Allowed? No No Yes Yes
Clients
AJAX (and mobile devices via AJAX) Yes Yes Yes
(WorkBench
included)
Yes
(WorkBench
included)
Internet Explorer Plugin Yes Yes No No
Installed QlikView Client Yes Yes No No
Scalability
Can be clustered (additional server license
required)
Yes No Yes Yes
Unlimited Documents Yes Yes No
(1 only)
No
(3 documents
only)



Doc: QV-Word_US_Letter.docx Version: 0.2
ID: KXTCKYMSY4RV-54-27 / English Owner: [Owner]
Modified: [Info Modified] / [Info Modified By] Page 7
EE SBE IAS QES
Integration
Third Party Security Integration Yes No No Yes
Dynamic Data Update Yes Yes Yes Yes
Features
License Lease (offline access, Named User
CALs required)
Yes Yes No No
Annotations Yes Yes No Yes
Collaboration (sheets, sheet objects, and input
fields)
Yes Yes No No
Session Collaboration Yes Yes No Yes
QlikView Publisher and PDF generation
(additional license required)
Yes Yes No No
QlikView Connector for use with SAP
NetWeaver® (additional license required)
Yes Yes Yes Yes
Test Server Option Yes Yes Yes Yes
Can be embedded in Microsoft SharePoint
(QlikView Web Parts for Microsoft SharePoint)
(additional license required)
Yes No Yes Yes
Build bespoke mashups/AJAX applications
(QlikView WorkBench) (additional license
required)
Yes No Yes
(included)
Yes
(included)
Security
Section Access Yes Yes No Yes
Document Metadata Service (DMS) Yes No No Yes
Active Directory/NTFS Yes Yes No Yes
Anonymous User Yes
(with
Session
CALs)
No Yes
(mandatory)
No