...
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
<SystemMonitorNotification system_id="OP5">
...
|
SystemMonitorNotification / Notification
...
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
...
<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
...
Expand |
---|
|
Name | Description |
---|
%SERVICE_NAME% | | %SERVICE_STATUS% | | %SERVICE_MESSAGE_PREFIX% | |
|
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
service name = %SERVICE_NAME% |
OS environment variables
All existing system variables can be defined by message with the syntax like %<variable name>%
(Windows/Unix)
.
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
%TEMP%/test.exe |
Examples
Notification environment variables
...
_STATUS% | | %SERVICE_MESSAGE_PREFIX% | |
|
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
service name = %SERVICE_NAME% |
OS environment variables
All existing system variables can be defined by message with the syntax like %<variable name>%
(Windows/Unix)
.
Code Block |
---|
language | xml |
---|
title | Example |
---|
collapse | true |
---|
|
%TEMP%/test.exe |
Examples
Code Block |
---|
language | xml |
---|
title | Message on error |
---|
collapse | true |
---|
|
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% |
Code Block |
---|
language | xml |
---|
title | Message on Success |
---|
collapse | true |
---|
|
scheduler id=%MON_N_SCHEDULER_ID%, history id=%MON_N_ORDER_HISTORY_ID%, job_chain=%MON_N_JOB_CHAIN_NAME%(%MON_N_ORDER_ID%), order time elapsed = %MON_N_ORDER_TIME_ELAPSED%s |
Code Block |
---|
language | xml |
---|
title | Message on timer |
---|
collapse | true |
---|
|
name = %MON_C_NAME%, 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 from=%MON_C_STEP_FROM%,step to=%MON_C_STEP_TO%, check = %MON_C_CHECK_TEXT% |
Notification environment variables
com.sos.scheduler.notification.plugins.notifier.SystemNotifierProcessBuilderPlugin
...
- System Monitor: The step of notifying JobScheduler through an acknowledgement in the System Monitor is an execution of a script. This is nothing else than a notification, like sending a mail for instance, but instead, another action is executed, which is the execution of the script that contacts JobScheduler and add an order to the JobChain
ResetNotifications
described above.