topic Re: Same Named CAL for two different folder structures in QlikView

Same Named CAL for two different folder structures

Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I am working for 2 different clients. I would like to go with two separate folder structures and wanted to get confirmation if one Named CAL is sufficient to accommodate for two projects.

Re: Same Named CAL for two different folder structures

karthikeyan1504 — Wed, 12 Aug 2015 03:46:15 GMT

Hi,

The Named CAL is user login based. So you cannot share it for different users. If the same end user wants to access more than one dashboard, then you can assign a single named cal for that user.

otherwise you have to assign the document cal or session cal.

Warm Regards,

Karthikeyan.

Re: Same Named CAL for two different folder structures

Wed, 12 Aug 2015 15:36:17 GMT

Hi,

Thanks for the reply,

As a Developer, I would be working on two different projects, So when I have been assigned a Named CAL ,Can we use it for two different projects.

Re: Same Named CAL for two different folder structures

Qrishna — Wed, 12 Aug 2015 15:39:35 GMT

two projects has two different accesspoint urls?Then NO.

two projects has same accesspoint URL? then YES.

Re: Same Named CAL for two different folder structures

Wed, 12 Aug 2015 15:44:02 GMT

Hi,

Here, two projects means different clients altogether and we would be having one QV Server installed. So Two projects different also access point URL can be same?

Re: Same Named CAL for two different folder structures

Qrishna — Wed, 12 Aug 2015 16:08:43 GMT

So Two projects different also access point URL can be same?

I did not understand this part. please explain?

Re: Same Named CAL for two different folder structures

Wed, 12 Aug 2015 16:18:38 GMT

As of now we are installing one QV Server. But we have two clients. For the two clients ,Server installation is same in virtual machines. My Query is when we have two projects(Client A and Client B) with same QV server .I am working for two clients .Can I have only one Named CAL for me and work for two different clients.

Re: Same Named CAL for two different folder structures

Wed, 12 Aug 2015 16:19:52 GMT

So when I work for two different clients, would we be having same access point or two different access points.

Re: Same Named CAL for two different folder structures

jagan — Wed, 12 Aug 2015 16:32:00 GMT

Hi,

If you are using the Same Qlikview Server then one Named CAL is enough for the two mounted folders. The Named CAL is based on the users not by folders. So a user can access any document in any mounted folder with single Named CAL if he has access.

Hope this helps you.

Regards,

Jagan.

Re: Same Named CAL for two different folder structures

Qrishna — Wed, 12 Aug 2015 16:38:24 GMT

Yes you can can have one named CAL on 1 server for multiple clients.(I've mentioned this earlier also).

Re: Same Named CAL for two different folder structures

Wed, 12 Aug 2015 16:40:32 GMT

yes.. This Help me..

When we say availability SLA is < 99.5 % per month means what actually it refers to when we go with Virtualization?

Re: Same Named CAL for two different folder structures

jagan — Wed, 12 Aug 2015 16:42:57 GMT

No idea.

Re: Same Named CAL for two different folder structures

karthikeyan1504 — Thu, 13 Aug 2015 01:43:04 GMT

Hi,

The qlikview licenses are restricted to one network.

You can have any number of virtual servers in one machine. If both of your servers are in same network, then you can use one named cal for your all dashboard developments. but if it is in different network, you need to have two separate named cal for two networks.

Hope this makes sense.

Warm Regards,

Karthikeyan.

Re: Same Named CAL for two different folder structures

Peter_Cammaert — Fri, 14 Aug 2015 12:10:31 GMT

It means that QlikView can be unavailable for no longer than 215 minutes (3 hours and 35 minutes cummulative) every month, not a minute more or penalty payments will be due. It doesn't matter whether you use virtualization technology or real hardware, although the former would make it much easier to failover in case of emergency.

I'm guessing that you actually mean SLA level > 99.5%. In your post, 10% availability would do just fine, which I think is not your customers intent.

Peter