The Automation Engine notifies connected client programs¹ of changes in the AE system using kicks. There are several different types of kick. You can see these kicks by enabling xml=3 tracing for the GUI or AWI.
| Kick type |
Description |
Example |
|
|
The AE folder tree has changed. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">OFS </kick> |
|
|
The EH table has changed — may impact open Activities windows (JUI) or Process Monitoring views (AWI). |
Automic Web Interface²
<kick client="0001" idnr="0000000000" system="AE_SYS_1">EH </kick>
Java User Interface²
<kick client="0001" idnr="0000000000" system="AE_SYS_1">OH </kick>
|
|
|
Client state has changed to active. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">SYS_GO </kick> |
|
|
Client state has changed to stop. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">SYS_STOP </kick> |
|
|
Prompt values are required in order to a execute an object. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">PRMPT </kick> |
|
|
Notification was added or removed for the current user. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">EOI </kick> |
|
|
Host assignment has changed. |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">HACL </kick> |
|
|
Undefined kick |
<kick client="0001" idnr="0000000000" system="AE_SYS_1">UNDEFINED </kick> |
Notes:
1. Such as the AWI, JUI, agents, and programs using the Java Application Interface
2. OH is the table where the AE objects are stored; EH is the activity table. It is not clear why ACTIVITY_LIST_CHANGED kicks are labeled OH kicks in the UCDJ trace, instead of EH kicks.