Dailog Work Process

The objective of the Dialog work process is to handle the user request quickly and display results back to the user.

Dialog work process relatively takes large number of resources relatively to back ground process so it is wise to have more number of Dialog work process running for each user logged in.

A Dialog work is not assigned to a single user for long amount of time.

When a Dialog user fires a request, the dispatcher assigns a Dialog work process to handle the request.

When user request is processed, it relives the work process from that user so that other users can use it.

Dialog work processes are multiplexed to handle large number of user request.

We require minimum 2 Dialog work process for each and every SAP system.

To process any user request one Dialog work process will take around 75-150 MB of memory.

Profile Parameters related to Dialog Work Process:

1)    abap/heap_area_dia: Heap memory quota for dialog work processes

Specifies how much local process memory (heap, malloc) a single dialog work process may allocate. The aim is to limit the size of a user context if necessary.

Default :  2,000,000,000 (2 GB)

2)    abap/heap_area_non-dia: Heap memory quota for spool / background / update work processes

Specifies how much local process memory (heap, malloc) a single non-dialog work process (update, spool, background work process) can allocate. The aim is to limit the size of a user context if necessary.

Default : 2,000,000,000 (2 GB)

3)    rdisp/async_dialog_timeout: timeout for asynchronous dialog RFCs

Default value: 120000 milliseconds

4)    rdisp/wp_no_dia: Number of Dialog work processes

Number of work processes that are available for processing tasks of interactive users. The number of work processes is not however fixed for the total life of the application server, but can be dynamically changed by operation mode switching.

            Default value: 2

            Valid entries, formats, areas: 2 – 100

5)    rdisp/max_wprun_time: maximum work process run time.

This parameter limits the maximum runtime of a process step within a dialog process. This ensures that dialog processes are not blocked by programs with long runtimes which hinder online operation. After the maximum runtime has expired, the program terminates in two stages:

·         If the program is currently executing ABAP commands, the ABAP processor terminates the program.

·         If the program is hanging in an external command, such as SQL, the entire work process is terminated after a second time period of a maximum of 60 seconds, and the user context is reset after the process restart.

Default value: 600 seconds