Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
rdms:webapp:processes [2025/09/22 12:28] – re-edit after change to styling agreements giuliordms:webapp:processes [2025/09/23 13:47] (current) – some small text changes jelte
Line 10: Line 10:
  
 Currently, the following operations are visible as processes: Currently, the following operations are visible as processes:
-  - Uploading of data via the web interface +  - Uploading of data via the web interface. 
-  - Bundling operations (compress to tar or decompress) +  - Bundling operations (compress to tar or decompress). 
-  - Extraction of metadata +  - Extraction of metadata. 
-  - Different steps of the [[rdms:workflows:archiving|Archiving Workflow]]+  - Different steps of the [[rdms:workflows:archiving|Archiving Workflow]].
  
 By clicking on a listed process, you can get more details about it, as shown below.  By clicking on a listed process, you can get more details about it, as shown below. 
Line 31: Line 31:
  
   * **Automated checksum calculations of your data**: If you upload files to the RDMS, an automated checksum calculation for your files will be executed as a delayed rule. This guarantees that all your files have a checksum registered, which gives you and us the capability to check the [[rdms:data:integrity|integrity of your data]].   * **Automated checksum calculations of your data**: If you upload files to the RDMS, an automated checksum calculation for your files will be executed as a delayed rule. This guarantees that all your files have a checksum registered, which gives you and us the capability to check the [[rdms:data:integrity|integrity of your data]].
-  * **Bundling/Unbundling via the web interface**: If you use the function to compress a folder to a tar archive or to decompress a tar archive, it will also be executed as a delayed rule.+  * **Bundling/Unbundling via the web interface**: If you use the function to compress a folder to a tar archive or to decompress a archive, it will also be executed as a delayed rule.
  
 You can observe the status of your rules via the second tab in the processes/jobs view.  You can observe the status of your rules via the second tab in the processes/jobs view. 
Line 43: Line 43:
 {{ :rdms:webapp:rdms_procces_8.png?direct&850 |}} {{ :rdms:webapp:rdms_procces_8.png?direct&850 |}}
  
-The priorities are set such that critical tasks, tasks initiated manually by the user, and tasks that are part of a workflow are allowed to jump the queue and be executed before tasks that are not essential to the functioning of the system, numerous, common, and automatically scheduled. For example, it is important that the checksum of a file is calculated after the file is uploaded, but this calculation should not stop the archiving workflow from moving to the next step. Even if the file was uploaded way before the workflow started, the calculation of the checksum is given minimal priority, so that it may happen when the system is mostly idle.  +The priorities are set such that critical tasks, tasks initiated manually by the user, and tasks that are part of a [[..:workflows:|workflow]] are allowed to jump the queue and be executed before tasks that are not essential to the functioning of the system, numerous, common, and automatically scheduled. For example, it is important that the checksum of a file is calculated after the file is uploaded, but this calculation should not stop the archiving workflow from moving to the next step. Even if the file was uploaded way before the workflow started, the calculation of the checksum is given minimal priority, so that it may happen when the system is mostly idle.  
  
 You can also check the status of delayed rules via the CLI tool [[rdms:access:linux:icommands|iCommands]] using the ''iqstat'' command, which shows the user's delayed rules that await execution. You can also check the status of delayed rules via the CLI tool [[rdms:access:linux:icommands|iCommands]] using the ''iqstat'' command, which shows the user's delayed rules that await execution.
  
 {{ :rdms:webapp:rdms_procces_9.png?direct&850 |}} {{ :rdms:webapp:rdms_procces_9.png?direct&850 |}}