Show TOC

Procedure documentationTrigger Resource Check as RFC Client Locate this document in the navigation structure

 

In transaction SM59 you can trigger from the server the resource check for an RFC destination. This delays the transmission of RFC calls.

Before the function module is executed the system checks whether the destination system has sufficient resources. If it hasn’t, the execution of the function module is delayed for a specified time.

The algorithm is the same as in the Detailed Check.

Procedure

  1. In transaction SM59 select the required RFC destination and double-click on it. Then choose   Edit   aRFC Options  .

  2. Choose Load Check Active.

    You can select either a static or a dynamic check.

    • Static check after n calls: Standard value n =10 is preset, but you can change this.

      After n asynchronous calls, the current system load of the remote system is evaluated.

    • Dynamic check: First of all the number of available resources for this destination is determined. If these resources are occupied by asynchronous calls, the next load check is carried out.

Result

This check on the client system ensures that requests do not accumulate in the dispatcher queue on the RFC server.