Installation Guide for Linux

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

This guide provides installation and configuration instructions for a production environment on Ubuntu 24.04.

This document describes how to install DigDash on Linux with Ubuntu 24.04.

For installation on Windows, please refer to the document Windows Installation Guide.

To update an existing installation, please refer to the document Upgrade Guide.

Supported versions

The following versions are supported:

Tomcat 10: latest patch
Java : OpenJDK 17
OpenDJ: version 4.8.0 and later
MariaDB: OS version or latest LTS version, latest patch
Nginx: system version

Digdash

OpenJDK

Java is required to run DigDash. The version to use is Java 17, 21 or 25.

# Install last version of openjdk (adapt to Java version)
sudo apt install openjdk-17-jdk

# Check installation
java -version

Tomcat 10

Installation

sudo apt install tomcat10

Creating the tree structure

# Location of webapps
sudo mkdir -p /home/digdash/webapps/default/
# Working directory
sudo mkdir -p /home/digdash/appdata/default/
# Location of the .properties file
sudo mkdir -p /etc/digdash/
# Location of logs
sudo mkdir -p /var/log/digdash/

Changing folder permissions

sudo chown -R tomcat:tomcat /home/digdash
sudo chown -R tomcat:tomcat /var/log/digdash
sudo chmod a+w /var/log/digdash

Configuring server.xml

Location: /etc/tomcat10/server.xml

Location of webapps

# Replace the appBase value
<Host name="localhost" appBase="webapps"

# by this one
<Host name="localhost" appBase="/home/digdash/webapps/default"

Valve Connector

# Complete the Connector valve
<Connector port="8080" protocol="HTTP/1.1"
              connectionTimeout="20000"
              redirectPort="8443" ></Connector>

# as follows
<Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               maxConnections="30000"
               maxParameterCount="100000"
               maxThreads="10000" maxPostSize="62914560"
             redirectPort="8443" compression="on" ></Connector>

Valve Reverse Proxy

❗In the case of SSO authentication (SAML or OpenID), the valve below must be placed before the SSO valve.

# Add this valve in the Host element near the end of the file
<Valve className="org.apache.catalina.valves.RemoteIpValve"
               internalProxies="127\.0\.[0-1]\.1"
               remoteIpHeader="X-Forwarded-For"
               requestAttributesEnabled="true"
               protocolHeader="X-Forwarded-Proto"
               protocolHeaderHttpsValue="https"></Valve>

In the case of an ipv6 server, use :

In very rare cases, reverse proxy is not installed on the machine. In this case, replace the value "127\.0\.[0-1]\.1" with the reverse proxy's ip address.
❗Please note: ".*" should only be used as a last resort.

Valve Log

# Add this valve in the Host element near the end of the file
<Valve className="org.apache.catalina.valves.ErrorReportValve" showReport="false" showServerInfo="false" ></Valve>

Limit the localhost_access_log file (optional)

To limit the size of the localhost_access_log file, add the maxDays parameter to the Access Log valve and give it the value of the number of days of your choice.

# For example
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" maxDays="10" ></Valve>

Editing the context.xml file

Location: /etc/tomcat10/context.xml

# Add the following line in the <Context> tag
<Resources cachingAllowed="true" cacheMaxSize="500000"></Resources>

Changing RAM

# Edit the following file
sudo vi /etc/default/tomcat10

# Replace the existing JAVA_OPTS by
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"

# Change the 6G parameter depending on the capacity of the machine, leaving at least 2G for the OS.
# In the example above, the machine has 8G of RAM.
# It is recommended to use the same value for Xms and Xmx.

Activating log write permission for tomcat

# Create the folder in /etc/systemd/system/
sudo mkdir -p /etc/systemd/system/tomcat10.service.d

# Create file
sudo vi /etc/systemd/system/tomcat10.service.d/logging-allow.conf

# Add the following lines
[Service]
ReadWritePaths=/var/log/digdash/ /home/digdash/

#Reload the "daemon" configuration
sudo systemctl daemon-reload

sudo systemctl restart tomcat10.service

Enabling automatic service start on startup

sudo systemctl enable tomcat10

Deployment of Digdash Version 2026 R1

Download the Digdash version

Unzip the version you just downloaded.

Properties files

Place the digdash.properties file (contained in the root of the unzipped folder) in the /etc/digdash folder.

Create the following files in the /etc/digdash folder:

Modify the digdash.properties file previously copied

# Add these lines at the beginning of the file

# Log files location
ddenterpriseapi.ddlog4j.properties.file=/etc/digdash/log4j2_api.properties
studio.ddlog4j.properties.file=/etc/digdash/log4j2_studio.properties
digdash_dashboard.ddlog4j.properties.file=/etc/digdash/log4j2_dash.properties

# Appadata location
ddenterpriseapi.AppDataPath=/home/digdash/appdata/default
digdash_dashboard.AppDataPath=/home/digdash/appdata/default
studio.AppDataPath=/home/digdash/appdata/default
adswrapper.ads.instance.name=/home/digdash/appdata/default/ldapdigdash

adminconsole.adminconsole_domain=adminconsole
adminconsole.webstudio_domain=studio
adminconsole.server_domain_list=ddenterpriseapi
adminconsole.dashboard_domain=digdash_dashboard

studio.DOMAIN=ddenterpriseapi
studio.FORCEDOMAIN=true
studio.SERVERURL=http://localhost:8080
studio.FORCESERVERURL=true
studio.adminconsole_domain=adminconsole

digdash_dashboard.DOMAIN=ddenterpriseapi
digdash_dashboard.FORCEDOMAIN=true
digdash_dashboard.SERVERURL=http://localhost:8080
digdash_dashboard.FORCESERVERURL=true
digdash_dashboard.adminconsole_domain=adminconsole

# IODS scripts location
studio.iods_exe_path=path/to/IODS/scripts
ddenterpriseapi.iods_exe_path=path/to/IODS/scripts

# NodeJS export
ddenterpriseapi.DDAPIFORNODEJSURL=http://localhost:8080
ddenterpriseapi.NODEJSURL=http://localhost:4000 #Random value between 4000 and 3000 different for each environment hosted on the same Tomcat

########### Nettoyage automatique des fichiers programmé
########### Scheduled automatic file cleaning
ddenterpriseapi.startCleaner=true

########### Nettoyage des fichiers inutilisés au démarrage du serveur
########### Clean up unused files on server startup
ddenterpriseapi.cleanOnStart=false

########### Sauvegarde automatique programmée
########### Scheduled automatic backup
ddenterpriseapi.autoBackup=true
ddenterpriseapi.autoBackupKeepDays=20
digdash_dashboard.CANCHANGEPASSWORD=true

Location of war files

Place the following items (contained in the apache_tomcat/webappps directory of the unzipped folder) in the /home/digdash/webapps/default folder :

adminconsole.war
ddenterpriseapi.war
digdash_dashboard.war
studio.war
the ROOT/ folder

Configuring DigDash after installation

Launching Digdash

Restart the Tomcat service.

sudo service tomcat10 restart

Check the war deployment in the home/digdash/webapps/default installation folder.
Access DigDash at the following address http://localhost:8080/adminconsole ..
The login / password will be admin / admin.