Upgrading

You can upgrade from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later using the Qlik Sense setup program. When upgrading, the previous version is completely replaced by the new version.

To upgrade from Qlik Sense 3.1 SR2 or later with a shared persistence model to Qlik Sense June 2017 or later, see Upgrading from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later.

Qlik Sense June 2017 and later versions do not support the synchronized persistence model. To upgrade from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later and migrate from a synchronized persistence model to a shared persistence model, see Upgrading and migrating from synchronized to shared persistence.

Upgrading from any version of Qlik Sense earlier than 3.1 SR2 to Qlik Sense June 2017 or later cannot be done using the setup program. To upgrade from earlier versions of Qlik Sense with a synchronized persistence model to Qlik Sense June 2017 or later, see Upgrading to Qlik Sense June 2017 or later from Qlik Sense versions earlier than 3.1 SR2.

Qlik Sense apps

When you upgrade Qlik Sense all existing apps need to be migrated to ensure compatibility between the versions. This happens automatically when the system starts the first time after the upgrade. If the migration fails for one or more apps, these apps will not be available in the Hub after the upgrade. Apps that are not migrated are indicated in the Apps section of Qlik Management Console, where you can also perform a manual migration.

Multi-node deployments

In a multi-node deployment, all nodes must run the same version of Qlik Sense to be able to communicate with each other. It is recommended to upgrade with all nodes offline, and to start with the central node.

Qlik Sense repository database

Qlik Sense June 2017 and later versions use PostgreSQL version 9.6 for the Qlik Sense repository database. If you upgrade in place without uninstalling Qlik Sense the Qlik Sense repository database is upgraded to PostgreSQL version 9.6 and your data, and standard settings are carried forward. If you have made custom configurations to your PostgreSQL installation, those must be recreated in the PostgreSQL after upgrade.

PostgreSQL version 9.6 is installed with the latest version of Qlik Sense. If you have uninstalled Qlik Sense but maintained your PostgreSQL database, and you want to upgrade your Qlik Sense deployment, you must create a database dump file and restore the PostgreSQL database manually. You will also need to manually reconfigure any custom parameters.

The PostgreSQL installation included in the Qlik Sense June 2017 or later setup does not include pgAdmin tools. For information about manually installing the PostgreSQL database, see Installing and configuring PostgreSQL.

Before you upgrade Qlik Sense, do the following:

• Review System requirements for Qlik Sense.
• Download the Qlik_Sense_setup.exe file.
• Make sure you have logged on as an administrator using an account that has an actual password defined, that is, not a blank password.
• If you are running the Qlik Sense services with a LocalSystem account then you must change to a service user account before begining the upgrade.
  See: Upgrading from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later
  
• Create a backup of your Qlik Sense deployment before upgrading.

The

Do the following:

1. Stop your Qlik Sense services.
2. Upgrade your central node by launching the Qlik Sense setup file (Qlik_Sense_setup.exe).
3. Select Upgrade to upgrade your existing shared persistence deployment.
4. Accept the license agreement and click Next.

5. On the Service Credentials page, enter the Username and Password for your Windows Qlik Sense service user account.

   If the user is member of a domain, enter the service account as <domain>\<username>. For more information, see User accounts.

6. On the Ready to upgrade page, select the appropriate check boxes if you want the setup to create desktop shortcuts and automatically start the Qlik Sense services when the setup is complete, and click Upgrade.
7. Check that all of the Qlik Sense services have started successfully.

8. Check that all apps have been migrated successfully on the central node. If migration has failed for one or more apps, resolve the issues before continuing.

   Warning note If the node running the app migration goes offline, migration will stop. It will not restart automatically. In a single node environment, all apps will have Migration status set to Unknown. See: Migrating apps. In a multi-node environment with failover nodes, the primary node will be replaced by the next available node, but migration will not restart. See: Failover. To resume migration, you will need to restart the following services, in order: Qlik Sense Service Dispatcher (QSD) and Qlik Sense Repository Service (QRS). See: Services.
9. Deploy the Qlik Sense upgrade with shared persistence on the remaining nodes.
Information noteAny custom manual configurations that you make to the PostgreSQL database must be manually reproduced after the upgrade.