Distributed Processing of Updates
Use
The update server has the task of distributing update requests (equally) to the various update work processes.
The update server, therefore, acts as an intermediary which receives update requests and distributes them to update work processes.
Each SAP application server that contains update work processes provides the update service.
Update distribution can be deactivated and configured using parameters in the SAP system profile. More information can be found in section System Profile Parameters for Updates or in the update profile parameters in transaction RZ11 (use the search string rdisp/vb* in RZ11 to search for the parameters).
In the profile of every SAP instance, you can define how update requests for this instance are processed. The options are as follows:
-
Update requests are distributed across the available update servers (Update Dispatching with Load Distribution).
-
Updates are processed by just one update server (update dispatching deactivated and rdisp/vbname set).
-
Updates are distributed within the update group that belongs to the instance (Configuring Update Groups).
Types of Update Work Processes
There are two types of update work processes, one for V1 updates (displayed as Update Processes in transactions SM50/ SM51) and one for V2 updates (displayed as Upd2 in transactions SM50/ SM51).
The V2 type is optional. This is intended for relieving performance problems in time-critical V1 updates by separating the processing of V2 update components. (V2 update components are typically statistical data and therefore less time-critical. If there is no V2 work process, both types of update components are processed in the V1 work process. If collective runs are updated, V2 work processes are also used.