The indirect destination is the RFC destination of an SAP System (such as the Solution Manager system), in which the destination of the monitoring system (monitored system) is known. The statistical data for the monitored system is then accessed indirectly using this intermediary system.
For example, you have three ABAP systems: A, B, and C, and you want to monitor systems B and C from system A. The RFC destination of system C is, however, only known to system B. In this case, the destination of system A to system B is the indirect destination. To create a system list in the system selection for this example, follow the procedure below:
Column | Description |
---|---|
Activated |
Indicator with which you can activate and deactivate the analysis of the component |
Component |
Component name (from the SCR) and, for ABAP systems, the name of the system |
Comp. Type |
Name of the component type (from the SCR) and, for ABAP Systems, the entry SAP R/3 |
Mon.Sys |
Monitoring system in which the statistical data of the component is collected; for ABAP systems, the system itself |
Dest. MonSys |
RFC destination of the monitoring system; this entry is empty if the monitoring system is the local ABAP system |
Indirect Dest. |
RFC destination of an ABAP system (for example, the system of the Solution Manager) in which the destination of the monitored system is known; access to the statistical data of the monitored system is then performed indirectly through this intermediate system |
Release |
Release of the SAP Web Application Servers; the system makes this entry automatically |
For ABAP systems, this is always the system itself, that is, for system A, enter A as the monitoring system, entering the monitoring system B for system B, and so on.
See also:
Selecting Data for the Functional Trace