Wiki source code of Sauvegarde et restauration
Last modified by Aurelie Bertrand on 2025/02/07 10:18
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{ddtoc/}} |
| 2 | |||
| 3 | ---- | ||
| 4 | |||
| |
48.1 | 5 | = MANUAL BACKUP / RESTORATION = |
| |
1.1 | 6 | |
| |
48.1 | 7 | [[Edit>>url:http://rack-lure:8585/bin/edit/Digdash_2019R2/deployment/configuration/backup_restore/WebHome?section=1]] |
| |
1.1 | 8 | |
| |
48.1 | 9 | If you want to install a new version of DigDash Enterprise or migrate to a new environment (transition from a test environment to a production environment, modification of the server machine, ...), you can backup and restore the data of your current environment: |
| |
1.1 | 10 | |
| |
48.1 | 11 | 1. Users, roles and use groups, |
| 12 | 1. Dashboards, | ||
| 13 | 1. Information portfolios and data models, | ||
| 14 | 1. Images, data dictionaries (translations, formats, connections, color palettes ...), etc. | ||
| 15 | 1. Data sources: Data sources in the UserDocs user data directory can be saved. | ||
| |
1.1 | 16 | |
| |
48.1 | 17 | First select the items you want to save. This creates a zip file which you must then restore to the new environment or the new version. |
| |
1.1 | 18 | |
| |
48.1 | 19 | Please note that the files in the DigDash Enterprise installation directory are not saved or restored by our tool, so you must copy them manually if you have made any changes: |
| |
1.1 | 20 | |
| |
48.1 | 21 | 1. dashboard styles: if you have modified the dashboard styles from the dashboard.css file in the webapps / digdash_dashboard directory, this must be manually copied to the new environment.((( |
| 22 | (% class="box infomessage" %) | ||
| 23 | ((( | ||
| 24 | Note: we recommend modifying the styles of the dashboard from the CSS editor of the dashboard. This creates a default.css file in the user data directory. This file can be saved and then restored by DigDash Enterprise. | ||
| 25 | ))) | ||
| 26 | ))) | ||
| 27 | 1. images, logos and icons: if you have modified the files located in the webapps / digdash_dashboard / icons directory, you will have to copy them to re-apply them on your new version. | ||
| |
1.1 | 28 | |
| |
48.1 | 29 | == Save data == |
| |
37.1 | 30 | |
| |
48.1 | 31 | [[Edit>>url:http://rack-lure:8585/bin/edit/Digdash_2019R2/deployment/configuration/backup_restore/WebHome?section=2]] |
| |
24.3 | 32 | |
| |
48.1 | 33 | 1. Display the home page: |
| |
29.2 | 34 | |
| |
48.1 | 35 | Start the Internet browser of your choice, then type the URL http: ~/~/ ServerName: Server Port (example: [[http: ~~/~~/ localhost: 8080>>url:http://localhost:8080/]] ). The DigDash Enterprise home page appears. |
| |
24.3 | 36 | |
| |
48.1 | 37 | 1. Click on the **Configuration ** link then **Backup management** . Click on **Save ** to save your current configuration |
| 38 | 1. In the login box, enter the user name and password | ||
| 39 | 1. Check in each section the items you want to save: //See the definition of each item in the appendix// . | ||
| 40 | 1. Click on **Generate** then on **Download the restoration file ** to obtain the backup file (.zip file) | ||
| 41 | |||
| |
19.1 | 42 | (% class="box infomessage" %) |
| 43 | ((( | ||
| |
48.1 | 44 | Note: The backup format changed in November 2015 (version 2015B1124). If you want to save for a version before this date, check the **Generate for a version before 2015B1124** check box . |
| |
19.1 | 45 | ))) |
| 46 | |||
| |
48.1 | 47 | == Restore data == |
| |
1.1 | 48 | |
| |
48.1 | 49 | [[Edit>>url:http://rack-lure:8585/bin/edit/Digdash_2019R2/deployment/configuration/backup_restore/WebHome?section=3]] |
| |
29.2 | 50 | |
| |
48.1 | 51 | 1. Display the home page: |
| |
27.1 | 52 | |
| |
48.1 | 53 | Start the Internet browser of your choice, then type the URL http: ~/~/ ServerName: Server Port (example: [[http: ~~/~~/ localhost: 8080>>url:http://localhost:8080/]] ). The DigDash Enterprise home page appears. |
| |
27.1 | 54 | |
| |
48.1 | 55 | 1. Click on the **Configuration ** link then **Backup management** . Click **Restore ** to restore a configuration. |
| 56 | 1. Click on **Browse ** to select the zip file corresponding to your backup then click on **Load** | ||
| 57 | 1. The list of database connections present in the backup file is displayed so that you can update them if necessary. | ||
| |
27.1 | 58 | |
| |
48.1 | 59 | __Migration of connections and document servers:__ |
| |
27.1 | 60 | |
| |
48.1 | 61 | In order to facilitate the migration of these elements, it is possible to modify their identifiers so that they are identical between the development and production servers. |
| |
27.1 | 62 | |
| |
48.1 | 63 | During the first migration between a development server and a production server: |
| |
27.1 | 64 | |
| |
48.1 | 65 | 1. Perform a full backup of the development environment |
| 66 | 1. Restore the backup to the production environment | ||
| 67 | 1. Modify connection strings to databases and file servers on the production environment (from the connection manager and the document server manager in Enterprise Studio). | ||
| |
27.1 | 68 | |
| |
48.1 | 69 | During the following migrations to production environments: |
| |
27.1 | 70 | |
| |
48.1 | 71 | * Selectively backup data: data models, portfolios, modified or new dashboards, ... |
| |
27.1 | 72 | |
| |
48.1 | 73 | Do not save the file containing the connections (dbcnxrepository.xml) as well as the file containing the document servers (serverurlrepository.xml) even if these contain modifications |
| |
27.1 | 74 | |
| |
48.1 | 75 | 1. Restore the backup to the production environment |
| 76 | 1. If changes have been made to connections or file servers in the development environment, post them manually to the production environment. | ||
| |
27.1 | 77 | |
| |
48.1 | 78 | For new connections or new document servers, report the identifier used on the development environment. |
| |
27.1 | 79 | |
| |
48.1 | 80 | To report the connection identifier, open the connection managers ( **Tools** menu **\ database connections manager ** in Enterprise Studio). Edit the connection to modify then click on **Edit ** to modify the identifier: |
| |
27.1 | 81 | |
| |
48.1 | 82 | To report the identifier of a document server, open the connection managers ( **Tools** menu **\ document servers manager ** in Enterprise Studio). Edit the document server to modify, then click **Edit ** to modify the identifier: |
| |
27.1 | 83 | |
| |
48.1 | 84 | = AUTOMATION = |
| |
27.1 | 85 | |
| |
48.1 | 86 | [[Edit>>url:http://rack-lure:8585/bin/edit/Digdash_2019R2/deployment/configuration/backup_restore/WebHome?section=4]] |
| |
27.1 | 87 | |
| |
48.1 | 88 | You can automatically backup your environment. For this, DigDash Enterprise provides a backuptools.jar backup tool to run on the server. |
| |
27.1 | 89 | |
| |
48.1 | 90 | This jar file is located in the <tomcat webapps> / ddenterpriseapi / WEB-INF / lib directory and must be used from this location (because it uses other jar files located in the same directory). |
| |
27.1 | 91 | |
| |
48.1 | 92 | The options are: |
| |
27.1 | 93 | |
| |
48.1 | 94 | 1. -url server_url: DigDash Enterprise server URL (default [[http: ~~/~~/ localhost: 8080>>url:http://localhost:8080/]] ) |
| 95 | 1. -domain dd_domain: domain name of the DigDash Enterprise application (by default ddenterpriseapi) | ||
| 96 | 1. -login user_login: DigDash Enterprise administrator login | ||
| 97 | 1. -pass user_pass: DigDash Enterprise administrator password | ||
| 98 | -export or -backup: save the DigDash Enterprise configuration in a zip file | ||
| 99 | 1. -import or -restore: restore the configuration of DigDash Enterprise from a zip file | ||
| 100 | 1. -file zipfile: path of the backup file to restore | ||
| 101 | 1. -ldap: backup or restore of the LDAP directory | ||
| 102 | 1. -noldap: no backup or restore of the LDAP directory | ||
| 103 | 1. -help: display help | ||
| 104 | 1. -debug: display error messages | ||
| 105 | |||
| |
27.1 | 106 | |
| |
48.1 | 107 | __Examples of use:__ |
| |
27.1 | 108 | |
| |
48.1 | 109 | java - jar backuptools . jar - admin login - admin pass - export - noldap |
| 110 | java - jar backuptools . jar - url http : ~/~/ localhost: 8080 -domain ddenterpriseapi -login admin -pass admin -export -ldap -file C: ~\~\ backup.zip | ||
| 111 | java - jar backuptools . jar - url http : ~/~/ localhost: 8080 -domain ddenterpriseapi -login admin -pass admin -import -ldap -file C: ~\~\ backup.zip | ||
| |
27.1 | 112 | |
| |
48.1 | 113 | If you make a backup of your environment a backup file is created. This file has the name datedujour_backup.zip (for example 20141219_backup.zip if the backup was performed on December 19, 2014) and is located in the directory containing the DigDash Enterprise data (By default, **Application Data / Enterprise Server / <domain> / config** .) |
| |
27.1 | 114 | |
| |
48.1 | 115 | DigDash Enterprise also provides a file “backup_export.bat” (interactive file with prompts) allowing you to save your environment: |
| |
27.1 | 116 | |
| |
48.1 | 117 | 1. This file is located in the DigDash Enterprise installation directory. When executing the file, you must indicate: |
| 118 | 1. the URL of your server: by default, [[http: ~~/~~/ localhost: 8080>>url:http://localhost:8080/]] | ||
| 119 | 1. the DigDash Enterprise domain: by default, ddenterpriseapi | ||
| 120 | 1. user login: by default, admin | ||
| 121 | 1. the user's password: by default, admin | ||
| 122 | 1. whether or not to save the LDAP dictionary (users and roles): enter **y** to save and **n** not to save. | ||
| |
27.1 | 123 | |
| |
48.1 | 124 | A backup file is created. This file has the name <datedujour> _backup.zip (for example 20130710_backup.zip if the backup was performed on July 10, 2013) and is located in a directory containing the DigDash Enterprise data. By default, **Application Data / Enterprise Server / <domain> / config** . |
| |
27.1 | 125 | |
| |
48.1 | 126 | For example on Windows 7: |
| |
27.1 | 127 | |
| |
48.1 | 128 | **C: \ Users \ <user> \ AppData \ Roaming \ Enterprise Server \ ddenterpriseapi \ config** |
| |
29.1 | 129 | |
| |
48.1 | 130 | To restore a backup automatically, you can also use the backup_import.bat file. You must enter the same parameters as for backup_export (instead of indicating if you want to save the LDAP directory, indicate if you want to restore it). Also specify the name of the backup file (by default, it must be in the directory where the backup_import.bat file is included). |
| |
1.1 | 131 | |
| |
48.1 | 132 | = APPENDIX - LIST OF ELEMENTS OF A BACKUP = |
| |
1.1 | 133 | |
| |
48.1 | 134 | [[Edit>>url:http://rack-lure:8585/bin/edit/Digdash_2019R2/deployment/configuration/backup_restore/WebHome?section=5]] |
| 135 | |||
| 136 | Here is the list of elements that can be saved / restored as well as their description. | ||
| 137 | |||
| 138 | When the element corresponds to a file, it is located in the data directory of the DigDash domain. For example: <AppData> / Enterprise Server / ddenterpriseapi. The file paths mentioned below are relative to this directory. | ||
| 139 | |||
| 140 | |**Element**|**Description** | ||
| |
1.1 | 141 | |(% colspan="2" %)((( |
| |
48.1 | 142 | __Users__ |
| |
1.1 | 143 | |
| |
48.1 | 144 | Data relating to each user. |
| |
1.1 | 145 | ))) |
| |
48.1 | 146 | |LDAP|User information stored in LDAP:((( |
| 147 | * User attributes (name, username, password, variables ...) | ||
| 148 | * User roles | ||
| 149 | * User permissions and permission groups | ||
| |
1.1 | 150 | ))) |
| |
48.1 | 151 | |Wallets|((( |
| 152 | Information portfolio and user flow | ||
| |
1.1 | 153 | |
| |
48.1 | 154 | File: /server/<user>/config/wallet.iwt |
| |
1.1 | 155 | ))) |
| |
48.1 | 156 | |Dashboards|((( |
| 157 | User dashboards | ||
| |
1.1 | 158 | |
| |
48.1 | 159 | File: /server/<user>/config/dashboard.xml |
| |
1.1 | 160 | ))) |
| |
48.1 | 161 | |Data models|((( |
| 162 | User data models | ||
| |
1.1 | 163 | |
| |
48.1 | 164 | File: /server/<user>/config/tabledatamodelrepository.xml |
| |
1.1 | 165 | ))) |
| |
48.1 | 166 | |Passwords|((( |
| 167 | User passwords | ||
| |
1.1 | 168 | |
| |
48.1 | 169 | File: /server/<user>/config/passwordrepository.xml |
| |
1.1 | 170 | ))) |
| 171 | |(% colspan="2" %)((( | ||
| |
48.1 | 172 | __Roles__ |
| |
35.2 | 173 | |
| |
48.1 | 174 | Data relating to each role. |
| |
35.2 | 175 | ))) |
| |
48.1 | 176 | |LDAP|Role information stored in LDAP:((( |
| 177 | * Role attributes (name, identifier) | ||
| 178 | * role users | ||
| |
1.1 | 179 | ))) |
| |
48.1 | 180 | |Wallets|((( |
| 181 | Information portfolio and role flow | ||
| |
1.1 | 182 | |
| |
48.1 | 183 | File: /config/wallet_<Id_Role>.xml |
| |
1.1 | 184 | ))) |
| |
48.1 | 185 | |Dashboards|((( |
| 186 | Role dashboards | ||
| |
1.1 | 187 | |
| |
48.1 | 188 | File: /config/dashboard_<Id_Role>.xml |
| |
1.1 | 189 | ))) |
| |
48.1 | 190 | |Data models|((( |
| 191 | Role data models | ||
| |
1.1 | 192 | |
| |
48.1 | 193 | File: /config/tabledatamodelrepository_<Id_Role>.xml |
| |
1.1 | 194 | ))) |
| |
48.1 | 195 | |Passwords|((( |
| 196 | Role passwords | ||
| |
1.1 | 197 | |
| |
48.1 | 198 | File: /config/passwordrepository_<Id_Role>.xml |
| |
1.1 | 199 | ))) |
| 200 | |(% colspan="2" %)((( | ||
| |
48.1 | 201 | __Authorization groups__ |
| |
1.1 | 202 | |
| |
48.1 | 203 | Definition of authorization groups provided by DigDash or added by the user. Authorization groups are only stored in LDAP. |
| |
1.1 | 204 | ))) |
| |
48.1 | 205 | |<Name of authorization group>|Definition of the authorization group:((( |
| 206 | * List of group unit authorizations | ||
| |
1.1 | 207 | ))) |
| 208 | |(% colspan="2" %)((( | ||
| |
48.1 | 209 | __Server common files__ |
| |
1.1 | 210 | |
| |
48.1 | 211 | List of files common to all users and roles. |
| |
1.1 | 212 | ))) |
| |
48.1 | 213 | |(% colspan="2" %)__Server common files / System files__ |
| |
1.1 | 214 | |serversettings.xml|((( |
| |
48.1 | 215 | DigDash Enterprise server settings: |
| |
1.1 | 216 | |
| |
48.1 | 217 | * HTTP proxy |
| 218 | * LDAP connection | ||
| 219 | * Scheduler parameters | ||
| 220 | * Performance settings | ||
| 221 | * And all the parameters of the server configuration page | ||
| |
1.1 | 222 | |
| |
48.1 | 223 | File: /config/serversettings.xml |
| |
1.1 | 224 | |
| |
48.1 | 225 | Recommendations: Do not carry this file between several different configurations |
| |
1.1 | 226 | ))) |
| 227 | |system.xml|((( | ||
| |
48.1 | 228 | System information and certain hidden parameters described in the document [[**guide_avance_systeme**>>doc:Digdash.deployment.configuration.advanced_system_guide.WebHome]] |
| |
1.1 | 229 | |
| |
48.1 | 230 | File: /config/system.xml |
| |
1.1 | 231 | |
| |
48.1 | 232 | Recommendations: Do not carry this file between several different configurations |
| |
1.1 | 233 | ))) |
| 234 | |userssettings.xml|((( | ||
| |
48.1 | 235 | User settings including the settings you have created. |
| |
1.1 | 236 | |
| |
48.1 | 237 | File: /config/userssettings.xml |
| |
1.1 | 238 | ))) |
| 239 | |(% colspan="2" %)((( | ||
| 240 | |||
| 241 | |||
| |
48.1 | 242 | __Server common files / Dictionaries__ |
| |
1.1 | 243 | |
| |
48.1 | 244 | Settings common to all users and roles. These files may or may not be present depending on the parameters used by the flows or the data models. |
| |
1.1 | 245 | ))) |
| 246 | |colortablerepository.xml|((( | ||
| |
48.1 | 247 | Dictionary of color palettes |
| |
1.1 | 248 | |
| |
48.1 | 249 | Scope: {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} configuration |
| |
1.1 | 250 | |
| |
48.1 | 251 | File: /config/colortablerepository.xml |
| |
1.1 | 252 | ))) |
| 253 | |cssrepository.xml|((( | ||
| |
48.1 | 254 | Dictionary of CSS styles |
| |
1.1 | 255 | |
| |
48.1 | 256 | Scope: {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} configuration |
| |
1.1 | 257 | |
| |
48.1 | 258 | File: /config/cssrepository.xml |
| |
1.1 | 259 | ))) |
| |
48.1 | 260 | |clustersettings.xml|((( |
| 261 | Configuration of cluster mode (advanced) | ||
| |
1.1 | 262 | |
| |
48.1 | 263 | Scope: System configuration |
| |
1.1 | 264 | |
| |
48.1 | 265 | File: /config/clustersettings.xml |
| |
1.1 | 266 | ))) |
| |
48.1 | 267 | |DDComments.h2.db|((( |
| 268 | Database of comments on dashboard data streams and models. | ||
| |
35.2 | 269 | |
| |
48.1 | 270 | Scope: Display of dashboards and flows |
| |
35.2 | 271 | |
| |
48.1 | 272 | File: /config/DDComments.h2.db |
| |
35.2 | 273 | ))) |
| 274 | |dbcnxrepository.xml|((( | ||
| |
48.1 | 275 | Dictionary of database connections (advanced) |
| |
35.2 | 276 | |
| |
48.1 | 277 | Scope: Configuration of data models (connections to data sources) |
| |
35.2 | 278 | |
| |
48.1 | 279 | File: /config/dbcnxrepository.xml |
| |
35.2 | 280 | ))) |
| |
1.1 | 281 | |favoritedevicesrepository.xml|((( |
| |
48.1 | 282 | Dictionary of devices used for synchronizing flows |
| |
1.1 | 283 | |
| |
48.1 | 284 | Scope: Export of flows |
| |
1.1 | 285 | |
| |
48.1 | 286 | File: /config/favoritedevicesrepository.xml |
| |
1.1 | 287 | ))) |
| 288 | |flowsnapshotrepository.xml|((( | ||
| |
48.1 | 289 | Dictionary of user views of flows used in BI self-service |
| |
1.1 | 290 | |
| |
48.1 | 291 | Scope: Display of flows (editable in the dashboard) |
| |
1.1 | 292 | |
| |
48.1 | 293 | File: /config/flowsnapshotrepository.xml |
| |
1.1 | 294 | ))) |
| 295 | |formatrepository.xml|((( | ||
| |
48.1 | 296 | Dictionary of number and date formats |
| |
1.1 | 297 | |
| |
48.1 | 298 | Scope: Configuration of data models and flows |
| |
1.1 | 299 | |
| |
48.1 | 300 | File: /config/formatrepository.xml |
| |
1.1 | 301 | ))) |
| |
48.1 | 302 | |jsfunctionrepository.xml|((( |
| 303 | Dictionary of javascript functions used in derived measurements, filters, source transformations… | ||
| |
1.1 | 304 | |
| |
48.1 | 305 | Scope: Configuration of data models and flows |
| |
1.1 | 306 | |
| |
48.1 | 307 | File: /config/jsfunctionrepository.xml |
| |
1.1 | 308 | ))) |
| 309 | |hierarchyrepository.xml|((( | ||
| |
48.1 | 310 | Dictionary of shared hierarchies used by data model dimensions |
| |
1.1 | 311 | |
| |
48.1 | 312 | Scope: Configuration of data models |
| |
1.1 | 313 | |
| |
48.1 | 314 | File: /config/hierarchyrepository.xml |
| |
1.1 | 315 | ))) |
| |
48.1 | 316 | |navigationsentencerepository.xml|((( |
| 317 | Dictionary of phrases created for video and text navigation of text streams | ||
| |
1.1 | 318 | |
| |
48.1 | 319 | Scope: {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} configuration |
| |
35.3 | 320 | |
| |
48.1 | 321 | File: /config/navigationsentencerepository.xml |
| |
35.3 | 322 | ))) |
| |
48.1 | 323 | |passwordrepository.xml|((( |
| 324 | Dictionary of global passwords. (Deprecated) | ||
| |
35.3 | 325 | |
| |
48.1 | 326 | File: /config/passwordrepository.xml |
| |
1.1 | 327 | ))) |
| 328 | |serverurlrepository.xml|((( | ||
| |
48.1 | 329 | Dictionary of document servers used in DigDash Enterprise |
| |
1.1 | 330 | |
| |
48.1 | 331 | Scope: Configuration of data models |
| |
1.1 | 332 | |
| |
48.1 | 333 | File: /config/serverurlrepository.xml |
| |
1.1 | 334 | ))) |
| 335 | |vectoriconrepository.xml|((( | ||
| |
48.1 | 336 | Dictionary of vector icons used by "Infographic" graphics |
| |
1.1 | 337 | |
| |
48.1 | 338 | Scope: {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} configuration |
| |
1.1 | 339 | |
| |
48.1 | 340 | File: /config/vectoriconrepository.xml |
| |
1.1 | 341 | ))) |
| 342 | |vizmodelrepository.xml|((( | ||
| |
48.1 | 343 | Dictionary of shared presentation models associated with flows. |
| |
1.1 | 344 | |
| |
48.1 | 345 | Scope: {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} configuration |
| |
1.1 | 346 | |
| |
48.1 | 347 | File: /config/vizmodelrepository.xml |
| |
1.1 | 348 | ))) |
| 349 | |(% colspan="2" %)((( | ||
| |
48.1 | 350 | __Server common files / Translation files__ |
| |
1.1 | 351 | |
| |
48.1 | 352 | Translation dictionaries group messages in different languages. |
| |
1.1 | 353 | |
| |
48.1 | 354 | Each following translation file can be accompanied by a file corresponding to the chosen language. For example, the files **dm.properties, dm_fr.properties, dm_es.properties** are the translations of messages corresponding to the English language (default), French and Spanish. |
| |
1.1 | 355 | ))) |
| 356 | |dashboard.properties|((( | ||
| |
48.1 | 357 | Dictionary of translations used in the elements specific to the dashboard: |
| |
1.1 | 358 | |
| |
48.1 | 359 | * Name of pages |
| 360 | * Portlet name | ||
| |
1.1 | 361 | |
| |
48.1 | 362 | File: /config/dashboard.properties |
| |
1.1 | 363 | |
| 364 | /config/dashboard_<lang>.properties | ||
| 365 | ))) | ||
| 366 | |dm.properties|((( | ||
| |
48.1 | 367 | Translation dictionaries used in data models and flows. |
| |
1.1 | 368 | |
| |
48.1 | 369 | Scope: Display of data model elements and streams |
| |
1.1 | 370 | |
| |
48.1 | 371 | Files: /config/dm.properties, |
| |
1.1 | 372 | |
| 373 | /config/dm_<lang>.properties | ||
| 374 | ))) | ||
| |
48.1 | 375 | |dmvoc.properties|((( |
| 376 | Dictionary of spoken values for expressions of data models. | ||
| |
35.6 | 377 | |
| |
48.1 | 378 | Scope: Export video stream (optional) |
| |
35.6 | 379 | |
| |
48.1 | 380 | Files: /config/dmvoc.properties, |
| |
35.6 | 381 | |
| |
48.1 | 382 | /config/dmvoc_<lang>.properties |
| |
35.6 | 383 | ))) |
| |
48.1 | 384 | |dmtag.properties|((( |
| 385 | Dictionary of synonyms created in data models. These dictionaries are used by the search function of the dashboard: query in natural language. | ||
| |
35.6 | 386 | |
| |
48.1 | 387 | Scope: Text search in the dashboard |
| |
35.6 | 388 | |
| |
48.1 | 389 | Files: /config/dmtag.properties, |
| |
35.6 | 390 | |
| |
48.1 | 391 | /config/dmtag_<lang>.properties |
| |
35.6 | 392 | ))) |
| 393 | |((( | ||
| |
48.1 | 394 | <domain> .properties dashboard |
| |
35.6 | 395 | |
| |
48.1 | 396 | //(Deprecated)// |
| |
35.6 | 397 | )))|((( |
| |
48.1 | 398 | Dictionary of dashboard elements (name of pages,…). |
| |
1.1 | 399 | |
| |
48.1 | 400 | //These files are deprecated and do not have to be backed up / restored// |
| |
1.1 | 401 | ))) |
| 402 | |(% colspan="2" %)((( | ||
| |
48.1 | 403 | __Server common files / Others__ |
| |
1.1 | 404 | |
| |
48.1 | 405 | Other files related to the configuration of dashboards. |
| |
1.1 | 406 | ))) |
| 407 | |((( | ||
| |
48.1 | 408 | Pictures |
| |
1.1 | 409 | |
| |
48.1 | 410 | (* .png, * .jpg, * .gif ...) |
| |
1.1 | 411 | )))|((( |
| |
48.1 | 412 | List of images added from the dashboard editor. |
| |
1.1 | 413 | |
| |
48.1 | 414 | Folder: / config / web / public /, / config / web / public / <Id_Role> /, / config / web / public / <user> / |
| |
1.1 | 415 | ))) |
| 416 | |((( | ||
| 417 | Styles | ||
| 418 | |||
| 419 | default.css | ||
| 420 | |||
| |
48.1 | 421 | ~* .css |
| |
1.1 | 422 | )))|((( |
| |
48.1 | 423 | Files containing the custom styles of the dashboard. CSS style sheets can be edited in the dashboard editing interface. |
| |
1.1 | 424 | |
| |
48.1 | 425 | File: /config/web/public/default.css, |
| |
1.1 | 426 | |
| 427 | /config/web/public/*.css | ||
| 428 | ))) | ||
| 429 | |js-const.js|((( | ||
| |
48.1 | 430 | Constants of the DigDash Enterprise server (properties listed on the "Server configuration> Advanced" page, "Constants" section) + export parameters ("Export options" section) |
| |
1.1 | 431 | |
| |
48.1 | 432 | File: /config/web/session/js-const.js, |
| |
1.1 | 433 | ))) |
| 434 | |js-default.js|((( | ||
| |
48.1 | 435 | Dashboard custom script file. This file can be directly edited from the dashboard editing interface. |
| |
1.1 | 436 | |
| |
48.1 | 437 | File: /config/web/session/js-default.js |
| |
1.1 | 438 | ))) |
| 439 | |(% colspan="2" %)((( | ||
| |
48.1 | 440 | __Server common files / Data sources__ |
| |
1.1 | 441 | |
| |
48.1 | 442 | Data sources in the UserDocs file server. The files contained in this server can be integrated into the backup |
| |
1.1 | 443 | ))) |