Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Nov 22, 2023 4:15:19 AM
Dec 5, 2018 4:29:23 AM
Is it possible to migrate a QlikView Server installation to a different machine without losing existing CAL assignments such as Named User CALs and Named Document CALs?
Can Named CALs be moved during an upgrade?
For general migration guidance, please see QlikView: Migrating to a different machine. This covers the general moving of the services, however does not offer details on tasks or CALs.
Applying a new license will always clear CAL assignments. Upgrading QlikView from one major version to another without moving host machines will retain them automatically.
- An important detail to note when moving a QlikView environment, is that tasks and CAL assignments are dependent on folder structure.
- .qvw files (QlikView documents) for User Documents must retain their folder structure CALs should be kept
CALData.pgo stores the CAL assignments and is always stored in the QlikView Server Root Folder. The .pgo files include operational data and need to be moved to the new root directory. The CAL.data stores all CAL information.
User Documents are the .qvw files seen by end users on the AccessPoint. They are stored in the QlikView Server's Mounted Folders or Root Folder. These files are what the Named Document CALs are linked to.
While planning the move of the QlikView environment and wanting to retain CAL assignments, make sure that the User Document Folders retain the same structure.
Examples:
If all User Documents (AccessPoint) files are currently stored in c:\ProgramData\Qliktech\UserDocuments (the default location), then they will need to be moved to the local drive on the new machine.
Same for the .pgo files.
But if the User Documents (AccessPoint) files are currently stored in \\servername\share\folder, and .pgo files in \\servername\shareTWO\folder, then the new QlikView server needs to be configured to point at these locations. The old server needs to be shut down at this point. Two servers cannot point at the same User Documents or Root folder!
If any of those folders change during the migration, CAL assignments (they are specific to location and file), are lost.
Example Step by Step instructions for a single node QlikView Server
The current setup:
All services are installed on QlikServer1.
The Root and User Document folders are configured to point at shared folders.
We have a User CAL assigned to User1 and a Document CAL assigned to User3.
Steps to migrate and keep the CALs:
- Stop all services on QlikServer1
- Install an identical version of QlikView on QlikServer2 and license the QlikView Server
- Stop all services on QlikServer2
- The quickest way to now align the folders is to modify the QlikView server settings.ini file. This is stored in C:\ProgramData\QlikTech
Open the file in a text editor.
It will currently begin like this:
[Settings 7]
ServerLogFolder=C:\ProgramData\QlikTech\QlikViewServer
NumberOfDocuments=-1
DocumentDirectory=C:\ProgramData\QlikTech\Documents
DocumentTimeout=28800
StandardReload=1
We will modify the DocumentDirectory= (Root) and we will add a new line DocumentMounts= (User Documents).
After our modification, the file will begin like this:
[Settings 7]
ServerLogFolder=\\dc1\share\Front-end\QvsLogs
NumberOfDocuments=-1
DocumentDirectory=\\dc1\share\Front-end\QvsRoot DocumentMounts="UserDocuments","\\dc1\share\Front-end\UserDocuments",1; DocumentTimeout=28800
StandardReload=1 - Save the file and start the QlikView Server service
Results:
Reviewing the setup now, we can see that the User Documents are available, that User3 still has their Document CAL, and that User1 retained their User CAL as well.
