Job Monitoring

(This page is under construction.)

In this context, Job Monitoring is the act of monitoring the status of jobs submitted by MOTEUR. This can be done in two ways:

• Job Monitoring Plugin
• the jobs.php page of a workflow.

Job monitoring plugin:

This is a plugin developed for use in the VBrowser. During and after the course of a workflow, the user can open this in the following steps:

1. Open the workflow in the VBrowser.
2. At the top of the page, select Logs.
3. In the list of files, select jobs.vljids.
4. If the mime-types are configured correctly, the VBrowser will open the JobMonitoring plugin and view all waiting, running and stopped / completed jobs.

Of the completed jobs, the user can download the files stdout and stderr result files through the following steps in the monitoring plugin:

1. Open the plugin for the workflow for which to download the files.
2. In the configuration tab, specify the grid resource (LFC location) to download the files to.
3. In the jobs tab, select the checkbox(es) of the jobs for which you want the files.
4. Click the 'Retrieve Output' button.
5. A status screen opens, with the progress for the download of the files. If this completes successfully, the end result is in the specified location.

The jobs.php page of a workflow.

There is also a webbased implementation of the job overview system. This omits the use for the plugin, but does not allow for downloading the std.out and .err of a job.

1. Open the workflow in the VBrowser.
2. Left-click the workflow.

A new page is now loaded with 'job details' as they're currently known by MOTEUR.

The main difference between these two techniques are the following:

• The jobs.php page of the workflow shows a statis snapshot of the situation. When the user refreshes the page, the snapshot is also refreshed, but it does not auto refresh yet.
• The jobs.php page of the workflow does not allow for the download of the std.out and std.err of a job. This requires grid access. This is unfeasable through a webbrowser in the current setup.
• The jobs.php page of the workflow can be opened in a webbrowser. Whereas in the earlier version of MOTEUR the file jobs.vljids was offered to the user when the user clicked a workflow in a normal webbrowser, now the jobs.php file will open, giving an overview of the jobs.
• The original JobMonitoring plugin opened the list of jobs and for each job queried the grid about the status. In the jobs.php page, the status is evaluated from the information that is kept by MOTEUR.This information can also be found in the 'jdl' subdirectory of the workflow, in the '.jdl.log' files.