Qlik Community

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Support Case Portal has moved to Qlik Community! Read the FAQs to start exploring Support resources.

Upgrading and Migrating Best Practices for QlikView Services Config, Settings.ini and QVB Settings.ini Files

Chip_Matejowsky
Support
Support

Upgrading and Migrating Best Practices for QlikView Services Config, Settings.ini and QVB Settings.ini Files

Environment

QlikView, all versions

Description

When upgrading QlikView Server/Publisher to newer versions or migrating to different servers, it is important to take steps to backup and configure the QlikView services config files, Settings.ini files, and the QVB Settings.ini file to ensure that the environment has the same configurations as it previously did.

 

Backing up QlikView Services Settings.ini Files and QVB Settings.ini File

The QlikView services all have configuration files that you can edit to suit the requirements of your deployment.  There are configuration and settings files for each QlikView service, and these are stored in the subfolders in your QlikView data directories.  The QVB Settings.ini file is by default located in %Windows%\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch and should be backed up as well.

If you have a created customizations of your own, you will have edited the configuration file for the relevant QlikView service.  From QlikView November 2018 and on, you can monitor all non-default values applied to the services in your deployment (except for the QlikView Server Service, QVS) directly from the QlikView Management Console (QMC).  In the QMC, go to status > services and select one of the services in your QlikView Server deployment.  If one or more custom config values are in place, they are listed in the information tab on the right-hand side of the screen.  The list shows which config settings are modified, on which machine, and what is the existing value compared to the default value.  Discrepancies between machines running the same service are listed as well.  For versions prior to QlikView November 2018, it will be necessary to manually make note of any and all non-default settings in the config files, Settings.ini files and QVB Settings.ini so that they can be applied post-upgrade.

 

Post Upgrade or Migration

Performing an in-place upgrade will overwrite existing config and Settings.ini files; and an installation on a new server you plan to migrate the environment to will not have previously made modifications.  If you restore your changed configuration and settings files to your upgraded deployment, you may overwrite important changes that Qlik has added in subsequent release and updates.  Therefore, to avoid loss, it is important to note down all the changes, or customizations that you have made to your configuration and settings files.  Once you have completed the upgrade process, you need to append your changes to the new config files.  If you follow this approach, it will ensure that your deployment includes all the latest config files, as well as all the customizations from your earlier deployment.

For example, if you have created your own customizations in the QlikView Distribution Service, you will have made changes to the QVDistributionService.exe.config file.  To back this up, navigate to C:\Program Files\QlikView\Distribution Service folder, and make a copy of the QVDistributionService.exe.config file.  Then, after upgrade, append your customizations to this file.

 

Related Content

Labels (1)
Version history
Revision #:
7 of 7
Last update:
‎2021-03-15 05:44 AM
Updated by: