Hi Monica,
for detailed licensing questions you should contact your QlikTech rep... we use a large number of document CALs in our environment and a small number of named CALs. Basically document CALs work the same way but need to be administrated differently as indicated.
Below the restrictions of named CALs - I'm not sure if these are still valid though, there was discussions on removing them... again you're best advised to talk to you QlikTech rep.
Cheers, Lukas
19.2 Types of CALs
There are four different types of CALs available:
• Named CAL (an identified user on a server) - Access is based on user identity
and valid for all documents on the server, that is any number of concurrent
sessions from one user on one machine at a time is allowed.
• Document CAL (an identified user within a given document) - Just as
above, the access is based on user identity, but the CAL is valid only for one
document. If the same user connects to two documents using this licensing
method, he will hence consume two Document CALs.
• Session CAL - Each Session CAL allows one user to access one QlikView
document, that is to have one session at a time. Anonymous users are
allowed, no identification of the client user is necessary.
• Usage CAL - Each Usage CAL gives the right to initiate one session (single
document) per running 28-day period. The session may last a maximum of
one hour. Any activity after the first hour has expired will count as a new
session (albeit without visible interruption). No identification of the client
user is necessary.
Note CALs are used for purposes of licensing only and they have nothing to do
with user authentication for data access purposes.
Identification
In order to utilize a Named CAL or a Document CAL, the client user must be
identified either via an authenticated user name (Windows Active Directory
216
or through a ticket exchange between the web server and the QlikView
Server) or with a unique machine ID. An IP address is not a valid form of
identification for a Named 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 Java and Ajax clients,
since machine name identification is not possible from these clients.
Document 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 into a single document, there are restrictions in the
documents which can be used with the Document CAL. The Named CAL,
the Session CAL and the Usage CAL can however be used to open any functional
QlikView document. The Document CAL, however, can only be used
with documents which have a single contiguous data model and do not contain
any chasm traps between tables.
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 as you move away from the fact table. Documents
containing such models typically fulfill the above demands and are
well suited for Document CALs.
But 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 one single column.
Further, the document may not contain any loosely coupled tables.
Finally, the cardinality (number of distinct values) of the key fields must
decrease as you move away from the fact table.
