Upgrading and migrating QlikView Server from 11.20 to November 2017 or later
When you upgrade QlikView Server, you can either upgrade on the same server, or you can upgrade and migrate to a different server. This topic outlines the steps you need to follow to upgrade from QlikView Server 11.20 to a newer version, and includes the steps for migrating to another server with a different machine name.
Before you perform the upgrade and migration, ensure that you have created an appropriate backup of your QlikView Server deployment. For a detailed list of the files and folders to backup, see Backup and upgrade preparation.
For a detailed list of changes and issues when upgrading from QlikView Server 11.20, read the following Qlik Support article: QlikView 11.20 End of Life Upgrade: Known Issues and changes in product behaviour.
Upgrading on the same machine
To upgrade QlikView Server on the same machine:
- Create a backup of your QlikView Server 11.20 installation. It is always important to create a backup of your installation, however this step is not essential if you are upgrading on the same machine. See Backup and upgrade preparation.
-
Download the latest version of QlikView Server from Product Downloads.
For more information, see Downloading installation files.
- Stop the QlikView services. During the upgrade process all the services are stopped by the installer, and restarted automatically, but it is still recommended that you stop all services before proceeding with an upgrade.
-
Run the installation program as an administrator, and follow the on screen instructions. For a step-by-step description of the install procedure, see: Installing QlikView Server.
Information noteWhen you upgrade from a QlikView Server 11.20 installation using certificates to QlikView Server November 2017 or later, remove the certificates before starting the upgrade. When you launch the installation program, a warning window is displayed if certificates are detected. You remove the certificates using the Microsoft Management Console (MMC). For more information, see: Removing certificates - During the installation, select a service authentication method. Choose either Use digital certificates or Use QlikView Administrators Group. If you previously used digital certificates then you should also choose this option when you upgrade.
- Restart your machine once the installation process has finished to ensure that all services start up correctly.
- Open the QlikView Management Console, and apply your license information for QlikView Server, and QlikView Publisher.
- Restart the server to apply the license information.
Upgrading on a multi-server deployment
To upgrade a multi-server installation:
- Stop all services on each machine before you perform the upgrade.
- Perform the upgrade procedure on each machine of the multi-server setup.
Upgrading and migrating to a different machine
To upgrade and migrate QlikView Server to a different machine follow the steps in this section.
Upgrade QlikView Server to a different machine:
- On your current machine, create a backup of your QlikView Server 11.20 installation. See Backup and upgrade preparation.
-
Download the latest version of QlikView Server from the Product Downloads.
- Launch the QlikView Server upgrade wizard, and follow the on screen instructions. For a step-by-step description of the installation procedure, see: Installing QlikView Server.
- During the installation, select a service authentication method. Choose either Use digital certificates or Use QlikView Administrators Group. If you previously used digital certificates then you should also choose this option when you upgrade.
- Restart your machine once the installation process has finished to ensure that all services start up correctly.
- Open the QlikView Management Console, and apply your license information for QlikView Server, and QlikView Publisher.
- You will be prompted to restart the server after applying the license information.
Migrate and restore your backup:
- Stop all QlikView services on both the current machine and the target machine.
- On the target machine, remove or rename the ProgramData\QlikTech\ManagementService\QVPR folder, as this will be replaced with your backed up version.
- On the target machine, remove or rename the qvpr_<TargetMachineName>.ini file located in ProgramData\QlikTech\ManagementService.
- Copy the QVPR folder and the qvpr_<CurrentMachineName>.ini file from your current machine to your target machine (make a note of the folder name).
- Rename the .ini file from qvpr_<CurrentMachineName>.ini to qvpr_<TargetMachineName>.ini.
- In the .xml files in the ProgramData\QlikTech\ManagementService folder, and in the Config.xml file, change all references to the current machine name to point to the target machine name.
- Restart the QlikView services. Start the QlikView Management Service first, then wait a minute, and start the other services in any order.
- Restore the SourceDocuments folder.
When you restore the source documents folder, you have two options: - If you are storing your source documents in the default ProgramData\QlikTech\SourceDocuments folder, then move all your source documents to the same location on the target machine.
- If you are storing your source documents in a different folder location, then add the source documents folder path in the QlikView Management Console. To do this see the Add section in Source Folders.
- Shut down your old server machine.
Upgrading and migrating a multi-server deployment
When upgrading and migrating a multi-server installation from QlikView Server 11.20 to QlikView Server November 2017 or later, perform the above procedure for each machine in your multi-server deployment.
Summary of steps:
- Perform a backup of each machine in your multi-server installation.
- Install a running, licensed version of QlikView Server on each of the target machines.
- Migrate and restore the backup specific for each machine of the installation. For example, the QVPR folder must be migrated (and the machine name changed) only to the target machine running the QlikView Management Service.
- Restore the Source Documents folder.
- Shut down the old server machines.