Does UAT Testers required Named CALs or Doc CALs

[#1]

Hi,

I would like to know if UAT Testers would be required Named CALs or Doc CALs to access the application?

[jagan]

Hi Swaroop,

1 Doc CAL is for one Qlikview Dashboard and with 1 Named CAL there is no restriction, simply if user needs access to more than 2 Dashboards then assign Named CAL otherwise assign Doc CAL.

Hope this helps you.

Regards,

Jagan.

[#3]

I got the point. Thanks for the Replies !!!..

I have one query. How can we control the security to server access/Folder access when we assign Named CALs to Users.

[SreeniJD]

Simpler option - > If you have Publisher-> set the rights (read only) on documents distribution

Not much simpler -> through Server, set NTFS permissions and then place your document in a subfolder in your document root folder. Apply read only rights to sub directory and inherit these properties to root folder.

HTH

Sreeni

[stevedark]

As Sreeni says you can set permissions on distribution or through Active

Directory.

I would say that AD is the simplest route, as there are always people in

the organisation that know AD.

What is important though is that you should never use licence allocation

for security. Think of it as two separate things - security for who is

allowed to see a document and licences for who you have paid to see a

document. The two are very different, and you never know when licencing may

change (for example you may purchase a Session CAL) and end up allowing

users into things they should not see.

Hope that helps,

Steve

[Anonymous]

Hi,

Yes For sure ..

Document cal for single Document access for a UAT user .

Named cal for Multiple Document  access for a UAT user.

Normally in the Projects mostly UAT part  done by developer . I think we don't have Such requirement but in case will go this way .

and to provide to read only access and all are secondary things.

Thanks ,

Bunny.

[Peter_Cammaert]

Just some extra info that may help you decide how to set-up a testing environment.

A test server comes with the exact same number and type of licenses that the production server has/had. But because the group of testers is usually much smaller than the group of regular end-users on your production platform, you will have a lot of headroom when assigning CALs on your test server.

In addition to this, having spare licenses offers extra choices to tune your test set-up as you go. For example, you can initially assign Document CALs to all testers and change those into Named CALs (and back) for specific users without delay or license restriction. You have a lot of flexibility here, and you'll learn to manage and tune this environment while you move on..

However, make sure that you set-up your QlikView environment as Steve suggests: strictly separate security from license assignment. Or you may get one or more embarassing surprises.

[#8]

I am able to get the glimpse of the above explanation.Can please explain bit more from Steve's Statement "

What is important though is that you should never use licence allocation

for security." " strictly separate security from license assignment."..How we need to decide and work on this at the time of Installation?

[Peter_Cammaert]

You may want to launch a new discussion on security vs license assignment. Otherwise this thread may wander through every aspect of setting up a QlikView Enterprise architecture and therefor become a bit long.

[stevedark]

Simply set up your security as if all users are going to have a Full User CAL, and therefore will be able to see everything.

To secure apps set up Active Directory groups based on function (e.g. Finance, Sales) and place users into these groups.  Then create folders for QVW files aligned to each of those groups.  Ensure that only the correct AD groups have access to each of these folders (don't lock yourself out in the process though).  Place the appropriate QVWs in the right folders.

Test.

This should then make your documents secure, regardless of CALs.  Also, it has the advantage that apps are hidden from the Access Point, rather than having users click on documents and then be given a "You Do Not Have A CAL" message.

This article talks more about folder structure:

http://www.quickintelligence.co.uk/qlikview-folder-structures/‌

Hope that helps,

Steve