Upgrading Decisions (v7 to v9)

Overview

Upgrading directly from version 7 to version 9 is not recommended. Instead, upgrade to version 8 first and then upgrade to version 9.

The rest of this article provides instructions for upgrading from Version 7 to 8 and troubleshooting potential upgrading issues.

Backing up the Previous Installation

It is highly recommended to back up the v7 installation and its affiliated database before upgrading.

While it cannot be used as a substitute for v8's Settings.xml, the v7 Settings.xml is a valuable reference to ensure the necessary variable match when upgrading.

1. Back up the Database noting the DB Server and DB name (or Connection String).
2. Navigate to C:\Program Files\Decisions\Decisions Server, and copy and paste the Settings.xml file into the desired location. 
3. Navigate to C:\Program Files\Decisions\Decisions Server\Instances\Control.
4. Copy and paste the Keys.dat file to the desired location.
5. Navigate to C:\Program Files\Decisions\FileStorage.
6. Back up the FileStorage Folder and reference the v7 Settings.xml file, copied above, to re-configure the exact path later in the v8 Installer.
   
   

Downloads, Selecting Installation Type, and Database Setup

1. Fulfill all v8 Prerequisites before beginning installation.
2. Download the Decisions 8 Installer from Download Decisions webpage. 
3. Right-click the installer, then select Run as Administrator. 
4. From the Decisions Installer, enable Change Settings on Update, then click UPDATE. 
5. Review the terms, check the I accept the terms of the License Agreement box, and then click Next to proceed.
6. For the installation type, select the desired server type. This example chooses a Standard server. Select Next to continue.
7. Upon reaching the Settings screen, click Next.
8. On the Database Setup screen, select the appropriate Database Type, and match the Connection Type and Connection Settings for the new v8 database. Click Next. 
9. If upgrading a clustered environment, the installer will prompt users to enter the Redis Base URL. Enter the Redis Base URL for the clustered environment. For more information, refer to Setting Up Redis External Caching.
   
10. Continue past the Full-Text Warning screen.

Portal Base URL

Set up the Portal Base URL based on the chosen Hosting Option. It is recommended to maintain the same URL in the prior version if possible.

To ensure previously emailed v7 task links resolve correctly, reference the v7 Settings.xml file to configure the matching values during the v8 installation.

Email Server, Encryption Keys, and File Storage,

1. Select the Outbound E-mail Server option previously used in v7, then click Next.
2. If database encryption was used, click Restore Key File to upload the copied v7 Keys.dat, then click Next.
3. Define a new v8File Storage location or select the original one. Then, click Next.
4. This ends any upgrade-specific changes from the standard installation. Proceed with the installation as detailed in the Installation Guide.
   
   

Manually edited .LESS Conflicts

Direct edits to the custom .less files made outside the Theme Editor may cause errors in the Portal UI.

Upgrading from v7 automatically overrides the .less files, but a conflict file is generated once this error occurs. The conflict file contains the old .less file's information.

To resolve this issue:

1. Open the provided conflict file named e.g. "theme.portal.less.conflict" found in the same folder as the .less files.
2. Open the .less file associated with the conflict file. Matching the example above, this would be the "theme.portal.less" file.
3. Replace each changed value in the .less file with the value shown in the conflict file.
   
4. Restart the Decisions server to apply changes. 

Upgrading Multiple Servers 

It is recommended to update servers in the following order:

• Development Server
• Repository and Test
• Production

Once Development has been upgraded, projects cannot be deployed to Repository or Test servers until they have been upgraded. It is possible to upgrade Development, Repository, and Test at the same time. Deploying to Production is also blocked until it has been upgraded.