Update Guide

Last modified by Aurelie Bertrand on 2026/07/02 10:55

Introduction

⚠ ONCE YOU HAVE UPDATED TO VERSION 2026 R1, IT IS NOT POSSIBLE TO ROLL BACK TO A PREVIOUS VERSION. ⚠

This guide describes the procedure and precautions to take when updating your version of DigDash Enterprise to the new version 2026 R1.

This applies to you ONLY if you follow the best practices described in the relevant section.
If this is not the case, please reinstall the software from scratch following the installation guide Linux or Windows.

Important: Migration of custom developments (all versions)

This procedure does not cover the migration of custom developments (such as logo modifications, the addition of JSPs, user import scripts, etc.), which may be described in your internal procedures.
If any custom developments have been carried out, make a backup copy of your current installation so that you can recover and migrate all these customisations.

DigDash Enterprise installation archives are named in the following format:
digdash_enterprise_2026R1_t10.zip or digdash_enterprise_2026R1_numpatch_t10.zip (for example, digdash_enterprise_2026R1_P01_t10 .zip for patch P01)

Once extracted, the folder will be named:
digdash_enterprise_2026R1_t10 or digdash_enterprise_2026R1_numpatch_t10.

To clarify the procedure, the installation folder for the oldest version will be named install_dd_OLD and the installation folder for the most recent version will be named install_dd_NEW.
The version number can be found at the bottom of the DigDash home page (or in the version.txt file within the archive).

Supported configuration:

⚠ From version 2026 R1 onwards, Tomcat 9 is no longer supported. Only Tomcat 10 is supported.

  • Server: Tomcat 10 only (Windows and Linux: Ubuntu 24.04).
  • Server: Java 17, Java 21 and Java 25 ( Windows and Linux)

Best practices for version 2026 R1

To ensure DigDash Enterprise runs optimally, we recommend following these guidelines:

  • Use the digdash.properties file to store environment configurations.
    For more information on configuring the file, see the page Configuring the digdash.properties file.
  • Use an external database system for the DDAudit, Comments and DDDataEntry databases.
    For more information on setting up an external database system, see the section:
  • Using a separate Tomcat installation from Digdash (installation via the OS package manager).
    For more information on installing a separate Tomcat instance, see the section:
  • Using OpenDJ instead of adswrapper (adswrapper is no longer included).
    For more information on installing OpenDJ, see the section:

Updating DigDash Enterprise to version 2026 R1

This section applies to you if you are updating DigDash Enterprise from version 2024 R2 or later to version 2026 R1.
To update from a version earlier than 2024 R2, please contact DigDash at contact@digdash.com.

The JDBC drivers have been updated and some of them need to be reinstalled. Please check the following document to see which ones apply to your situation: Adding a JDBC Driver > Preconfigured drivers not included.

Update procedure

Step 1: Backing up the configuration

Perform a full backup of your configuration: LDAP entries (users, roles, authorization groups), data models, dashboards, etc.
If you have added any files to your installation (modified logos, images, CSS, added JSP files, etc.), you will need to transfer them to the new installation.
See the documentation Backup and restore.

Step 2: Shutting down the server

Shut down the DigDash server:

  • On Windows: right-click on the service, then click Stop in the Windows Services application.
  • On Linux: use the command sudo service tomcat10 stop

Step 3: Backing up and deleting old applications

Back up and then delete the files and folders in <install_dd>/webapps:

Folders:

  • adminconsole
  • ddenterpriseapi
  • digdash_dashboard
  • studio

Files:

  • adminconsole.war
  • ddenterpriseapi.war
  • digdash_dashboard.war
  • studio.war

⚠ Do not delete the ROOT folder.

Step 4: Copying the new applications

Unzip the new version of the product into a temporary location.

Navigate within this temporary folder to the webapps folder .
Copy the following files into the same folder in your installation:

  • adminconsole.war
  • ddenterpriseapi.war
  • digdash_dashboard.war
  • studio.war

The webapps folder should now contain 4 .war files and the ROOT folder.

Step 5: Retrieving the add-ons

Copy the contents of the add-ons directory to the same location in your installation.
If you have modified any files (importtools, backuptools, etc.), back them up before copying.

Step 6: Modifying the JAVA_OPTS variable

Some parameters must be added to the JAVA_OPTS variable.

On Linux

  1. Edit the following file:
sudo vi /etc/default/tomcat10
  1. Add the parameters-Dfile.encoding=UTF-8 and --add-opens=java.base/java.nio=org.apache.arrow.memory.core,ALL-UNNAMED --add-opens=java.base/sun.security.ssl=ALL-UNNAMED --add-opens=java.base/sun.security.util=ALL-UNNAMEDto the JAVA_OPTS variable to obtain the following result:
JAVA_OPTS="-Djava.awt.headless=true -Xms6G -Xmx6G -Djava.security.egd=file:/dev/urandom -Dfile.encoding=UTF-8 -DPROP_MAX_CONCURRENT_TOTAL=5000 -DPROP_MAX_CONCURRENT_CON_PER_HOST=5000 --add-opens=java.base/java.nio=org.apache.arrow.memory.core,ALL-UNNAMED --add-opens=java.base/sun.security.ssl=ALL-UNNAMED --add-opens=java.base/sun.security.util=ALL-UNNAMED"

On Windows

  1. Go to the Tomcat installation directory, then to the bin directory, and runtomcat10w.exe.
  2. Go to the Java tab.

  3. Add the parameter-Dfile.encoding=UTF-8to Java Options as follows:
    Encodage

  4. Add the parameters--add-opens=java.base/java.nio=org.apache.arrow.memory.core,ALL-UNNAMED --add-opens=java.base/sun.security.ssl=ALL-UNNAMED --add-opens=java.base/sun.security.util=ALL-UNNAMEDto the Java 9 Options.

Step 7: Restarting the server

Restart the DigDash server:

  • On Windows:right-click on the service, then clickStart in the Windows Services application.

  • On Linux: use the command sudo service tomcat10 start

and let Tomcat redeploy the new applications.

On Linux, refer to the Linux Installation Guide.
On Windows, refer to Windows Installation Guide.

Step 8: Restoring the data

If you have configured your new installation to point to your old data folder AND your old LDAP, restoration is not necessary.

If you are pointing to a new data folder, use the backup from Step 2 to restore the data files (data models, flows, dashboards, etc.).
Similarly, if you are pointing to a new LDAP folder, restore the LDAP entries (users, roles, authorisation groups),

Important: if you have made any changes to configuration files (web.xml, etc.), images or CSS files in the ddenterpriseapi and digdash_dashboard folders, you will need to copy these over.

Step 9: Clearing the browser cache

Clear your browser cache (shortcut on most browsers: Ctrl + Shift + Delete).

Step 10: Regenerating data models

💡 Regenerating data models is recommended when upgrading to a major version.

TheEVENT_REFRESHFLOW_FORCEALL event allows you to refresh all system flows (except those that are disabled) and force the regeneration of all cubes.

  • Enter the URL* in the following format in your browser to trigger this event via fireevent.
    http://localhost:8080/ddenterpriseapi/fireevent?eventid=EVENT_REFRESHFLOW_FORCEALL

    * Replace http://localhost:8080/ with the address of your DigDash environment andddenterpriseapi with your domain name.

Step 11: Resetting the default authorization groups

New permissions have been added. You must reset the permission groups provided by DigDash to ensure they are applied correctly.

⚠ If you had modified the authorisation groups, these changes will be lost.

To do this:

  1. Go to Configuration > User Management > Authorizations Groups: all permission groups are listed there.
  2. Click on the Reset default Acls Groups link.
    ➡ A confirmation message will appear.
  3. Click OK.

Step 12: Resetting the digdash_2024 and digdash_2019 themes

The digdash_2019 and digdash_2024 themes have been modified. They must therefore be reset.

To do this:

  1. From Studio, open the Styles Manager.
  2. Right-click on the digdash_2024 ordigdash_2019 theme, as appropriate, then click Reset.
  3. Click OK.

If you are using a customised digdash_2019 or digdash_2024 theme:

  1. Copy any changes or additions you have made to the stylesheet and save them separately.
  2. Reset the theme as described in the previous paragraph.
  3. Create a new custom theme using the Theme Editor. See the page Theme Editor for a detailed description.
  4. Reapply the changes/additions via the interface.
  5. Go to Configuration > Server Settings > Additional Settings > Miscellaneous to select the new custom theme as the server theme.

Behaviour changes

New features or bug fixes in 2026 R1 have led to changes in behaviour that may have an impact. It is therefore recommended that you consult the list of changes in behaviour available on the dedicated page: Behaviour changes.

Deploying a patch to a 2026 R1

This section covers updating from one version of 2026 R1 to a more recent version of 2026 R1.

We assume here that your configuration follows the recommendation to use the digdash.properties file. If this is not the case, please refer to the section Best Practices for version 2026 R1.

⚠ If your installation contains any custom developments located in the following application folders:
<install_dd>/apache-tomcat/webapps/ddenterpriseapi or<install_dd>/apache-tomcat/webapps/digdash_dashboard
, these will be lost during the update. Back them up before carrying out any other operations, so that you can restore them after the update.

The procedure for deploying a patch is now the same as for a version update. You can therefore follow the procedure detailed above.