Monitoring Screen

Use the Monitoring screen to get detailed information about RFC Trace Files and SAP Log Files.


Overview over RFC Trace Files
This list shows you all existing RFC Trace Files.

Trace File
Name of the RFC Trace File. By clicking on the name you can get detailed information about a single trace entry. With the RFC Trace File you can verify if a RFC call has been executed successfully.

Size (byte)
Size of the Trace File. RFC Trace Files are split into several parts, each containing one trace entry.

Created On
Date and time of the trace entry creation.

Delete
You can delete a single trace entry by clicking the button [X] in the corresponding line. If You want to delete all trace entries, click [delete all].

Overview over SAP Log Files
This list shows you all existing SAP Log Files.

SAP Log File
Name of the SAP Log File. By clicking on the name you can get detailed information about all communication procedures executed by the BC server. For example, you can verify if a BAPI, a Function Module, or an IDOC has been processed correctly.

Size (byte)
Large SAP Log Files are split into several parts of about 500K. Larger documents take a long time to be created or may cause a time out. By clicking on Display SAP log, you can return from the display of one part to the overview list of that file.

Created On
Date and time of the log file creation.

Delete
You can delete a single log file by clicking in the corresponding line. If you want to delete all log files, click [delete all].

jARM Overview
jARM (Java Application Responstime Measurement) is a monitoring feature that gives you an overview of the status of a JAVA system.

jARM Request Summary
Overview of all jARM requests.

Requests total
Number of requests executed so far.

Request rate
Requests per second since the jARM Monitoring has been started.

Requests ok
Number of successful requests.

Requests with errors
Number of requests with errors.

Components total
Number of components used in requests.

Components per request
Average number of components per request.

Total time
Execution time for all requests in milliseconds.

Average time
Average execution time for a request in milliseconds.

jARM Requests
Additionally, it's possible to get more information about Requests and Components. You can get the TOP 100 requests, i.e. the requests that needed the longest execution times. To restrict those entries you can specify two inputs before pressing the "Show"-Button:

Info for ...
Wildcard-like pattern for the request names, you want the information for. You can use only exact patterns and patterns with a single '*' at the end, such as 'IDoc*'. It's not possible to use something like '*XML*'.

max. listed Requests
Limits the number of requests to the given number. After pressing the button, you're getting to the jARM Requests Overview.

Click the link to get to the jARM Requests screen.

jARM Components
Here you can get accumulated information about all components, that have been used in requests. To restrict those entries you can specify an input before pressing the "Show"-Button:

Info for ...
Wildcard-like pattern for the Component names, you want the information for. You can use only exact patterns and patterns with a single '*' at the end, such as 'client.*'. It's not possible to use something like '*Render*'.

Click the link to get to the jARM Components screen.