...
Attribute | Usage | Description |
---|---|---|
language | Required | Script language name Supported languages:
|
Message
Usage
The Message sended to System Monitor can be configured as CDATA element on the following parent nodes:
...
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Example: scheduler id = %MON_N_SCHEDULER_ID%, history id = %MON_N_ORDER_HISTORY_ID%, job_chain = %MON_N_JOB_CHAIN_NAME%(%MON_N_ORDER_ID%), error = %MON_N_ERROR_TEXT%
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
|
Example: step from = %MON_S_STEP_FROM%, step to = %MON_S_STEP_TO%, notification = %MON_S_NOTIFICATIONS% (of %MON_S_MAX_NOTIFICATIONS%)
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Example: timer name = %MON_C_NAME%, text = %MON_C_CHECK_TEXT%
Service variables
Name | Description |
---|---|
%SERVICE_NAME% | |
%SERVICE_STATUS% | |
%SERVICE_MESSAGE_PREFIX% |
Example: service name = %SERVICE_NAME%
Environment variables
All existing system variables can be defined by message with the syntax like %<variable name>%
(Windows/Unix)
.
Example: %TEMP%/test.exe
Examples
Status | ||||
---|---|---|---|---|
|
...
- 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.