Configure an alarm
About this task
An alarm is used to send a notification when an exception occurs. The alarm definition specifies how a notification should be sent if an exception occurs. When a user defines a flow to schedule work, they can select an alarm to open if an exception occurs. They select an alarm from a configured list of alarms. Alarms are configured by the Process Manager administrator.
Alarms are stored in the directory JS_TOP/work/alarms. Each alarm is in a separate file named alarm_name.alarm. The file name and its contents are case-sensitive. Each alarm can either notify one or more email addresses, or execute a script.
The alarm file contains the following parameters:
Any alarm files with an invalid alarm definition will not be registered. Any extra unrecognized parameters are ignored, but the alarm will still be registered.
As the Process Manager administrator, create a new file in the directory
JS_TOP/work/alarms. Specify a name for the file that is a
meaningful name for the alarm, with a file suffix of alarm. For example:
The name you specify will appear in the Flow Editor in the list of available alarms.
- Optional. Specify a meaningful description for the alarm.
DESCRIPTION=Send DBA a message indicating DBMS failure
- Required. Specify the alarm type and definition.
Specify the "Email" command, followed by a space-delimited list of email addresses to notify regarding the exception. Specify the complete email address, or just the user name if JS_MAILHOST was defined in js.conf. For example:
You must specify a valid notification statement with at least one email address, or the alarm is not valid.
NOTIFICATION=CMD[/file_path/script_file user_variable ...]
Specify the "CMD" command, followed by the path to the script file and any user variables (such as the error code). For example:
Variable values cannot contain the backquote character (‘).
- To enable the alarm, reload the alarm list using the following