This interface allows you to see all the Agent servers available to this JobServer environment.
Selecting this option let's you see all the Partitions that are using this Agent to run jobs on. An Agent server can't run jobs until a Partition has been associated to the Agent. The Partition can then specifiy the maximum number of jobs it wants to run on the Agent and then start directing jobs to run on the remote Agent.
This is the name of tha Agent server. This should be the default hostname of the machine used to reach the server. If you have edit rights, you can click on the Agent host name and edit the Agent's properties such as maximum allowed JVM memory, for example.
This shows the number of jobs running on the Agent and the maximum allowed number of jobs allowed to run as configured in each associated Partition. The Agent summary row will show the aggregated number of running jobs and the maximum allowed jobs for all the Partitions using this Agent. When looking at the Partition level details, this shows the number of jobs and the maximum allowed jobs for that particular Partition.
If you click on the highlighted link under Running Jobs, you will see a popup window that shows the active running jobs. From there you can see the details for each running jobs and also kill running jobs.
This indicates if the Agent is enabled or disabled to run jobs. An Agent that is enabled means that jobs are allowed to run on the Agent and that the Agent is accepting new jobs. Disabled means the Agent is not accepting new jobs, but will allow existing jobs to finish running.
When looking at the Partition level details, this will show if the Partition is enabled or disabled. If the Partition is disabled, this will effect the maximum allowed number of jobs for the Agent overall.
You can select the Agent and change the enable/disable state of the Agent. You may apply the changes to more than one Agent if you like.
This indicates the running status of the Agent. If an Agent goes down for any reason, the local environment on the host will try to restart the Agent Server if possible. The user can shutdown an Agent either gracefully which means that the Agent will only shutdown after all currrent jobs are finished (and will not accept new jobs). The user can also shutdown the Agent immediately which will terminate any running jobs and shutdown the Agent quickly. After shutdown the Agent will go into an "Idle" state. Normally, if you do not want an Agent to run new jobs, you should first disable the Agent instead of shutting it down.
You can select the Agent and change the running status of the Agent. You may apply the changes to more than one Agent if you like.
Use the add button to add new Agents. Agents can be added to any remote server that shares the same JobServer environment and is reachable.
To delete an Agent, the Agent must not have any associated Partitions linked to it and no jobs can be running on the Agent. Also, the Agent must be in disabled state for the delete to be permitted.
You can view the startup logs and runtime logs assoicated with each Agent. The startup logs show the startup sequences that the Agent went through during its last startup attempt. The runtime log shows a history of current and past start/stop events for the Agent and runtime loggin details during each run for the Agent.