V13 Migration

When migrating from a previous version of the DES to version 13, the following administrative steps are required.

Digital Enterprise Suite - Licensing

The license of the Digital Enterprise Suite (DES) should be updated after the deployment of the new version.

The owner of the instance will have received a new license code by email from our support. The new license enables new features such as the Insight Analyzer and the ability to transparently issue Digital Distributed Containers licenses (see the migration section for DDC licenses).

Digital Enterprise Suite - Graph Indexing

A graph re-indexing is required when migrating to version 13. Connect to the DES pod and run the command.

des-cli graph index

Digital Enterprise Suite - Place Migration

The Digital Enterprise Suite (DES) keeps places content on the file system. To provide more efficient storage option a GIT based implementation has been introduced in version 13.

A place migration is required to the GIT based places as soon as the new version is deployed.

It is recommended to do a backup before migrating places.

Migration

Place migration should be done during a maintenance window. Access to the system should be disabled (e.g. remove ingress) while migrating places.

Place migration is a 6 steps process:

  • Log into DES pod.

  • Go to DES data folder.

cd /data/des

  • Compact the file-based history to a git structure (/data/des/backup is created with the git structure temporarily). This step will take a few minutes based on the number of models and places.

des-cli place cp-git /data/des

  • Switch /data/des/backup migrated content to the repositories folder.

des-cli place migr-git /data/des

  • Restart the pod.

  • Once the pod restarted and users have validated that they still can access the places and their models, log back into the pod to clean the backup folder. Alternatively, it is possible to revert the migration.

rm -Rf /data/des/backup

Revert migration

To revert the migration, issue following DES cli command

des-cli place rv-migr-git /data/des

Once revert migration operation is done, update the preference

Restart the pod.

Digital Distributed Containers - Storage Migration - Helm Charts

When upgrading to the helm charts provided with version 13, the persistent storage attached with the Digital Distributed Containers (DDC) is now assuming that the process instances (in the /data/des/pinstances folder) are stored in a pinstances subfolder of the volume.

Additional mounts are provided for the completed instances (completed-pinstances), data stores (datastores-content), and logs (logs).

Before upgrading to the new helm charts, the persistent volume should be cloned, all its data should be move under a pinstances subfolder and this new volume should be used with the v13 helm charts.

Digital Distributed Containers - Licensing

Starting with version 13, Digital Distributed Containers (DDC) generated from the Digital Enterprise Suite (DES) are licensed with a transparent licensing mechanism.

This means that any new DDC generated from the DES starting at version 13 (if the license of the DES was updated properly) will not require a LICENSE environment variable in the POD at runtime.

This applies only for new DDC generated from version 13. Any DDC generated prior still require the LICENSE environment variable to be set at runtime.

If the DDC was deployed using the helm charts provided by Trisotech,

helm upgrade --reuse-values --set ddc.LICENSE=null --wait --namespace=des  --atomic  <DDC_NAME> ddc-<VERSION>.tgz

If the DDC was deployed using your own deployment descriptor, make sure that the LICENSE environment variable is not set anymore.

If a version 13 container runs with the LICENSE environment variable set, the DDC will prioritize that license which can expire.