System Configuration for Parallel RFCs
Use
You can optimize the configuration of your SAP system for the purposes of working with parallel RFCs. This section describes the tools (profile parameters, transactions, and so on) you use to do this.
Prerequisites
To use parallel RFCs, your system has to be configured accordingly and must fulfil the following prerequisites.
More dialog work processes than non-dialog work processes have to be configured on every server that is available for processing parallel RFCs.
The profile parameter
rdisp/wp_no_<wptyp> uses <wptyp> = dia, spo, vb, vb2, btc to determine the number of work processes of one type. This number is not, however, necessarily the most up-to-date number, as the work process types can be changed while the server is in operation (by means of operation mode switching, for example). You can find out the current number of work processes in the Process Overview (SM50; see also
Display and Control Work Processes).
Procedure
A range of profile parameters is available for resource distribution during the processing of parallel RFCs. These parameters are described in the following sections:
rdisp/rfc_use_quotas rdisp/rfc_max_queue rdisp/rfc_max_login rdisp/rfc_max_own_login rdisp/rfc_min_wait_dia_wp rdisp/rfc_max_own_used_wp rdisp/rfc_max_comm_entries rdisp/rfc_max_wait_timeFor more parameters to do with RFC, open transaction RZ11 and search for
isp/rfc*.
Note that the parameters
In other words, the parameters only apply to qRFC and parallel RFC.
While manipulating the parameters, you can also dynamically change the aRFC resources. You could do this before running the application that uses a high volume of parallel RFCs.
To do this, use transaction SARFC, as described in the section
Dynamically Configuring RFC Quotas.