When you run an eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase., 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 (agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host start, blocking statusThis represents the condition of a task (such as active, blocked, generating). of a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]) or userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. 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 scriptA particular Automation Engine object type. 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 UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] available at that time, the same limitations apply as for events that have been generated at runtime.
Stop execution
A running Event objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task 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.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |