Converting and upgrading a Container

Overview

A Decisions instance can be converted to run entirely in a container, though some items need to be migrated from the instance over to the filestorage path for the container. Alongside this, the properties from the Settings.xml must be turned into environment variables. This article will provide a brief overview of the needed items that will have to be migrated over to the container.

Migrating from a VM to a Container

To start, the properties from the Settings.xml need to be converted into environment variables. To convert the properties of the settings.xml, please refer to the following article: Docker Container Configuration. These same steps will be used to upgrade a container from version 7 as well.

In addition, the following items will need to be migrated over into the file storage path of the container. The path to locate these items have been included below:

• databaseid.txt - C:\Program Files\Decisions\Decisions Server\Instances\Control\databaseid.txt
• keys.dat - C:\Program Files\Decisions\Decisions Server\Instances\Control\keys.dat
• PortalPublicKey - C:\Program Files\Decisions\Decisions Server\Instances\Control\PortalPublicKey.key.
• lessdefault folder - C:\Program Files\Decisions\Decisions Server\wwwroot\styles\lessdefault
• LogSettings.Json - C:\Program Files\Decisions\Decisions Server\LogSettings.json

To assist with organization, these files can be added to a Settings folder created on the file storage path, for example, /home/Filestorage/Settings.

Upgrading containerized instances of Decisions

When upgrading containerized instances of Decisions, the user will need to visit the Docker hub and retrieve the latest image of the Decisions container. Once retrieved, the user can apply the image to the container to have the environment upgraded. Similar steps to upgrading a Decisions environment should be followed, such as taking backups prior to upgrading the environment.