
The most important profile parameters for configuring work processes are listed below:
Parameter Name |
Meaning |
Unit |
Default Value |
|---|---|---|---|
rdisp/configurable _wp_no |
Number of configurable work processes for operation mode switching. To enable the Dispatcher to resolve deadlocks automatically, five dynamic work processes are excluded from operation mode switching in the default setting: The number of configurable work processes is calculated from the value of profile parameter rdsip/wp_max_no - 5 dynamic work processes that are always reserved for handling a deadlock. This means that in the default setting the value of configured work processes (sum of all configured WPs + 5) and the value of configurable work processes (rdisp/wp_max_no - 5) is identical. If you increase the value of profile parameter rdisp/wp_max_no manually, you can increase the number of dynamic work processes too. If the number of dynamic work processes is higher than the default (= 5), the number of configurable work processes is also increased. Caution This parameter should have the default value. Only change the value in exceptional situations and after consulting SAP.
Example
Starting with the following configuration: rdips/wp_max_no = 30 rdisp/wp_no_dia = 20 rdisp/configurable _wp_no is set to the default value (rdsip/wp_max_no - 5 WPs for deadlock handling) This means that 20 dialog work processes and 10 dynamic work processes are configured. 25 work processes are configurable for operation mode switching (rdsip/configurable_wp_no). |
Whole number between 0 and 512, or DEFAULT |
( max( $(rdisp/wp_max_no) - 5, $(rdisp/wp_no_dia) + $(rdisp/wp_no_vb) + $(rdisp/wp_no_vb2) + $(rdisp/wp_no_enq) + $(rdisp/wp_no_btc) + $(rdisp/wp_no_spo) ) ) (rdisp/wp_max_no -5 WPs for deadlock handling) |
rdisp/max_dynamic _wp_alive_time |
Lifespan of dynamic work processes. Dynamic work processes are stopped as soon as deadlocks are resolved. If you are not processing a request, the work processes are stopped after this time interval. |
Seconds |
300 |
rdisp/wp_max_no |
Maximum number of work processes including those work processes created dynamically. Calculated from the sum of the following profile parameters plus five dynamic work processes:
If you want to configure more than five dynamic work processes, the value of parameter rdips/wp_max_no must be increased accordingly. |
Whole number between 2 and 512 (must be greater than the sum of all work process types) |
( $(rdisp/wp_no_dia) + $(rdisp/wp_no_vb) + $(rdisp/wp_no_vb2) + $(rdisp/wp_no_enq) + $(rdisp/wp_no_btc) + $(rdisp/wp_no_spo) + max( $(rdisp/wp_no_restricted), 5 ) ) (sum of all configured work processes + 5) |
rdisp/wp_no_btc |
Number of batch work processes (background processing). |
Whole number between 0 and 512 |
0 |
| rdisp/wp_no_dia | Number of dialog work processes. |
Whole number between 2 and 512 |
2 |
rdisp/wp_no_enq |
Number of enqueue work processes. |
Whole number between 0 and 5 |
0 |
rdisp/wp_no_ restricted |
Number of stand-by work processes. Stand-by work processes are kept free in normal operation and not used until the application server identifies a bottleneck and needs additional work processes to remove it. The difference between work processes restarted dynamically and stand-by work processes is that stand-by work processes are started when the application server is started. |
Whole number between 0 and 512 |
0 |
rdisp/wp_no_spo |
Number of spool work processes (printing). |
Whole number between 0 and 512 |
0 |
rdisp/wp_no_vb |
Number of V1 update work processes (time-critical). |
Whole number between 0 and 512 |
0 |
rdisp/wp_no_vb2 |
Number of V2 update work processes (not time-critical). |
Whole number between 0 and 512 |
0 |