QLIKVIEW LICENSE LEASING
QlikView Technical Brief
QlikView Test Server
In most cases, customers choose to replicate the licenses they have in production to a test environment, utilizing the QlikView Test Server for this purpose. The QlikView Test Server does not permit license leasing because it does not have any allocated licenses. When users open QlikView applications on the Test Server, they actually use their production QlikView Server license. A QlikView developer only requires a single licensing server to be given offline development capabilities removing the restriction of the Personal Edition. This does not prohibit them in any way from creating and posting QlikView applications to any number of additional servers.
if the qlikview server is a test server, from here (pag. 4)
QlikView Test Server
In most cases, customers choose to replicate the licenses they have in production to a test
environment, utilizing the QlikView Test Server for this purpose. The QlikView Test Server
does not permit license leasing because it does not have any allocated licenses. When users
open QlikView applications on the Test Server, they actually use their production QlikView
Server license. A QlikView developer only requires a single licensing server to be given
offline development capabilities removing the restriction of the Personal Edition. This does
not prohibit them in any way from creating and posting QlikView applications to any number
of additional servers
QlikView Test Server is a way to license for QlikView Server that you can purchase separately. A Test Server is always and only possible if you have a production (non-Test) Small Business Server or Enterprise Edition and it replicates the same environment.
An example: you have a Enterprise Edition Server with two nodes to create a QlikView cluster and allow 100 named users, and a Test license corresponding to that environment. The Test license will allow to have two nodes in a different environment as well and the same 100 named users. So if you need a license to develop, that should come from the non-Test environment.
Actually, the test server will have the licenses and we can lease the licenses. But the thing is, once you lease a license in single environment, you can use it only in that environment. If you use the same thing in different environment, it shows as you are running personal edition.
For example, your production environment is a cluster and you leased a license from production server and use it in the dev. You cannot use the same license lease in production environment. So, in this case, you see license lease in dev environment (here you are leasing from production QMC), but in production you cannot open any other documents.
If you need to have the same license lease in production, assign a named cal in dev QMC to yourself and use this in production environment.
Allow me to apply Miguels statement to your situation.
If you have a Production server with a regular QlikView Server licenses (say MachineP) and a Test server with a QlikView Test Server License (say MachineT), you can promote your QlikView Desktop from PE to "licensed" only by leasing a license from the production machine (MachineP). There are two main cases:
1. If you want to open any and all QVW files (the files themselves) from either the production environment or the test environment, open QV Desktop, select Open in server, navigate to the production machine (MachineP) and do something (selecting a file, opening a document whatever - the lease is usually transferred upon simply displaying the document tree. Only if you have a Named CAL assigned in Production QMC - MachineP, that is)
2. If you want to use QV Desktop as a client for visiting either Access Point, then you'll need a license assignment in both QMCs. That's because a license leased from production will not ring a bell with the test server - your account isn't recognized as a valid QV Test server user if you don't have a license (either a document or a named call) assigned in the Test QMC (on MachineT). So for visiting the Test AP and opening all or specific documents from that particular Access Point, you should have at least one license assigned to you in the Test QMC.
Usually, the range and type of client licenses in the Test Server license is exactly the same as those embedded in the Production license. But the Test server does not allow leasing (otherwise you would have double the number of Desktop licenses that you paid for) and stand-alone QlikView servers do not exchange/recognize each others CALs. So no floating licenses (yet). The best thing you can do is copy the license assignments from MachineP to MachineT (or vice versa) for all users/developers that need to visit/manage both machines.
Hope I'm making it clearer to you. If not, feel free to ask away.
Thank you Peter. It's bit clearer.
Okay, I read again what you said, I can't lease a license with the test server.
"The best thing you can do is copy the license assignments from MachineP to MachineT (or vice versa) for all users/developers that need to visit/manage both machines."
Can you explain, please ? Do you mean the allocations of the CALs ?
Sorry if my questions are stupid but I discovered QV Server a few days ago
Thank you again for your help
What means is that, say, your user is DOMAIN\LAURA and you have a license in MachineP. Then you can use the same license to access and develop on MachineT.
And vice versa: if you do not have a license assigned to user DOMAIN\LAURA in MachineP you will not be able to access and develop on MachineT.
When I say a license assigned in MachineP is that you have a license assigned to that DOMAIN\LAURA (or whatever your actual username is) you will be able to access to MachineT.
But, the Server that leases the actual license is MachineP, so you need access to it, apart from having a license assigned to the user.
The process is always:
- The QlikView Sysadmin assigns you a license in MachineP
- You use Desktop > Open in Server to MachineP to get your license
- You now have a lease for 30 days
- You can now open any document, regardless the Server it is
P.S.: This document has all relevant information on how license lease works.
Thank you Miguel
The problem I have is that I want to open my documents when i'm on MAchineT without accessing to MAchineP because there is no links between the 2 machines.
I have had a look at the licences in the management console. When I go to the management console from MachineT:
There is this line which is not in the licence of MAchine P : TEST_EDITION;YES;;
What does that mean ?
Moreover, the 2 machines have 2 different numeros of licences.
Im sorry if this is a bit confusing, I'm a very very beginner
You are welcome,
Short answer: you cannot open documents on MachineT unless you have a license borrowed from MachineP. You need to have a license assigned to your user in MachineP and you need access to MachineP to get that license.
The TEST_EDITION keyword means that is a Test license type, that is all what we have been talking above (i.e.: you cannot borrow licenses from a test server). And yes, the license numbers are different, but in our systems, they are linked (you issue a test license for a non-test/production license).
I strongly recommend that you check with your Partner Manager (if you are a Qlik Partner) or Account Manager (if you are a Qlik Customer) so they can explain in detail the licensing model of QlikView.
I will be glad if you can help me with the anwsers for the following.
- DOMAIN\LAURA has named cal licence in MachineP ( Production Server )
- MachineP and MachineT are in the same environment.
- There is no user id LAURA in machineT.
- MachineT has user id as BI_USER.
- 5. BI_USER wants to lease a license from MachineP using domain\laura account. Is this possible ?
- If answer to point 5 is, user domain\laura will still be able to access the qvw applications in the MachineP(production server) through accesspoint.
- The number of named cals in MachineP will not reduce due to leasing of licence.
- Can a user in the domain lease a licence of another named user in the MachineP.
BI_USER could eventually use DOMAIN\LAURA account provided he knows her password. In this case, then yes, he would be able to use DOMAIN\LAURA's license.
However, as soon as DOMAIN\LAURA connects she will drop BI_USER connection, since the license can only be leased to one user+computer (session). Put in different words, the same user (in this case, for QlikView, user is DOMAIN\LAURA) cannot have more than one sessions at the same time.
If all the above is correct, there will only be one license leased.