You can optimize the configuration of your SAP system for the purposes of working with parallel RFCs.
To use parallel RFCs effeciently, your system has to be configured accordingly and must meet 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, upd, up2, 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
A range of profile parameters is available for resource distribution during the processing of parallel RFCs.
rdisp/rfc_check
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_time
For more parameters to do with RFC, open transaction RZ11 and search for isp/rfc*.
Note that the parameters rdisp/rfc* only apply to the above-mentioned RFC types, and not to any other types, such as synchronous RFC or asynchronous RFC without a group.
In other words, the parameters only apply to qRFC and parallel RFC.
The standard values for the quotas are restrictive, since you must assume that dialog users are also active in the system and they are given priority. You can set the maximum resources for RFC users as follows.
rdisp/rfc_max_login = 100
rdisp/rfc_max_own_login = 100
rdisp/rfc_max_own_used_wp = 100
rdisp/rfc_max_comm_entries = 100
These can of course affect the response time for dialog users.
No comments:
Post a Comment