Differences

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

--- rdms:webapp:processes [2025/03/18 10:45] – [Delayed Rules] More text jelte
+++ rdms:webapp:processes [2026/08/05 15:01] (current) – burcu
@@ Line 1: / Line 1: @@
-====== Processes/Jobs ======
+{{indexmenu_n>6}}
-{{indexmenu_n>5}}
-The RDMS web interface allows you to observe certain processes/jobs that you do via the web interface. For that, the //Processes/jobs// view on the left-side menu can be used. Moreover, this view allows you to observe the status of your //Delayed Rules//, a concept that will be explained in this section as well.
+====== Processes and Jobs ======
-{{ :rdms:webapp:rdms_procces_0.png?direct&800 |}}
+You can use the RDMS Web interface to view the status of processes and jobs that you started through the Web interface. Select the "Processes/jobs" icon in the main menu on the left to open this view.
-===== Processes/Jobs in the Web Interface =====
+You can also use this view to check the status of your delayed rules. The "Delayed Rules" section below explains this concept.
-If you perform certain operations in the RDMS web interface, these get registered as processes. The status of these processes can be observed here.
-Currently, the following operations are visible as processes:
+{{ :rdms:webapp:rdms_procces_0.png?direct&850 |}}
-  - Uploading of data via the web interface
-  - Bundling operations (compress to tar or decompress)
-  - Extraction of metadata
-  - Different steps of the [[rdms:workflows:archiving|Archiving Workflow]]
-By clicking on a listed process, you can get more details about it.
+===== Processes and Jobs in the Web Interface =====
-{{ :rdms:webapp:rdms_procces_4.png?direct&800 |}}
+When you perform certain operations through the RDMS Web interface, the RDMS registers them as processes. You can use the "Processes/jobs" view to check their status.
-This shows you, for example, the kind of process and the data on which it was executed. Moreover, every process gets a process number as well as a ID. The ID can be used to correlated the job to a Delayed Rule (see below) if applicable.
+The following operations are currently displayed as processes:
-**Note:** Not all jobs are executed as Delayed Rules as will described below. For example the upload operation, is not a delayed rule, but it has a Delayed Rule associated with it that is executed in the background (computation of data checksum).
+  * Uploading files through the Web interface
+  * Compressing folders into tar archives and extracting tar archives
+  * Extracting metadata
+  * Performing steps in the [[rdms:workflows:archiving|Archiving Workflow]]
+Select a process to view more information about it, as shown below.
+{{ :rdms:webapp:rdms_procces_4.png?direct&850 |}}
+The process details show information such as the type of process and the files or folders on which it was performed. Each process has both an "RDMS process ID" and an "ID". When applicable, you can use the "RDMS process ID" to match the process to the corresponding delayed rule.
+**Note:** The RDMS does not execute every process as a delayed rule. For example, uploading a file is not a delayed rule. However, the checksum calculation that starts after the upload runs as a delayed rule in the background.
 ===== Delayed Rules =====
-The RDMS is built on top of the data management software [[rdms:rdmsproject:irods|iRODS]]. The iRODS system has the in-built capability to execute certain task when a certain event is registered in the system. This automated tasks are called //rules// and they can be delayed, meaning being queued and executed in the background even if the user is not logged in anymore.
-We use rules at several places in the RDMS, often as delayed rules. Important example of delayed rules are:
+The RDMS is built on the [[https://irods.org/|iRODS]] data-management software. iRODS can automatically perform tasks when specific events occur in the system. These automated tasks are called rules.
+The RDMS can queue a rule and execute it in the background at a later time, even after you have logged out. This type of rule is called a delayed rule.
+The RDMS uses delayed rules for several operations, including:
+  * **Calculating checksums automatically:** When you upload files to the RDMS, the system calculates their checksums by using a delayed rule. The registered checksums allow you and the RDMS administrators to verify the [[rdms:data:integrity|integrity of your data]].
+  * **Compressing and extracting files through the Web interface:** When you compress a folder into a tar archive or extract a tar archive, the RDMS performs the operation as a delayed rule.
-  * **Automated checksum calculations of your data**: If you upload files to the RDMS, a automated checksum calculation for your files with be executed as a delayed rules. This guarantees that all your files have a checksum registered which gives you/us the capability to check the [[rdms:data:integrity|integrity of your data]].
+To view your delayed rules, select the second tab in the "Processes/jobs" view.
-  * **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 be also executed as a delayed rule.
-You can observe the status of your rules via the second tab in the processes/jobs view.
+{{ :rdms:webapp:rdms_procces_5.png?direct&850 |}}
-{{ :rdms:webapp:rdms_procces_5.png?direct&800 |}}
+Each delayed rule displays its "RDMS process ID". You can use this value to match the delayed rule to the corresponding process or job. The "ID" is a separate identifier shown in the Web interface.
-The RDMS process ID is visible for every delayed rule via the web interface which allows you to correlate a job with its respective delayed rule. For example, in the screenshot above, you can see that the process ID is the same as the one in the screenshot above it which showed the related job.
+In the examples above, the delayed rule and its related job have the same "RDMS process ID".
-Moreover, you can see here some more information of the kind of delayed rule (in the above example the creation of a tar archive). As well as its **priority** which is in this example 9 which indicates a delayed rule that will be executed with highest priority.
+The example below shows a delayed rule for creating a tar archive. The rule details include its assigned priority. The RDMS uses the following priority levels to determine queue preference:
-In contrast, the automated checksum calculations have a lower priority of 1 by default.
+  * **Priority 9:** Rules with high queue priority
+  * **Priority 5:** Rules with medium queue priority
+  * **Priority 1:** Rules with low queue priority, such as checksum calculations
-{{ :rdms:webapp:rdms_procces_6.png?direct&800 |}}
+{{ :rdms:webapp:rdms_procces_8.png?direct&850 |}}
+The priority system allows critical tasks, manually started tasks, and tasks that are part of an [[..:workflows:|RDMS workflow]] to receive a higher queue preference than common, automatically scheduled tasks.
-The priorities are set as such that the task that are executed from the web interface like tar creation or decompression, extraction of checksums, and the steps of the archiving workflow, are executed with a higher priority (meaning: earlier) then the automated checksum calculation. The reasons for that is that if a user uploads a folder with multiple thousand of files and the checksum calculation rules take highest priority, this might clog the whole queue for some time.
+For example, the RDMS must calculate a checksum after you upload a file. However, this calculation should not delay an Archiving Workflow. The RDMS therefore assigns checksum calculations a lower queue priority, allowing higher-priority operations to be processed first when resources are available.
+You can also check the status of delayed rules through the command-line interface (CLI). Use the ''iqstat'' command in ''iCommands'' to display your delayed rules that are waiting to run.
+{{ :rdms:webapp:rdms_procces_9.png?direct&850 |}}