Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

ABAP Application log entries (Transaction SLG1) are written for several actions. All entries can be identified by the object name EEM. The following sub-object names exists with their related action:

SUBOBJECT

Description

UPLOAD

When a script and global resources are uploaded from an EEM Editor you can identify with this applog entry, which resources have been uploaded by whom and when.

DEPLOY

When a script or a resource is deployed or undeployed you can identify with this applog entry which resources have been deployed/undployed to/from which robot.

RUN

This entry is written when a user triggers in the monitoring application the action 'Run Script with trace'.

TEMP_CONF

This entry is written when a user triggers in the monitoring application the action 'Set Temporary Configuration'.

START

This entry is written when a script is started either by a user in the admin application (SOLMAN_SETUP) or by a Background job for downtime management.

STOP

This entry is written when a script is stopped either by a user in the admin application (SOLMAN_SETUP) or by a Background job for downtime management.

TRIGGER

By default writing this log entry is disabled and it should be set only for troubleshooting of collection problems.
Whenever an extractor for collecting the system data is calling the E2E Trace application in JAVA stack applog entries are written for this sub-object. The success message contains the number of system data that could be retrieved and error message contain the reason why no data could be found (e.g. http log missing, connection not possible,...). It can be enabled by setting the check box 'Logging of Server Side Collection' in SOLMAN_SETUP -> Technical Monitoring -> EEM-> Step 2.2 (Global Settings).

  • No labels