Cisco Cisco Workload Automation 6.3 Betriebsanweisung

Events

Event Types

Trigger History Tab

The 

 tab lists all of the instances when the event was triggered during the trigger history retention 

period. This retention period is configured on the 

 tab of the 

 dialog. For information 

about the fields and options on this tab, refer to the 

.

File Events

About File Events

An event monitor can be defined to monitor for a designated file and trigger an associated action whenever that file meets 
the defined conditions. 

File Event Definition Dialog

A file event monitor is defined from the 

 dialog. The 

 dialog displays 

whenever you add or edit a file event. 

In the 

 pane, select 

 to display the 

 pane. To display the 

dialog, either right-click in the 

 pane and select 

 from the context menu or 

click the 

 button.

Common to All Tabs



 – The name of the system event (up to 30 characters).



 – The owner of the system event. By default, the creator is the owner.



 – Makes this event available to all users of CWA as allowed by their security policy. You can create a default 

for this option on the 

 tab in the 

 dialog.



 – Makes the event available for use. When this option is cleared, the event cannot be triggered by the 

master. If the event is inactive, the event cannot be monitored by the master. 

File Monitor Tab

The 

 tab defines the file and the event characteristics that a file monitor will watch for. 

This tab contains the following elements:



 – Enter or select the name of the agent that will process the file.



 – Designates the directory where the file being monitored is located.



 – A specific file name can be entered or a mask using the asterisk (*) and question mark (?) characters 

can be created to filter for certain files to be monitored.

Any combination of the following criteria options can be selected to apply to the file.



 – The file must reach the size (in bytes) that is specified here.



 – The event monitor must wait the number of milliseconds specified here 

before it can react to the defined event.



 – The file size must remain unchanged for the specified number of 

milliseconds before the event conditions are met.