SAP Library - Find your answers

Go to transaction code rz04 then button Operation Modes / Instances. Then select the Operation mode and double click on it. Then you will see a window with no of Background work process. In the field named Class A increase the no to 1 (use the + button to increase that). Default value is zero. Then click on the save button to save the configuration

Dialog Work process(D) :- Used by frontend users or frontend process every dispatcher requires at least two dialog work processes

Backgorund Work process (B) : Used for long running Jobs .At least two for each R/3 system (more than one allowed for each dispatcher)

Enqueue Work process (E) :Used for Locking /Unlocking purposes. Only one enqueue work process is needed for each system

Update work process (V1) : Used for critical updates into Database at least one for each R/3 System (more than one allowed for each dispatcher)

Update workprocess (V2): Used for normal updates after critical updates

Gateway work process (G) : allows communication between R/3, R/2 and external application systems.

Spool work process (S) : Used for Printing from SAP at least one process

Message Service (M): Used for messaging purpose. The message server (MS or M) communicates between the distributed dispatchers within the R/3 System and is therefore the prerequisite for scalability using several parallel-processing Application servers.

Dialog Work process(D) :- Used by frontend users or frontend process every dispatcher requires at least two dialog work processes

Backgorund Work process (B) : Used for long running Jobs .At least two for each R/3 system (more than one allowed for each dispatcher)

Enqueue Work process (E) :Used for Locking /Unlocking purposes. Only one enqueue work process is needed for each system

Update work process (V1) : Used for critical updates into Database at least one for each R/3 System (more than one allowed for each dispatcher)

Update workprocess (V2): Used for normal updates after critical updates

Gateway work process (G) : allows communication between R/3, R/2 and external application systems.

Spool work process (S) : Used for Printing from SAP at least one process

Message Service (M): Used for messaging purpose. The message server (MS or M) communicates between the distributed dispatchers within the R/3 System and is therefore the prerequisite for scalability using several parallel-processing Application servers.

Keyword: BASIS
Title : J2EE Engine : Restarting a Single Process

Symptom

Corrective action

Increase the swap space or decrease the R/3 Extended Memory.

If necessary, increase the roll area.

Check if the maximum process size (operating system parameter) is sufficient.

See: Swap Space Bottleneck During R/3 Operation

Keyword: BASIS
Title : Virtual Address Space of a Work Process

Step by step process on how to upgrade the kernel

"Updating the Kernel: Make sure you have at least 200MB of free disk space on the SAP instance before doing a Kernel update. The following steps illustrate how to update the Kernel on a central instance:

1. Download the latest Kernel patch into a temporary directory in your system or network share.

2. Unpack the patch using SAPCAR.exe. First, change to the directory you downloaded the patch into and then run SAPCAR –xvf .

3. Stop the SAP central instance and the SAP services.

4. Back up all existing files in the Kernel directory (usr/sap/sid/sys/exe/run). This way, you can easily recover the old Kernel in case of problems with the new one.

5. Copy the new Kernel files into the run directory.

Use

This value specifies the memory amount in bytes. When this amount is exceeded, a work process is restarted after executing a dialog step.

In a work process, heap memory (malloc) can be allocated for a user context. See Allocating Memory for User Contexts and Private Memory. If a user context releases this memory again, it still remains reserved by the process (compared to the operating system), and is only available for other processes if the process itself has ended.

The following chart illustrates this situation using the example of a dialog work process.

Goal:

As few restarts of work processes as possible, but swap space bottlenecks may not occur. The local memory allocated by the work processes has to be released again.

As depicted in the graphic, the value of abap/heaplimit should be smaller than abap/heap_area_dia or abap/heap_area_nondia, so that the dialog step that is running can still be executed. This prevents the work process from working against the operating system’s swap space limit if there is a programmed termination of the work process.

To determine how many work processes are restarted, use the CCMS (transaction RZ03). Note that the column Err in the work process display (transaction SM50) does not refer to work processes that are restarted.

Unit: Bytes

Default value: 40000000 (40 MB)

Recommended value: 20000000 (20 MB); recommended area: 10000000... 50000000 (10 MB... 50 MB)

You can get the values from the configuration examples (Contents button).

Changes: The customer can make changes.

Keyword: BASIS
Title : Java Instance – Server Process

1. The way in which you proceed here depends on whether or not the applicant has been assigned to a vacancy.

If the applicant	Choose	The following screen appears:
Has not been assigned to a vacancy	Applicant master data ® Bulk processing ® Receipt of application	Applicants by Action
Has been assigned to a vacancy	Applicant master data ® Bulk processing ® Vac.assignment list	Vacancy Assignments

2. Enter any relevant selection criteria, and choose Program
® Execute.




If you enter 1 in the Status (overall) field, the system only lists applicants whose overall status is already In process.

A second Applicants by Action or Vacancy Assignments screen appears.

3. Select the applicant you want to set to In process and choose Edit
® Change overall status.

The Change Overall Status dialog box appears.

4. Enter 1 (for In process) in the Overall status field, and choose Continue.

Result