Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this Wiki is to explain the resources  shown when running transaction SARFC

Overview

This page will go through the parameters used to evaluate the resources available in SARFC.

Transaction SARFC

When double clicking on the server name in transaction SARFC, you will get a popup to show the resource configuration.  For example, see the following screenshot from transaction SARFC:


 

 Pressing F1 in each of the "Resource Allocation" fields will show the associated profile parameter

Profile Parameters

Activated --> Parameter  rdisp/rfc_use_quotas

         Default value : 1

          You can use this switch to activate the quota setting for specifying resources.
           0  : Resouce specification deactivated
           1  : Resource specification activated (default)


Max.No.of Requests in Queue --> Parameter rdisp/rfc_max_queue 

Default value: 5%

 Quota for the maximum number of requests in the dialog queue.  If this value is exceeded, no further resources are returned to the caller, since the server should be protected from overload.

The value is specified as a percentage, that is, it depends on the current value set in the profile. The total number of requests in the queue is specified by the parameter %%rdisp/elem_per_queue%%.


Maximum Number of Logons --> Parameter rdisp/rfc_max_login

Default value : 90

Quota for the number of users logged onto the SAP system. If this value is exceeded, no further resources are returned to the callers as the server should be protected from overload.

The value is specified as a percentage, that is, it depends on the current value set in the profile. The absolute number of logons in the SAP system is specified by the
parameter %%rdisp/tm_max_no%%.


Maximum No. Separate Logons ==> Parameter rdisp/rfc_max_own_login
Default value : 25

Quota for the number of own logons in the SAP system. If this value is exceeded, no further resources are returned to the callers as the server should be protected from overload.

The value is specified as a percentage, that is, it depends on the current value set in the profile. The absolute number of logons in the SAP system is specified by the
parameter %%rdisp/tm_max_no%%.


Maximum Number of Used WPs ==> Parameter rdisp/rfc_max_own_used_wp

Default value : 75

Quota for the number of dialog work processes that the user can use at the same time. If this value is exceeded, no further resources are returned to the callers, as the server should be protected from overload. The value is specified as a percentage, that is, it depends on the current value set in the profile.
Note: This parameter is only effective in dialog operation. If the report runs in background processing or in the update, it is ignored.
The total number of dialog work processes is specified by parameter %%rdisp/wp_no_dia%%.


Minimum Number of Free WPs --> Parameter rdisp/rfc_min_wait_dia_wp

Default value    : 1

Number of dialog work processes that should remain free for other users, and are therefore not available for RFC requests. If no more dialog work processes are available for RFC requests, no
further resources are returned to the caller, since the server should be protected from overloading. The absolute number of dialog work processes is specified by the parameter %%rdisp/wp_no_dia%%. Example: There are 10 dialog WPs, rdisp/rfc_min_wait_dia_wp = 4. If the dispatcher receives an RFC request for processing, and there
are currently four dialog work processes free, the request is place in the queue, and only processed once at least five dialog WPs are free.


Maximum No.of Comm. Entries ==> Parameter rdisp/rfc_max_comm_entries

Default value: 90

Quota for the maximum number of communication entries that the user can use. If this value is exceeded, no further resources are returned to the caller, since the server should be protected
from overload. The value is specified as a percentage, that is, it depends on the current value set in the profile. The total number of communication entries is specified by the
parameter %%rdisp/max_comm_entries%%.


 Maximum Wait Time (Seconds) ==> Parameter rdisp/rfc_max_wait_time

Default value: 10

Specifies the maximum waiting time (in seconds) the system should wait after a load check. The waiting time is determined by the available resources. The fewer the available resources, the longer the waiting time.

Example

if the system has 10 dialog work processes (rdisp/wp_no_dia)  and based on the configuration from the screenshot above, you will have the below calculations:

Maximum Resources = (total dialog work processes – Maximum number of Free WPs) = 10 -1 =9:

Resources = total dialog work processes X Maximum Number of Used WPs = 10 X 75% = 7:

For more information check the here on the  online help.

Related Content

Related Documents

Related Notes

 74141      Resource Management for tRFC and aRFC