AXIS Job Monitor is part of the AXIS GridLink Module feature.
Please note that this feature requires the AXIS GridLink Module Licence.
Please refer to the help topic "AXIS GridLink Module" for the overview.
After a batch job has been submitted to AXIS Job Controller successfully, the controller assigns the job a unique ID for future reference and asks the user whether to monitor the job status or not. The user can answer "Yes" to enter the monitor mode immediately, or answer "No" and enter the monitor mode later from the menu "Tools - GridLink Module - Monitor Remote Jobs".
Please note that the name of the remote AXIS master machine and the TCP port through which AXIS GridLink Controller is connected need to be specified in the System Parameters dialog on the job monitor. Please refer to help topic "Distributed Processing Tab in System Parameters" for more details.
Monitoring Jobs Without AXIS Key
The GridLink farm administrators usually are not AXIS end users and they don't have a AXIS security key which is required to run AXIS normally. However, if they use AXIS through the command line to monitor remote jobs, AXIS key is not required.
The syntax is shown below:
AXIS -GLC:controllername [-GLT:tcpport] -Monitor:[remotejobid]
If "TCP port" is not specified, the default port number (3764) will be used.
If "Remote Job ID" is not specified, the job monitor will simply show the whole remote job list. Otherwise, it shows the whole list, and the detailed batch status for the specified remote job.
Once entered the monitor mode, a complete list of jobs maintained by the controller is displayed as below.
AXIS GridLink Controller can retrieve the information on the batch status dialog on the currently running job and send it back to the monitor. The user can look at the batch status dialog as if the job is running on his/her local machine. At any time the user can close the monitor and even turn off the local machine. He/she can reconnect to AXIS GridLink Controller later and reopen the monitor as long the job is still running.
If the user entered the monitor mode right after the job was submitted, when the job is finished, the remote job list dialog will be closed automatically, the dataset will be reopened on the user's local machine and System Log messages ever logged during the run will be displayed, as if this job was run locally.
If the user has more than one GridLink licenced controllers, he/she can switch from one job queue to another using a combo box at the bottom.
When the remote job list becomes very long, it takes a while for the job monitor to receive the full remote job list. If the user doesn't have to receive the full list, he/she can turn on the option "only show up to 100 most recent jobs, plush all unfinished jobs" to make the job list come up much faster.
The user can control the batch through this dialog. e.g. clicking on the "Cancel" button to cancel the batch run. The name of the user who cancelled a running job will be logged and can be viewed with the detailed job information.
The user can click on the "Close Monitor" button on the caption bar to close this remote batch status dialog and return to the remote job list.
If the option "Move Remote Job Between Queues" is enabled in GridLink and the current job queue is busy, then the job may be moved to another available queue so that it can be started right away. When this happens, the job status is shown as "Moved". When the job is running, the user can be redirected to the other job queue to view the batch status dialog. When the job has finished, the original job record will be updated with the final status ("Done", "Aborted", etc.) and runtime information.
In the remote job list dialog, the user has the following menu items available by right-clicking on a remote job in the list:
View Detailed Information - show detailed information about this job. If this job failed to run, the detailed messages are also reported.
Show Remote Job Status - to display the remote batch status dialog on the local machine.
Change Resource Priority - to change the resource priority of a batch job if it is distributable and has not finished yet (either pending, running or being suspended). If this job is currently running, helper resources on the farm will be reallocated once the priority has been changed.
Please note that you can only change the priority for jobs submitted from AXIS 11501001 and later versions.
View Log - to display System Log messages logged for this batch job.
Suspend Pending Job - to suspend a job that is in pending state.
Resume Suspended Job - to resume a job that is being suspended.
Terminate Running Job - to ask AXIS GridLink Controller to terminate the AXIS processing that is running remotely. Please note that terminating AXIS can cause undesired results including loss of data and system instability. It is strongly recommended that the user selects "Show Remote Job Status" then uses "Cancel" button to cancel the batch job. The name of the user who terminated a running job will be logged and can be viewed with the detailed job information.
Resubmit Jobs - to resubmit one or more jobs that have been submitted previously.
Delete Jobs - to delete current job or selected jobs from the list. Please note that a job that is running cannot be deleted.
Move Up Pending/Suspended Job and Move Down Pending/Suspended Job - to change the order in which pending jobs are run.
Delete All Finished Jobs - to delete all finished jobs from the list.
For information about configuring AXIS GridLink Controller, Please refer to help topic "AXIS GridLink Controller".
For information about submitting a batch job to AXIS GridLink Controller, please refer to the help topic "Submit a Batch Job".