Each task has the following properties:
ERROR_NOTIFICATION_WARNING = nn MINUTES
ERROR_NOTIFICATION_WARNING = nn MISSED_POLLS
ERROR_NOTIFICATION_REMINDER = nn MINUTES
ERROR_NOTIFICATION_REMINDER = nn MISSED_POLLS
After viewing the list of tasks, the administrator may modify some aspects of any one of the tasks:
Generally, this function is used to modify the start option, either to start or to stop a task from executing or to alter the frequency with which the task executes. No matter what the prior value is for start option, when the user updates the task, the specified start option is carried out by the task control task. START_NOW and STOP_NOW have immediate consequences on the target node, as long as the task control task (TASK_CONTROL_TASK) is running.
One of the options in the task management utility EDIT screen is to delete a task. Note that this only removes the task from the task management utility and has no effect on the background processing of the task. If it is already running, it continues to run. If the task is stopped or in error it remains in that state.
Some tasks run on a single node, and some may or must run on all nodes in your network. There are some considerations:
ADD_UPDATE | Add & Update Task | Optional. This may be run on any or all nodes and must be run if you are using ADD, COPY and UPDATE business rules or handling large-sized file imports |
BATCHMAIL | Batchmail Task | Optional. Should but should be run on a single node to process outgoing notifications |
ESCALATION | Escalation Task | Optional. Should be run on a single node to process issue escalations |
EVMAIL | EVMail Task | Optional. Can be run many times on one or more different nodes to process incoming emails. Each instance of the task can be configured differently |
FILE_IMPORT_WORKER | File Import Task | Optional. Used to process file imports |
FULL_TEXT_SYNCHRONIZE | Quickfind Task | Optional, but is almost always run on a single node to process inserted and updated text within issues |
SCHEDULED_REPORT_TASK | Scheduled Report Task | Optional, but must be run to process the scheduling and delivery of reports |
SESSION_MONITOR | Session Monitor Task | This must run once on all nodes, and runs by default |
TASK_CONTROL_TASK | Task Control Task | This must run once on all nodes, and runs by default |
TEMPLATE_LOADER | Template Loader Task | Optional but if used should be run on all nodes. Used in a small number of sites to pre-load the most commonly used templates, thereby improving performance to users when the application server is first started |
On any node, you may monitor the status of tasks running on that node or other nodes within the cluster. You can start and stop tasks from any node and download the application server log from any of these nodes. This is providing that you have permission to that part of the file system with an absolute path.