When you run an event, the system distinguishes event recognition and event handling.
Event recognition
After activation and start, the event is in the condition SLEEPING. The system now permanently monitors whether an event occurs as previously specified. event recognition distinguishes real events and polling events.
A signal is generated if a real event occurs.
The responsible technical unit recognizes this signal and creates an AE
event.
real events are messages on a BS2000 Console, SNMP Traps, AE internal
signals (agent start, blocking status of a workflow) or user signals
via an interface, for example.
No signal is generated
if a polling event occurs. Instead, the system periodically checks if
an event of this type has occurred.
polling events are the presence or absence of particular files, the
workload of the file system, command results (analyzes of values and status
information of the OS) or SNMP values, for example.
Events can have values which means that a particular value is monitored. The event is triggered as soon as this value exceeds a defined limit. Events without values have no values to be monitored. The occurrence of a defined condition represents the event.
Event handling
Event handling is the processing of the !Process tab.
The post script of an event is not processed at its activation time. It is processed when the defined condition occurs. Active Event objects consider modifications made in !Process. As there is no UserInterface available at that time, the same limitations apply as for events that have been generated at runtime.
Stop execution
A running Event object can be stopped and restarted at any time.
Handling |
|
---|---|
Right-click the object in the Activity Window. |
Select Stop / Go in the context menu. |
End status
A normally ended event ends on status ENDED_OK, a canceled object ends on status ENDED_CANCEL.
A FileSystem event which ends because of its runtime settingswithout the conditions having occurred, it obtains the status ENDED_TIMEOUT.