-
Technical Assistance
Request product support from SAP
-
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Technical Assistance
Request product support from SAP
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
A remote function call (RFC) is the call of a remote-enabled function module (RFM) in a partner system. The caller is the RFC client and the called partner is the RFC server. Information about the server is stored on the client side in table RFCDES. RFC destinations are maintained in transaction SM59. The remote destination can be another application server in the same or a different R/3 System, an R/2 System, or a non-SAP system.
With synchronous RFC (sRFC), processing stops in the calling program while the called remote function is processed. Once the RFC output is returned, processing continues in the calling program.
In an asynchronous RFC, the called remote function is started immediately in the calling program and then continues processing on its own, separately from the calling program. The function output can be received later in the program. Asynchronous RFC is intended for parallel processing. You can also use aRFC within a single SAP R/3 System, for example, to move some of the processing load to an application server that is used especially for this purpose or use aRFC locally within the same application server to implement parallel processing in several work processes.
In table RFCDES, you can set the number of aRFC calls for each destination using the aRFC options. After these aRFC calls, an automatic load check is performed on the target server. If resource bottlenecks are detected, the system waits for a short time for the next aRFC call to the same remote system, and the client program is rolled out of its work process. It can then receive results from previous aRFC calls.
The following technical prerequisites have to be met in order to use the RFC monitoring:
With IFMon you can monitor RFC destinations of type 3 (to another ABAP system) or T (TCP/IP destinations).
Metric Name | Description | MAI Category | Since SP |
---|---|---|---|
RFC Channel available |
Availability measured by UXMon Script |
Availability |
7.1 SP 05 |
RFC Destination available |
Ping to RFC Destination |
Availability |
7.1 SP 10 |
RFC Destination available (with logon) |
Ping to RFC Destination including logon |
Availability |
7.1 SP 11 |
Number of AppLog Errors (RFC) |
Exceptions from Application log (SLG1) |
Exception |
7.1 SP 05 |
Number of ABAP Dumps |
Dumps in the target system containing the Destination name and the function module |
Exceptions |
7.1 SP 05 |
Number of Exceptions via ABAP Instrumentation Platform |
Number of Exceptions via ABAP Instrumentation Platform |
Exceptions |
7.1 SP 05 |
RFC Latency |
Latency time of a ping to RFC Destination |
Performance |
7.1 SP 11 |
Average RFC Response Time |
Average Response Time in ms |
Performance |
7.1 SP 05 |
Average RFC Response Time per Instance |
Average Response Time per Instance in ms |
Performance |
7.1 SP 08 |
Number of RFC executions |
Number of executions |
Performance |
7.1 SP 05 |
Number of RFC executions per Instance |
Number of executions per Instance |
Performance |
7.1 SP 08 |
Notes:
Note: Performance Warning: Because of potentially high data volume instance specific data collection is turned off by default
The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP).
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Note: If you didn't perform the infrastructure configuration yet, follow the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2.
Navigate to the Define Scope step. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection. You can add more than one RFC destination to one channel. Please note that the input help will only contain values after the available RFC destination were successfully collected by the extractor in the previous step, Preparation.
Select Metrics:
On the Metrics tab, select the metrics you want to monitor. Please note that the selected metrics are collected for each RFC destination entered above.
Enter Metric Parameters:
Metric: RFC Channel available
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
Script Name (mandatory): Enter the name of the UXMon script used to monitor the RFC availability. To learn how to record the UXMon script please refer to the wiki page ICMonAvailability Script.
Note: RFC Destination Name
Note that for some metrics the RFC destination needs to be fully specified and wild cards in the RFC destination parameter are not supported. These metrics are:
Note: RFC Destination available (with logon)
This metric requires a white list for the destination name and can only be selected via value help. If the destination is not available in the value help it cannot be used. This white list is created by the extractor scheduled in the setup step 5.1.
You can maintain attributes as described in the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2 on the Attributes tab.
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click Next in the main guided procedure to move to the Activation step.
Maintain Thresholds and Schedule: