RFC Resources on the Application Server 

A total of rdisp/tm_max_no users can be simultaneously logged on to the server (using the GUI or RFC). If rdisp/rfc_max_login % of the maximum number of users are logged on, no more RFC logons can be accepted. An RFC user may occupy a maximum of rdisp/rfc_max_own_login % of the login slots (see isp/tm_max_no).

Display: User List (transaction SM04). For more information, see Display and Manage User Sessions.

The dialog queue of the dispatcher contains rdisp/elem_per_queue entries. A maximum of rdisp/rfc_max_queue % of these may be filled by RFC requests.

Display: SAP servers (transaction SM51): Goto ® Server Information ® Queue Information. For more information, see Overview of SAP Application Servers.

The communication table contains an entry for every CPIC communication for all parties involved. The table can contain a maximum of rdisp/max_comm_entries entries. One user may occupy rdisp/rfc_max_comm_entries% of these.

Display: SAP servers (transaction SM51): Goto ® Server Information ® Communication table. See also Overview of SAP Application Servers.

When the server is started, it has rdisp/wp_no_dia dialog work processes. This number can, however, be changed while the server is running. One way to do this is to use operation mode switching. You can find out the current number of processes in the Process Overview (SM50; see also Display and Control Work Processes). Of the dialog work processes, the dispatcher keeps rdisp/rfc_min_wait_dia_wp free for "genuine" dialog requests (not RFC).

A user may occupy a maximum of rdisp/rfc_max_own_used_wp work processes.

Transaction SARFC is used to monitor the resources on all servers in the SAP system. This is described in the section Monitoring RFC Resources on the Application Server.