Skip to Content

I was very excited, when I read about dynamic work process switch capability of Netweaver 7.0 EHP2.

Many times deadlock situation occurs in SAP system because work processes are busy and not available for new task.

In earlier version of NetWeaver intervention from basis administrator was required to handle such situation, but from Netweaver 7.0 EHP2 onwards systems itself handles deadlock situation.

System keeps some reserve process to handle deadlock situation and dynamically checks the work process availability.  If deadlock situation occurs, system first tries to use reserved dialog work processes or dynamically start process of required type. The changes to server are reset as soon as deadlock no longer exists.

 

image

 

 

 

 

 

Following parameters are important for configuring dynamic work processes:

 

 

Rdisp/dynamic_wp_check

This parameter check with dispatcher if dead lock situation occurs

rdisp/wp_max_no

Maximum number of work processes that server can start

Rdisp/wp_no_restricted

Number of work processes that are available to process specific task

rdisp/configurable_wp_no*

Define how many work processes of type dialog, background, update, spool can be activated by operation mode

rdisp/max_dynamic_wp_alive_time

Define alive time of dynamic work process

Finally SM50 work processes table looks like as follows:

 

image

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply