SAP events matching criteria
The SAP background
events specified in the event rule are matched with the events raised
in the SAP system,
according to the following criteria. Depending on the parameters you
set:
- The SAP event ID and parameter are specified in the event rule
- To match, the SAP event
ID and parameter must be the same as the event ID and event parameter
raised in the SAP system.
Also, the event state must be N (New). SAP events
with a different parameter or without any parameter are ignored.
The information collected about the matching SAP event is sent by the r3evmon process to HCL Workload Automation. If the notification is successfully sent, the event is committed on the SAP system and its state changed to C (Confirmed).
For example, you define an event rule in your HCL Workload Automation plan based on the following SAP event:- SAP event ID
- SAP_TEST
- SAP event parameter
- ABCDEF
- Workstation
- An extended agent named GENIUS
!R3EVENT 0008SAP_TEST0006ABCDEF
Monitoring of the SAP_TEST event with parameter ABCDEF is automatically started. Suppose that the following SAP events were raised on the SAP system:Only the following SAP event is notified to HCL Workload Automation:Table 1. History table of the SAP events raised EVENT GUID SAP EVENT ID EVENT PARM EVENT SERVER EVENT TIMESTAMP EVENT STATE PROCESS STATE COUNT OF JOBS 1234 SAP_TEST ABC123 ... 20070925 13:00 C OK 1 2345 SAP_TEST ABCD ... 20070925 14:00 N OK 2 3456 SAP_TEST ... 20070925 15:00 N OK 3 4567 SAP_TEST ABCDEF ... 20070925 16:00 N OK 4 If the notification is successfully sent, the event is committed on the SAP system and its state changed to C (Confirmed).Table 2. SAP event matching with the event rule defined EVENT GUID SAP EVENT ID EVENT PARM EVENT SERVER EVENT TIMESTAMP EVENT STATE PROCESS STATE COUNT OF JOBS 4567 SAP_TEST ABCDEF ... 20070925 16:00 N OK 4 - Only the SAP event ID is specified in the event rule
- To match, the SAP event
ID must be the same as the ID of the events raised in the SAP system
whose state is N (New). The parameters of the SAP events,
whether specified or not, are not taken into account.
The information collected about all the matching SAP events is sent by the r3evmon process to HCL Workload Automation. Each event successfully notified is committed on the SAP system and its status changed to C (Confirmed).
For example, you define an event rule in your HCL Workload Automation plan based on the following SAP event:- SAP event ID
- SAP_TEST
- Workstation
- GENIUS
!R3EVENT 0008SAP_TEST
Monitoring of the SAP_TEST event is automatically started. Suppose that the following SAP events were raised on the SAP system:Only the following SAP events are notified to HCL Workload Automation:Table 3. History table of the SAP events raised EVENT GUID SAP EVENT ID EVENT PARM EVENT SERVER EVENT TIMESTAMP EVENT STATE PROCESS STATE COUNT OF JOBS 1234 SAP_TEST ABC123 ... 20070925 13:00 C OK 1 2345 SAP_TEST ABCD ... 20070925 14:00 N OK 2 3456 SAP_TEST ... 20070925 15:00 N OK 3 4567 SAP_TEST ABCDEF ... 20070925 16:00 N OK 4 Each event whose notification is successfully sent is committed on the SAP system and its state changed to C (Confirmed).Table 4. SAP events matching with the event rule defined EVENT GUID SAP EVENT ID EVENT PARM EVENT SERVER EVENT TIMESTAMP EVENT STATE PROCESS STATE COUNT OF JOBS 2345 SAP_TEST ABCD ... 20070925 14:00 N OK 2 3456 SAP_TEST ... 20070925 15:00 N OK 3 4567 SAP_TEST ABCDEF ... 20070925 16:00 N OK 4