Group Configuration

From the System Administration tool you can create, edit, and view the Groups available in JobServer. By default, all Jobs that are created are put into the "DEFAULT" Group. New Groups can be created by the administrator. Jobs can be moved between Groups without restriction.

Edit Groups

A Group's name and description can be changed through this interface. Take special care if you decide to rename the "DEFAULT" Group. While the name of the default Group can be changed, it is best to name it something that will be easy to identify as the default. New jobs are placed into the DEFAULT Group by default.

Add and Remove Job Groups

Through this screen Groups can be added and removed. As many Job Groups as desired can be created. Existing Groups can't be delete if no existing jobs are assigned to the corresponding Group. All Jobs must be removed from the Group before the group can be deleted. Also, the DEFAULT Group can't be delete under any circumstance.

Alert Emails

Alerts are sent to the email addresses listed, when a job that is part of a Job Group encounters any kind a unexpected failure. This allows a person or group of people to be notified if anything exceptional goes wrong with any job within a Group.

Job alerts notify users when a Job failure occurs during processing. These are typically failures associated with the Job/Tasklet throwing an unexpected exception that may result in the Tasklet or Job failing to continue processing. For example an uncaught out of memory exception or sql exception would constitute such a situation. Also when a Job/Tasklet throws TaskletFailureException this will also trigger an alert to be sent out. Note that errors and warnings logged via Log4J or the Java Logging API do not trigger an email alert. The email alerts use a cascading mechanism. It works by first sending an alert to the email address listed at the system level. It then sends the alert to the email addresses defined for that Job's Partition, it then sends it to the Job's Group alert addresses, and then it finally will send it to the alert email addresses defined for the specific Job. With this design you can setup a hierarchy of email alerts. So, for example, you can set it up so that you only receive emails when a specific Job fails or when any Job in a specific Partition fails, ...etc.

The Tasklet may also programmatically trigger alerts by using the SOAFaces API. Refer to the API TaskletOutputContext.sendAlert().