Events are significant in SAP's background processing. Event objects of type "Console" can be used to monitor SAP events.
The 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 periodically polls the SAP system for occurred SAP events and reports them to the active Console events in an interval the administrator has defined in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_HOSTCHAR_DEFAULT, key JOB_CHECKINTERVAL.
Filters are available which serve to define the SAP events to be monitored. The statements defined in the !Process tab initiate further processing steps as they are processed when an agent reports a SAP eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase..
Use the functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… GET_EVENT_INFO in the !Process tab. It supplies details about the SAP event that has occurred.
Several filter lines can be specified in the table in the tab's lower area. !Process is processed if a SAP event is triggered which meets at least one filter specification. !Process is NOT processed several times if several filter specifications are met.
Overlapping filters can occur if several Console events are used. The agent would then notify all Console events about the relevant SAP event.
AE does not only provide Console events but also functions which can be used to handle SAP events via Job objects. R3_GET_EVENT waits for a SAP-triggered event and R3_RAISE_EVENT can be used to trigger a SAP-defined event.
XBP 3.0 is required in order to monitor SAP events of event type "Console". The administrator can specify the XBP 3.0 interface in the SAP agent's INI file.
If the agent loses its connection to the SAP system, SAP events can accumulate as the agent is not able to forward them to the Console events. As soon as the connection has been re-established, the agent checks if there are SAP events and reports them to the affected Console events.
Due to the fact that huge data amounts can be involved, the agent does not read all SAP events at once. The administrator can define the required handling in the agent's INI-file parameter maxEventTimeSpan= .
The agent cannot monitor SAP events if it is terminated. After a restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts., it retrieves the point in time when it last monitored SAP events and also reports SAP events that occurred during its termination.
All agents connected to the SAP system poll SAP events. This means that each agent reports all SAP events which occurred to the Console events.
If the SAP system's time runs behind AE's system time, the first SAP events cannot be received if they occur in the gap between the two different times.
See also:
Event Management
Sample Collection - Reaction to External Events
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |