Upgrading Sisense

Sisense releases several major versions a year, and a few minor versions in between. Each version includes new features and enhancements as well as other improvements.

Sisense allows you to decide when you want to upgrade to the latest version. There are no automatic updates for Sisense. Before upgrading, you can learn about the contents of each release in the Release Notes.

This topic provides prerequisites for upgrading Sisense, notes for upgrading to specific versions of Sisense, and instructions for upgrading Sisense on a single machine and Sisense in high availability environments where multiple machines are involved.

Before You Upgrade

Sisense recommends you follow these guidelines before you begin the upgrade process in single server and high availability environments:

Sisense Version Upgrades

Click the links below to view more information about upgrading to a specific version of Sisense.

Upgrading Sisense

Sisense is upgraded according to the installation settings you selected the last time you installed Sisense. To customize a new installation, you should uninstall Sisense and then install the latest version. See Customizing the Installation for more information.

The procedure below describes how to upgrade Sisense on a single machine. Additionally, upgrading to some versions of Sisense might require further changes. See Sisense Version Upgrades for additional instructions specific to each version of Sisense.

Also, if you are upgrading a high availability environment, see Upgrading Sisense High Availability Environments as well.

To install the latest version:

  1. Before installing the latest version of Sisense, it is recommended that you back up your current installation. See Backing Up a Sisense Installation for more information.
  2. Download the latest version of Sisense. For more information, see Downloading and Installing Sisense.
  3. Run the installation file as a Windows Administrator. Sisense automatically detects if a version is already installed, and displays the upgrade wizard.
  4. Click Continue.
  5. Click Upgrade.

Upgrading Sisense High Availability Environments

If you have implemented a high availability environment for Sisense and want to upgrade to Sisense V6.7.1 or later, there are a few files you must update following changes made to the Sisense infrastructure in addition to the procedure described in Upgrading Sisense.

The procedure below describes what files need to be modified so your high availability implementation continues working for Sisense V6.7.1 and beyond.

Note: When upgrading your high availability environment, make sure all of your Sisense servers are running the same version to avoid compatibility issues.

To upgrade your high availability environment:

  1. Back up the following files:

  2. Build Node(s):
    Web Node(s):
  3. Stop the Sisense Repository server on each of the web nodes.
  4. Upgrade Sisense on each of the Sisense nodes by running the Sisense installation file as a Windows Administrator.
  5. After you have installed Sisense on each of the machines, back up the default.yaml file on each of these machines located at:
    C:\Program Files\Sisense\PrismWeb\vnext\config\default.yaml
  6. In the build node, open the default.yaml located at C:\Program Files\Sisense\PrismWeb\vnext\config\default.yaml and do the following:
    1. Copy and replace the “db_security:” section from your build node to all the query nodes in your high availability environment.
    2. Remove the comments (#) from “replica_set:” section and update all the relevant parameters by copying the details from your default.yaml file on the build node that you backed up in Step 1 located at:
      C:\Program Files\Sisense\PrismWeb\vnext\config\default.yaml
      Note: Make sure that “name=replica_set” parameter is identical to the replica set name you gave in the file on the build node located at:
      C:\Program Files\Sisense\Infra\MongoDB\mongodbconfig.conf
    3. Copy and replace the “replica_set:” section to all other relevant Sisense web machines.
  7. Open the file db.config file located at C:\Program Files\Sisense\PrismWeb\App_Data\Configurations\db.config on the build node.
    Update the “MongoProvider” connection string with the IP addresses of your nodes, for example:
    For example:

    Note: The only values that should be changed are the IP addresses in the connectionString and replicatesetname.
  8. (Optional) If you have enabled SSL, you need to back up the following file, C:\Program Files\Sisense\PrismWeb\AnalyticalEngine\dist\config\production.json and move it to the same location after you have installed Sisense.
  9. Reset your IIS server.

Downgrading Sisense

When you upgrade Sisense, a backup copy of your MongoDB instance is automatically created. The MongoDB contains your server settings including your user and dashboard information. This allows you to reinstall earlier versions of Sisense without having to set up your system a second time.

Note: Before downgrading your Sisense installation, consult the Sisense Technical Support who can assist through the process.

During the uninstall process, you can choose to remove all user data, which deletes the MongoDB instance. The next time you install Sisense, your system will be completely clean, and your dashboard, dashboard list, and user data will be fresh.

Sisense is improving all the time and some versions of Sisense are incompatible with earlier versions. If you upgrade to a version and need to downgrade to an incompatible version, you can restore a backup copy of the MongoDB created automatically when you installed the last version of Sisense.

To downgrade to an earlier version of Sisense:

  1. In Windows, go to Add or Remove Programs.
  2. Locate Sisense and click Uninstall.

    The Uninstall Wizard is displayed.
  3. In the Uninstall Wizard, click Remove Anyway. If you select the Remove User Data checkbox, Sisense deletes all information stored in the MongoDB and this information must be configured the next time you install Sisense.

    Sisense is uninstalled.
  4. Install the previous version of Sisense. The downgrade process is complete.