Create automated rules to automatically execute commands or generate event reports. The automated rules can also be configured for manual use which is useful when placing a task icon in a graphic map.
Step 1 Select Global I/O from the Events & Alarms menu. The Automates Rules window lists the currently defined rules.
The main window includes the following columns.
· Name: The name of the automated task.
· Enabled: Yes if the task is enabled. No if the task is disabled.
· Trigger: Operator-defined events, and or time schedules that execute an action or notification.
· Action: Reporting or device commands executed on devices.
· Notification: The notification type. For example: E-mail, FTP, or Syslog notification.
Step 2 Click Add, or select an existing rule and click Edit.
Tip You can also right click on an item in the table to display a pop-up menu of commands.
Step 3 In the resulting Add Automation Rule or Edit Automation Rule window, select or deselect the Enabled check box.
Step 4 Type a Name for the rule.
Step 5 (Optional.) Specify the Location.
Step 6 Click New or Edit.
Step 7 In the resulting dialog, select the trigger’s Type for the rule, then click OK.
The choices are:
· Event: The rule is invoked when an event matching the defined filter occurs.
– Select Event.
– Click Edit Filter to define the filter.
– Select a Time Schedule for the rule. If the event occurs within the specified schedule, the rule will be invoked. See Configuring Time Schedules to define the schedules.
· Periodic (time schedule): The rule is invoked according to a Monthly, Weekly, or Daily schedule. Select the day of week or day of month, if necessary, and the Time of day (in a 24-hour format).
· Manual Only: The rule is invoked manually. You can create a Quick Launch button or add the rule to a graphic map
Step 5 Define one or more Actions that occur when the rule is triggered. The action types are:
· Report: Generates a report that can be saved or sent to a user.
· Device Command: Executes a command on a specified device.
· CSV Import: Imports a comma separated value file containing personnel or organization data. The file must be located on an FTP server or an ICPAM server.
· Group Edit: Edits multiple personnel or badge records.
· Delay: Shows the time of delay between two actions performed in the Global I/O.
· External Command: An External command is used to run an EXE file or application on server from global I/O.
· Sanity Report Action: Provides a snapshot of the system status.
· URL Action: performs a pre-defined URL action.
Tip See Understanding Automated Rule Actions for descriptions of the fields and settings for each option.
Step 6 Specify the Notification destination that defines where the notification or report file will be sent. The choices are:
· E-mail: Sends the notification or report file to one or more e-mail addresses. To enable e-mail notifications, you must enter the SMTP server settings in the Automation Driver. For instructions, see Step 3 in Enabling the Automation Driver.
· FTP: Sends the file to the specified FTP server.
– Host: The FTP server IP address or name.
– Username: Log in username required by the FTP server.
– Password: Password to log in to the FTP server.
– Path: Path on the FTP server where files should be uploaded.
· Syslog: Sends the notification or report to a Syslog.
– Host: The Syslog server IP address or name. You must verify that the server is accessible and allows remote hosts to log messages. ICPAM does not verify the Host server availability.
– Facility: The log facility to use when recording the information to the Syslog.
Step 7 Select the desired notification recording options, by clicking the check boxes to activate or deactivate the options:
· Record event when trigger fails: Each time the trigger fails, record an event.
· Record event when action fails: Each time the action fails, record an event
· Record event when notification fails: Each time the notification fails, record an event.
Step 8 Click Save and Close.
See also:
Understanding Automated Rule Actions