Show TOC

Monitoring in the Back-End SystemLocate this document in the navigation structure

This section describes the monitoring tasks in the application back-end system.

Background RFC Monitor

If any RFCs involved in the message flow fail, the message is sent to the bgRFC queue described in the following sections.

To open the background RFC monitor, run transaction SBGRFCMON.

ABAP SMI uses the same bgRFC destination, IWFND_ODATA_PUSH, for the distribution of notifications to the active target servers if no other queue name is specified in the server settings (transaction CLB2_PLATF, field bgRFC Destination).

In this case, the unit names follow the pattern:

<service provider>_<application ID>_<timestamp>

Application Log for ABAP SMI

When exceptions occur, ABAP SMI writes detailed information to the application log. This is because only the information from the top-level exception is visible in the bgRFC monitor. More precise information from previous exception levels is not accessible from this monitor.

If you find an error in the bgRFC monitor, run transaction SLG1. You can find the log entries in transaction SLG1 as follows:

  • Object: CLB2 Collaboration (Add-On)

  • Subobject: GWN Gateway Notifications
The application log for the ABAP SMI object provides the option to display long text messages for detailed information.