Basic instructions on how to migrate a QlikView server installation to a different host.
If an upgrade is planned, see How to Upgrade or Migrate QlikView 11.20 and later versions
The instructions in this article have been sourced from the above.
The example is written for a single node environment.
See the QlikView Online Help Upgrading to a different machine
When planning your migration consider how to maintain CAL assignments. See Migrating QlikView Server without losing CAL assignments?Summary:
- On the new machine, install a running, licensed version of QlikView Server.
- Stop all QlikView services on the old machine.
- On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\QVPR folder.
- On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\qvpr_<NewMachineName>.ini file.
- Copy the QVPR folder and the .ini file “as is” from the old machine to the new one (that is, keep the folder name).
- Change all references to <OldMachineName> to <NewMachineName> in the following files:
- Rename the .ini file (that is, change qvpr_<OldMachineName>.ini to qvpr_<NewMachineName>.ini).
- Change all references to <OldMachineName> to <NewMachineName> in the QVPR .xml files.
- Start the QlikView services on the new machine.
- Do NOT use the QMC to change the Distribution Service Source Document paths, as doing so will potentially break the task links. If you need to change paths, go directly to the SourceFolderDocumentResource.xml in the QVPR and make the changes directly there to point to the new paths, do not change anything but the path information, as the GUID links must stay the same in order to keep the tasks aligned. An alternative to editing the XML file directly is to use the XML DB Viewer power tool which allows you to search as well as find/replace.
- Shut down the old machine.
If there have been any changes made to the QMS exe.config
file, be certain those changes are documented somewhere, as they will need to be re-applied to the new QMS exe.config file post-upgrade. The upgrade uninstalls the 11.20 files and installs new 12.xx files, which means the exe.config
will be removed and recreated without customizations. The QMS is unique in that it does not write changes to the programdata
path like the other services, so be certain the customizations are documented and reapplied post-upgrade prior to bringing the services back online again.