Upgrade Instructions for Specific Versions

Sisense V7.3

If you are upgrading to Sisense V7.3 from a version before Sisense V7.2, review the Sisense V7.2 upgrade documentation above as there were significant changes to the Sisense architecture.

If you are upgrading from Sisense V7.2 or later to Sisense V7.3, you can upgrade without any special considerations.

Sisense V7.2

In Sisense V7.2, significant changes were made to the Sisense application server. These changes impact how Sisense can be installed and configured.

The table below summarizes the changes.

Application Server changed from Microsoft IIS/IIS Express to NodeJS

Pre-Sisense V7.2

  1. You had the option to install Microsoft IIS or IIS Express as the Sisense application server.
    See the following:
    Installing Sisense

    Custom Installation
  2. You had the option to install Microsoft IIS or IIS Express silently by editing the PrismFeature.XML files.
    See the following:
    Silent Installation
  3. You could write server side IIS-based plugins.

Sisense V7.2

The web application server is configured automatically, and you do not have to specify it for the silent installation. NodeJS is used as the application server, and IIS is used for minimal functionality. IIS Express is no longer supported.
See the following:

  1. Installing Sisense
    Custom Installation
  2. Silent Installation
  3. IIS-based server side add-ons will no longer work as expected and will need to be rewritten.

Migrating Sisense

Pre-Sisense V7.2

You had to copy and modified multiple configuration files to the new environment.
The following were the files that needed to be copied:
%ProgramFiles%\Sisense\PrismWeb\ECMNext\GraphQL\src\config\default.yaml

%ProgramFiles%\Sisense\PrismWeb\vnext\config\default.yaml
%ProgramFiles%\Sisense\Infra\MongoDB\mongodbconfig.conf
%ProgramFiles%\Sisense\PrismWeb\App_Data\Configurations\db.config

See the following:
Migrating a Sisense Installation

Sisense V7.2

You need to copy several directories to the new environment.
These directories include:
%ProgramData%\Sisense\PrismWeb\Repository
%ProgramData%\Sisense\Infra

Delete an identifier value from your application database.
See the following:
Migrating a Sisense Installation

Backing Up Sisense

Pre-Sisense V7.2

You had to back up multiple configuration files.
The following were the files that needed to be backed up:
%ProgramFiles%\Prism\ECMLogsPersistence\src\config\default.yaml
%ProgramFiles%\Sisense\PrismWeb\SisenseStorage\config\default.yaml
See the following:
Backing Up Sisense

Sisense V7.2

You need to back upseveral directories.
These directories include:
%ProgramData%\Sisense\PrismWeb\Repository
%ProgramData%\Sisense\Infra

See the following:
Backing Up Sisense

Logs

Pre-Sisense V7.2

The location of Application log files was: %ProgramFiles%\Sisense\PrismWeb\vnext\iisnode

Sisense V7.2

The location of Application log files was moved to: %ProgramFiles%\Sisense\application-logs

SSL

Pre-Sisense V7.2

You had to configure SSL through IIS and the Sisense System Settings located in the Admin page. The SSL certificate was installed on the IIS.

See the following:
Setting Up SSL

Sisense V7.2

You can enable and configure SSL through the Configuration Manager. If you have already set up SSL in an earlier version, you must upload the SSL certificate again.

See the following: 
Setting Up SSL

Rebranding Sisense Automated Emails

Pre-Sisense V7.2

The location of Sisense's email templates was %ProgramFiles%\Sisense\PrismWeb\vnext\src\features\emails\templates.

See the following: 

Rebranding Sisense Automated Emails

Sisense V7.2

The location of the Email Templates directory has been changed from %ProgramFiles%\Sisense\PrismWeb\vnext\src\features\emails\templates to %ProgramFiles%\Sisense\app\galaxy-service\src\features\emails\templates.

Templates located in the old folder are automatically migrated to the new location when you install Sisense V7.2. For newer templates, the files should be moved to %ProgramFiles%\Sisense\PrismWeb\Resources\branding\emails.

See the following: 

Rebranding Sisense Automated Emails

FIPS

Pre-Sisense V7.2

You had to modify the configuration file, C:\Program Files\Sisense\Infra\MongoDB\mongodbconfig.conf by removing the username and password keys from your application database connection string.

See the following:
FIPS

Sisense V7.2

In the Configuration Manager, you can remove the application database user name and password values in the field Connection String.

See the following:
FIPS

GeoLocation

Pre-Sisense V7.2

The location of the GeoLocation files were located at: %ProgramFiles%\Sisense\PrismWeb

Sisense V7.2

The new location of the GeoLocation files are: %ProgramFiles%\Sisense\app\galaxy-service\src\features\geo\geoJson

High Availability Deployment

Pre-Sisense V7.2

You had to manually edit configuration files to ensure your connection string to the application database was aligned across your system.
There was no option to replicate the Configuration Database and Message Broker.

See the following: 
High Availability

Sisense V7.2

If you have implemented a high availability environment prior to Sisense V7.2, you need to set up the environment again.

See the following:
Overview
Setting Up High Availability
Replicating the Application Database
Replicating ZooKeeper
Replicating Message Broker
The Orchestrator configuration file is retained. For more information on Orchestrator configuration, see below: 
Distributing ElastiCube Builds to Query Nodes

Sisense V7.1

If you are upgrading from Sisense V7.0 or later, there are no special requirements.

If you are upgrading from a version earlier than Sisense V6.7, see the Sisense V6.7 Upgrade Guide.

If you have a high availability environment, and you want to use the web-based ElastiCube Manager, your build node must have a Sisense application server installed on it. The application server must use the system application database’s replica set.

For more information, see Supporting Web ElastiCube Manager in High Availability Environments.

Sisense V7.0

If you are upgrading from a version earlier than Sisense V6.7, see the Sisense V6.7 Upgrade Guide.

If you have a high availability environment, and you want to use the web-based ElastiCube Manager, your build node must have a Sisense application server installed on it. The application server must use the system application database’s replica set.

For more information, see Supporting Web ElastiCube Manager in High Availability Environments.