Is it possible to migrate a QlikView Server installation to a different machine without losing existing CAL assignments and tasks?Environment:
QlikView any version
For general migration guidance, please see QlikView: Upgrading and migrating to a different machine
. This covers the general moving of the services, however does not offer details on tasks or CALs.
- 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 both User and Source Document use must retain their folder structure, if tasks and CALs should be kept
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.
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 CALs are linked to.
(only available with Publisher license) are the source .qvw files used by the QlikView Publisher / Distribution Service to reload and publish / distribute previously mentioned User Documents.
! These files are what the tasks are linked to.
While planning the move of the QlikView environment, make sure that the Source Document Folders
and 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!
The same principle applies for Source Documents, if a Publisher license is available.
If any of those folders change during the migration, CAL assignments (they are specific to location and file), as well as tasks, are lost.