A Job is a specific task that can be independently executed. Using the Zend Platform's Job Queue feature, Jobs can be handled in queues providing an easy way to manage and handle Job execution.
The Jobs screen is accessed from: Job Queues | Jobs.
Through this screen users can:
Filter Table Data
Locate Jobs by their ID number
View Job Details in a sortable table
Filtering Table Data
Zend Platform allows you to filter the Jobs displayed in the Jobs table.
The filter options are as follows:
Queue - The name of the Queue
Status - The statuses are: Scheduled, Dependant, Ready to Run, Running, Suspended, Successful and Failed.
Priority - High, medium or low.
Host - The host on which the Job is to be executed.
Recurrence - Jobs can be nonrecurring (run once) or recurring (defined to be executed repeatedly).
Name - The alias for the Job script. Defined when creating a new Job or in Code based Jobs defined in the function: setJobName($name), if left empty the filter by script name.
The status line (above the filter by options) changes to show a summary of the items that are currently displayed in the table.
To filter the data displayed in the Jobs table:
Select the filter criteria to apply to the table by clicking "Filter By" and selecting the options from the drop-down lists..
Click "Go" to display the filtered events in the Jobs table.
The Jobs Table displays the following information:
ID - a unique identifier given to each Job managed through Zend Platform.
Name - an alias for the Job script. Defined when creating a new Job or in Code based Jobs defined in the function: setJobName($name), if left empty the script name will be displayed.
Status - the current state of the Job (see list of statuses below)
Priority - the importance of the job, the priorities are (in order of importance) Low, High, Normal, Urgent. Defined when creating a new job or in code based Jobs defined in the function: $_priority = JOB_QUEUE_PRIORITY_[TYPE];
Application - an additional identifier for grouping and filtering Jobs. Defined when creating a new Job or in Code based Jobs defined in the function: $_application_id = null, if left empty no name will be displayed.
Host - the name of the Host on which the Job was generated.
Script - the name and location of the actual script initiated by the Job.
A Job can hold one of the following statuses:
Scheduled - a Job which is waiting to be executed since it has been scheduled to a time later than the current time.
Dependent - a Job which is waiting to be executed since it waits for a previous Job to finish running.
Ready to run - a Job which is ready to be executed.
Running - a Job which currently runs.
Suspended - a Job which can run but is currently suspended (paused). A Suspended Job can be resumed and hence moved to another status.
Successful - a Job which has completed and resulted in a success.
Failed - a Job which has completed and resulted in a failure.
The maximum count of Jobs displayed in this page is configured in the Preferences page: Job Queues | Settings.
Locating Jobs by Job ID
Each Job is given a unique ID number when it is created. If you know the Job ID of a specific Job you want to view, enter the number into the "Find Job by ID" field and click Find to display the Job in the Jobs table.
View Job Details
The Jobs table displays various details regarding the displayed Jobs.
Apart from the basic information displayed users can click on a Job in the Jobs table and open the Job Details Page (for more information on Job Details see Job Details).
The Jobs tab includes the following Job management options:
Delete - Remove a Job from the list. Jobs that are in progress will complete running and then be deleted.
Resume - Resume a Job that was previously suspended.
Suspend - Suspend a Job from running.
To apply one of these options to a Job, select a Job by marking the check box (you can select more than one) and click one of the Job management options (Delete, Resume or Suspend).
If you want to apply one of the options to all the Jobs in the table click "Select All".
When applying one of the management options to multiple Jobs make sure their current state does not conflict with the option for example, you cannot delete active Jobs.