Wiki source code of Guide de mise à jour

Last modified by Aurelie Bertrand on 2026/07/15 11:32
Show last authors
1 {{ddtoc/}}
2
3 ----
4
5 = Introduction =
6
7 (% class="box warningmessage" %)
8 (((
9 **⚠ ONCE YOU HAVE UPDATED TO VERSION 2026 R1, IT __IS NOT POSSIBLE TO __ROLL BACK TO A PREVIOUS VERSION. ⚠**
10 )))
11
12 This guide describes the procedure and precautions to take when updating your version of DigDash Enterprise to the new version 2026 R1.
13
14 This applies to you ONLY if you follow the [[best practices>>doc:||anchor="Bonnes_pratiques"]] described in the relevant section.
15 If this is not the case, please reinstall the software from scratch following the installation guide [[Linux>>doc:Digdash.deployment.installation.Ubuntu24.WebHome]] or [[Windows>>doc:Digdash.deployment.installation.install_guide_windows.WebHome]].
16
17 (% class="box warningmessage" %)
18 (((
19 **Important: Migration of custom developments (all versions)**
20 \\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.
21 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.
22 )))
23
24 DigDash Enterprise installation archives are named in the following format:
25 **digdash_enterprise_2026R1_t10.zip** or **digdash_enterprise_2026R1_numpatch_t10.zip **(for example**, digdash_enterprise_2026R1_P01_t10 **.zip for patch P01)
26
27 Once extracted, the folder will be named:
28 **digdash_enterprise_2026R1_t10 **or **digdash_enterprise_2026R1_numpatch_t10**.
29
30 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.**
31 The version number can be found at the bottom of the DigDash home page (or in the version.txt file within the archive).
32
33 **Supported configuration:**
34
35 (% class="box warningmessage" %)
36 (((
37 **⚠ From version 2026 R1** **onwards**, Tomcat 9 is no longer supported. Only Tomcat 10 is supported.
38 )))
39
40 * Server: **Tomcat 10 only** (Windows and Linux: Ubuntu 24.04).
41 * Server: **Java 17, Java 21 and Java 25 ( **Windows and Linux)
42
43 = Best practices for version 2026 R1{{id name="Bonnes_pratiques"/}}{{id name="Bonnes_pratiques"/}} =
44
45 To ensure DigDash Enterprise runs optimally, we recommend following these guidelines:
46
47 * Use the **digdash.properties** file to store environment configurations.
48 For more information on configuring the file, see the page [[Configuring the digdash.properties file>>doc:.DigDash\.properties.WebHome]].
49 * Use an external database system for the DDAudit, Comments and DDDataEntry databases.
50 For more information on setting up an external database system, see the section:
51 ** [[Installing MariaDB>>doc:Digdash.deployment.installation.install_guide_windows.WebHome||anchor="DB_windows"]] for a **Windows** production environment.
52 ** [[Installing MariaDB>>doc:Digdash.deployment.installation.Ubuntu24.WebHome||anchor="DB_ubuntu"]] for an **Ubuntu** production environment.
53 * Using a separate Tomcat installation from Digdash (installation via the OS package manager).
54 For more information on installing a separate Tomcat instance, see the section:
55 ** [[Installing Tomcat 10>>doc:Digdash.deployment.installation.install_guide_windows.WebHome||anchor="Tomcat_windows"]] for a **Windows** production environment.
56 ** [[Installing Tomcat 10>>doc:Digdash.deployment.installation.Ubuntu24.WebHome||anchor="Tomcat_ubuntu"]] for an **Ubuntu 24.04** production environment.
57 * Using OpenDJ instead of adswrapper (adswrapper is no longer included).
58 For more information on installing OpenDJ, see the section:
59 ** [[Installing OpenDJ>>doc:Digdash.deployment.installation.install_guide_windows.WebHome||anchor="OpenDJ"]] for a **Windows** production environment.
60 ** [[Installing OpenDJ>>doc:Digdash.deployment.installation.Ubuntu24.WebHome||anchor="OpenDJ"]]  for an **Ubuntu** production environment.
61
62 = Updating DigDash Enterprise to version 2026 R1{{id name="Premier_deploiement"/}} =
63
64 This section applies to you if you are updating DigDash Enterprise from version 2024 R2 or later to version 2026 R1.
65 To update from a version earlier than 2024 R2, please contact DigDash at [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)__contact@digdash.com__>>path:mailto:contact@digdash.com]](%%).
66
67 (% class="box warningmessage" %)
68 (((
69 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>>doc:Digdash.deployment.Connectivity_Database.adding_jdbc_driver.WebHome||anchor="HDriversprE9configurE9snoninclus"]].
70 )))
71
72 == Update procedure ==
73
74 === Step 1: Backing up the configuration ===
75
76 Perform a full backup of your configuration: LDAP entries (users, roles, authorization groups), data models, dashboards, etc.
77 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.
78 See the documentation [[Backup and restore>>doc:Digdash.deployment.configuration.backup_restore.WebHome]].
79
80 === Step 2: Shutting down the server{{id name="Stop_server"/}} ===
81
82 Shut down the DigDash server:
83
84 * **On Windows: **right-click on the service, then click **Stop **in the Windows **Services** application.
85 * **On Linux: **use** **the command** **##{{code language="shell"}}sudo service tomcat10 stop{{/code}}##
86
87 === Step 3: Backing up and deleting old applications ===
88
89 Back up and then delete the files and folders in **<install_dd>/webapps:**
90
91 (% border="0" style="width:563px" %)
92 |(% style="width:286px" %)(((
93 Folders:
94
95 * adminconsole
96 * ddenterpriseapi
97 * digdash_dashboard
98 * studio
99 )))|(% style="width:317px" %)(((
100 Files:
101
102 * adminconsole.war
103 * ddenterpriseapi.war
104 * digdash_dashboard.war
105 * studio.war
106 )))
107
108 (% class="box warningmessage" %)
109 (((
110 ⚠ Do not delete the **ROOT** folder.
111 )))
112
113 === Step 4: Copying the new applications ===
114
115 Unzip the new version of the product into a temporary location.
116
117 Navigate within this temporary folder to the **webapps** folder **.**
118 Copy the following files into the same folder in your installation:
119
120 * adminconsole.war
121 * ddenterpriseapi.war
122 * digdash_dashboard.war
123 * studio.war
124
125 The **webapps **folder **should **now contain 4 .war files and the **ROOT** folder.
126
127 === Step 5: Retrieving the add-ons ===
128
129 Copy the contents of the **add-ons** directory to the same location in your installation.
130 If you have modified any files (**importtools**, **backuptools**, etc.), back them up before copying.
131
132 === Step 6: Modifying the JAVA_OPTS variable{{id name="JVM"/}} ===
133
134 Some parameters must be added to the JAVA_OPTS variable.
135
136 ==== On Linux ====
137
138 1. Edit the following file:
139
140 {{code language="shell"}}
141 sudo vi /etc/default/tomcat10
142 {{/code}}
143
144 (% start="2" %)
145 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-UNNAMED**to the JAVA_OPTS variable to obtain the following result:
146
147 {{code language="shell"}}
148 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"
149 {{/code}}
150
151 ==== On Windows ====
152
153 1. Go to the Tomcat installation directory, then to the bin directory, and run**tomcat10w.exe**.
154 1. Go to the **Java** tab.
155 1. (((
156 Add the parameter**-Dfile.encoding=UTF-8**to Java Options as follows:
157 [[image:Dfile.png||alt="Encodage"]]
158 )))
159 1. (((
160 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-UNNAMED**to the Java 9 Options.
161 )))
162
163 === Step 7: Restarting the server{{id name="Start_server"/}} ===
164
165 Restart the DigDash server:
166
167 * **On Windows:**right-click on the service, then click**Start in **the Windows **Services** application.
168 * (((
169 **On Linux: use **the command## {{code language="shell"}}sudo service tomcat10 start{{/code}}##
170 )))
171
172 and let Tomcat redeploy the new applications.
173
174 On Linux, refer to the [[Linux Installation Guide>>doc:Digdash.deployment.installation.Ubuntu24.WebHome||target="_blank"]].
175 On Windows, refer to [[Windows Installation Guide>>doc:Digdash.deployment.installation.install_guide_windows.WebHome||target="_blank"]].
176
177 === Step 8: Restoring the data ===
178
179 If you have configured your new installation to point to your old data folder AND your old LDAP, restoration is not necessary.
180
181 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.).
182 Similarly, if you are pointing to a new LDAP folder, restore the LDAP entries (users, roles, authorisation groups),
183
184 (% class="box warningmessage" %)
185 (((
186 **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.
187 )))
188
189 === Step 9: Clearing the browser cache ===
190
191 Clear your browser cache (shortcut on most browsers: Ctrl + Shift + Delete).
192
193 === Step 10: Regenerating data models ===
194
195 (% class="box infomessage" %)
196 (((
197 💡 Regenerating data models is recommended when upgrading to a major version.
198 )))
199
200 The//EVENT_REFRESHFLOW_FORCEALL// event allows you to refresh all system flows (except those that are disabled) and force the regeneration of all cubes.
201
202 * Enter the URL* in the following format in your browser to trigger this event** **via fireevent.
203 __http:~/~/localhost:8080/ddenterpriseapi/fireevent?eventid=EVENT_REFRESHFLOW_FORCEALL__
204 \\* //Replace http:~/~/localhost:8080/ with //the address of your DigDash environment and//ddenterpriseapi with //your domain name.
205
206 === Step 11: Resetting the default authorization groups ===
207
208 New permissions have been added. You must reset the permission groups provided by DigDash to ensure they are applied correctly.
209
210 (% class="box warningmessage" %)
211 (((
212 ⚠ If you had modified the authorisation groups, these changes will be lost.
213 )))
214
215 To do this:
216
217 1. Go to **Configuration > User Management **> **Authorizations Groups**: all permission groups are listed there.
218 1. Click on the **Reset default Acls Groups** link.
219 ➡ A confirmation message will appear.
220 1. Click **OK**.
221
222 === Step 12: Resetting the //digdash_2024 //and //digdash_2019// themes //{{id name="thème"/}}// ===
223
224 The //digdash_2019 //and //digdash_2024 //themes have been modified. They must therefore be reset.
225
226 To do this:
227
228 1. From Studio, open the **Styles Manager**.
229 1. Right-click on the **digdash_2024** or**digdash_2019 **theme, as appropriate, then click **Reset**.
230 1. Click **OK**.
231
232 If you are using a //customised digdash_2019 //or //digdash_2024 //theme:
233
234 1. Copy any changes or additions you have made to the stylesheet and save them separately.
235 1. Reset the theme as described in the previous paragraph.
236 1. Create a new custom theme using the Theme Editor. See the page[[ Theme Editor>>doc:Digdash.user_guide.dashboard.theme_editor.WebHome]] for a detailed description.
237 1. Reapply the changes/additions via the interface.
238 1. Go to **Configuration **> **Server Settings **> **Additional Settings **> **Miscellaneous **to select the new custom theme as the server theme.
239
240 == Behaviour changes ==
241
242 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>>doc:Digdash.deployment.installation.behaviour_changes.WebHome]].
243
244 = Deploying a patch to a 2026 R1{{id name="Deploiement_patch"/}} =
245
246 This section covers updating from one version of 2026 R1 to a more recent version of 2026 R1.
247
248 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>>doc:||anchor="Bonnes_pratiques"]].
249
250 (% class="box warningmessage" %)
251 (((
252 ⚠ If your installation contains any custom developments located in the following application folders:
253 **<install_dd>/apache-tomcat/webapps/ddenterpriseapi** or**<install_dd>/apache-tomcat/webapps/digdash_dashboard**
254 , 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.
255 )))
256
257 (% class="wikigeneratedid" %)
258 The procedure for deploying a patch is now the same as for a version update. You can therefore follow the procedure detailed above.