...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
... <NotificationCommand><![CDATA[ echo scheduler id=%MON_N_SCHEDULER_ID%, history id=%MON_N_ORDER_HISTORY_ID%, job_chain=%MON_N_JOB_CHAIN_NAME%(%MON_N_ORDER_ID%), step =%MON_N_ORDER_STEP_STATE%, error=%MON_N_ERROR_TEXT% > D://errors.txt ]]></NotificationCommand> ... |
SystemMonitorNotification/Notification/NotificationObjects
One of the following elements may be nested inside a NotificationObjects element:
| Element | Element description | Description |
|---|---|---|
| JobChain | Optional, once or more inside of NotificationObjects element | Restricts notifications for job chains |
| Timer | Optional, once or more inside of NotificationObjects element | Restricts notifications for job checks (Timer) |
SystemMonitorNotification/Notification/NotificationObjects/JobChain
JobChain support the following attributes:
| Attribute | Usage | Description |
|---|---|---|
| notifications | optional | Specifies the number of notifications that are sent to a System Monitor. Default: 1 |
| scheduler_id | optional | Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that would log into the same database. |
| name | optional | Job chain name including possible folder names |
| step_from | optional | Restricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes. |
| step_to | optional | Restricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes. |
| excluded_steps | optional |
Here you go an example of an XML file used for notifying a specific System Monitor (op5 Monitor) and using NotificationCommand:
...