Wiki source code of État du serveur
Last modified by Aurelie Bertrand on 2025/12/19 08:51
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
23.1 | 1 | {{ddtoc/}} |
| 2 | |||
| 3 | ---- | ||
| 4 | |||
| |
73.1 | 5 | This page is used to monitor the status of the server and activate a set of services. |
| |
7.2 | 6 | |
| |
73.1 | 7 | [[image:Server_status_EN.png||alt="Server status"]] |
| |
70.1 | 8 | |
| |
73.1 | 9 | = General status = |
| |
7.2 | 10 | |
| |
73.1 | 11 | This section is mainly used to view system information (versions installed, memory, etc) and download server logs. |
| |
7.2 | 12 | |
| |
73.1 | 13 | |=(% scope="row" style="width: 370px;" %)Memory (occupied/max)|(% style="width:795px" %)((( |
| 14 | Displays occupied and available memory. | ||
| 15 | Click on the [[image:1710249675342-408.png]] button reclaims memory space using the garbage collector. This allows you to manage memory, in particular by freeing memory for objects that are no longer in use. | ||
| |
40.1 | 16 | ))) |
| |
7.2 | 17 | |=(% style="width: 370px;" %)((( |
| |
73.1 | 18 | Memory overview |
| |
7.2 | 19 | |
| 20 | [[image:1710250381866-493.png]] | ||
| 21 | )))|(% style="width:795px" %)((( | ||
| |
73.1 | 22 | Gives an overview of memory usage in the form of a progress bar: |
| |
7.2 | 23 | |
| |
73.1 | 24 | * In light blue: the actual amount of memory used |
| 25 | * In blue: the amount of memory reserved | ||
| 26 | * In white: the maximum amount that the application will be able to use | ||
| |
40.1 | 27 | |
| |
73.1 | 28 | Clicking on the preview bar displays a window listing the quotas defined. See the paragraph [[Quota management>>doc:Digdash.deployment.configuration.configuration_guide.Cluster_parameters.WebHome||anchor="quota"]] for more details. |
| |
7.2 | 29 | ))) |
| |
73.1 | 30 | |=(% style="width: 370px;" %)Work directory (AppData)|(% style="width:795px" %)((( |
| 31 | Path to the working directory. | ||
| 32 | Click on the icon [[image:1710250771783-246.png]] icon will take you to the configuration details in the digdash.properties file. | ||
| 33 | A link will take you to the [[documentation>>doc:Digdash.deployment.configuration.advanced_system_guide.other_advanced_parameters.WebHome]] for more information. | ||
| |
7.2 | 34 | |
| |
73.1 | 35 | [[image:Configuration_details_server_EN.png||alt="Configuration details"]] |
| |
7.2 | 36 | ))) |
| 37 | |||
| |
73.1 | 38 | == Download server logs == |
| |
7.2 | 39 | |
| |
73.1 | 40 | To retrieve the server logs, click on **Log level 'debug' | Current log level 'info' then __Download the log file.__** |
| |
58.1 | 41 | |
| |
73.1 | 42 | The logs are particularly useful in the event of an error in your support request. |
| |
7.3 | 43 | |
| |
73.1 | 44 | = Scheduler = |
| |
55.1 | 45 | |
| |
73.1 | 46 | This section** allows you to **start/stop the scheduler and view its information. |
| |
55.1 | 47 | |
| |
73.1 | 48 | The scheduler must be started for refresh programming to work. If it is stopped, click on [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]]. |
| 49 | The scheduler user must also be entered. | ||
| 50 | See the page [[Schedule refreshes>>doc:Digdash.user_guide.studio.Schedule_refresh.WebHome]] page for more details. | ||
| |
55.1 | 51 | |
| |
73.1 | 52 | You can check if there are any scheduled tasks to run by clicking on the [[image:1710254700486-368.png]] icon at the end of the **Last check date** line. |
| |
7.3 | 53 | |
| |
73.1 | 54 | = Maintenance service = |
| |
9.4 | 55 | |
| |
73.1 | 56 | This section** **allows you to** **start/stop the maintenance service and view information about the operations performed. |
| |
7.3 | 57 | |
| |
73.1 | 58 | The maintenance service consists of : |
| |
9.5 | 59 | |
| |
73.1 | 60 | * A file cleaner (also known as Files GC) which cleans up all unused files: old history files, cubes and other {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}}-dependent files. |
| 61 | * An automatic configuration backup | ||
| |
7.3 | 62 | |
| |
73.1 | 63 | See the [[Automatic Maintenance Service>>doc:Digdash.deployment.configuration.advanced_system_guide.Automatic_maintenance.WebHome]] page for a detailed description. |
| |
9.6 | 64 | |
| |
73.1 | 65 | To start this service, (% id="cke_bm_2197S" style="display:none" %)click (%%)on [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]] at the end of the **Maintenance Service Started** line. |
| |
9.2 | 66 | |
| |
73.1 | 67 | By default, maintenance takes place at midnight. You can start the file cleaner immediately by clicking on the icon [[image:1710254700486-368.png]] icon at the end of the **Next maintenance date** line. |
| |
9.2 | 68 | |
| |
73.1 | 69 | = Audit services = |
| |
9.2 | 70 | |
| |
73.1 | 71 | This section allows you to** **start the DigDash data audit services you wish to use (session audit service, cubes, flows, etc). |
| |
9.2 | 72 | |
| |
73.1 | 73 | Click on the [[image:https://doc.digdash.com/xwiki/wiki/dev/download/Digdash/user_guide/studio/Schedule_refresh/WebHome/1706526467080-910.png?width=16&height=18&rev=1.1||alt="1706526467080-910.png" height="18" width="16"]] icon to activate the desired audit services. |
| 74 | Pre-defined reports can be accessed directly from the **Choose an audit report **drop-down list **... **See the page [[DDAudit - Server status reports>>doc:.ddaudit_notice.WebHome]] for details of the reports. | ||
| |
51.1 | 75 | |
| |
73.1 | 76 | See the [[Deployment of the audit module>>doc:Digdash.deployment.configuration.ddaudit_module_install.WebHome]] page for details of the audit module. |
| |
9.2 | 77 | |
| |
73.1 | 78 | = Sessions = |
| |
9.2 | 79 | |
| |
73.1 | 80 | This section allows you to view general session information. |
| |
9.3 | 81 | |
| |
73.1 | 82 | You can click on the** List **link next to **Session count (Total / Scheduling) **to view details of active sessions. |
| |
9.4 | 83 | |
| |
73.1 | 84 | You can disable authentication for all users by clicking on the [[image:1710259471051-331.png]] icon on the **Activate authentication** line. This disables the server and prevents all users from connecting. |
| 85 | ❗Only (% style="color:#c0392b" %)**the super-user can connect to a disabled server.❗** | ||
| |
47.1 | 86 | |
| |
73.1 | 87 | = Refresh engine = |
| |
47.1 | 88 | |
| |
73.1 | 89 | This section allows you to view in-memory cube information and synchronisation tasks. |
| |
47.1 | 90 | |
| |
73.1 | 91 | == Cubes in memory == |
| |
9.4 | 92 | |
| |
73.1 | 93 | You can click **List** to the right of **In memory cubes and cube parts **to view details of cubes in memory |
| |
9.4 | 94 | |
| |
73.1 | 95 | [[image:Cubes_in_memory_EN.png||alt="Cubes in memory"]] |
| |
9.4 | 96 | |
| |
14.1 | 97 | (% class="wikigeneratedid" id="H" %) |
| |
73.1 | 98 | The **Attributes** column gives the following information about the cubes: |
| |
14.1 | 99 | |
| |
73.1 | 100 | * **I**: Interactive use (used by flows and dashboards) |
| 101 | * **M**: In memory only | ||
| 102 | * **N**: Unmanaged (temporary, deleted, in generation, etc.) | ||
| 103 | * **B**: Cube in generation. Cube generation can be stopped by clicking on the [[image:1710249675342-408.png]] button in front of the cube name (or by ticking the box and then **Deleting**). | ||
| 104 | * **L**: Live data cube | ||
| |
25.1 | 105 | |
| |
73.1 | 106 | You can delete cubes in memory by checking the corresponding box and then clicking on the **Delete **button or(% id="cke_bm_3342S" style="display:none" %) by (%%)clicking on the [[image:1710249675342-408.png]](% id="cke_bm_3342E" style="display:none" %) button for (%%)each one. |
| |
26.1 | 107 | |
| |
73.1 | 108 | == Synchronizers == |
| |
66.1 | 109 | |
| |
73.1 | 110 | Synchronizers are in charge of cube synchronization tasks: |
| |
27.1 | 111 | |
| |
73.1 | 112 | * **"PlayTP" **: interactive tasks (launched by the user). For example, the user synchronises a {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} in the Studio or refreshes it from the dashboard. |
| 113 | * "**SyncTP": **scheduled tasks. These are mainly tasks relating to the scheduling of refreshes. They also include {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} synchronisation tasks for users other than the logged-in user. | ||
| 114 | * "**CopyTP": **tasks for sending exports to their destination (devices: file server, email, SMS, etc). | ||
| 115 | * "**ExportTP": **conversion tasks into the format requested for the export. For example, when a user exports a chart as a PDF. |