- Print
- DarkLight
All Submitted Jobs
Suppose that a user is performing a print job. Some print jobs can take quite some time but of course the user, meanwhile, wants to be able to work on other tasks. Therefore a print job typically runs in the background so that the user can continue working. The handling of the background job is taken care of by a quartz scheduler.
Such a background print job will show up in the list of submitted jobs.
Should a background job, like the print job, get stuck for some reason, it is possible to remove that job from the list, a functionality that makes the list of submitted jobs an important administrative tool.
Selecting the Submitted jobs task will take you to the Submitted jobs main portlet as below.
Figure 23 Submitted jobs main portlet
Table 17 Submitted jobs main portlet fields
User | Login name of the user that is running the job. |
Schedule name | Schedule name of the job. Scheduler names are defined in the sitedef. The schedule name “_batch” is system predefined. Jobs with a schedule name of “_batch” are, in contrast to “_persist” removed at system restart. |
Name | Job name. |
Status | Status of the job. |
Started | Start time of the job. |
Progress | Job progress. |
Info | Job information. |
Ended | Time when the job ended. |
Memory Utilisation | The amount of system internal memory used by the job. |
Table 18 Submitted jobs main portlet buttons
Refreshes the view. | |
Closes the portlet. | |
Removes all finished jobs from the list of submitted jobs. |
Figure 24 Submitted jobs main portlet right click options
A right click on a specific job entry will present three different options:
Remove: Removes the job from the list of submitted jobs
View: View details of the job
Calculate memory utilization: Calculates the amount of memory that the job uses and populates the field Memory utilization with the calculated value
Submitted jobs top segment
The top segment (see highlighted segment in Figure 25) of the submitted jobs main portlet gives you a summarized view of the total number of jobs ran for a specific scheduler (scheduler name).
Figure 25 Submitted jobs main portlet top segment
Non submitted jobs
Note that not all quartz scheduler handled background jobs, such as for example process related scheduled jobs, populates the list of submitted jobs. This is because the system designer has not wanted all jobs, given the character of the job, to be regarded as a submitted job. Figure 25, where 670 jobs have executed but the list of submitted jobs is empty without having been cleared, provides an example of this