Scribd
Upload
8 views10 pages

Work Process Overview

The document provides an overview of various work processes in a system, including Dialogue, Background, Update, Enqueue, Message, Gateway, and Spool Work Processes. Each process has specific functions, monitoring methods, and parameters for configuration. The document also outlines the status of jobs and processes, as well as the importance of load balancing and connectivity between application servers.

Uploaded by

amohammedasad212
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views10 pages

Work Process Overview

The document provides an overview of various work processes in a system, including Dialogue, Background, Update, Enqueue, Message, Gateway, and Spool Work Processes. Each process has specific functions, monitoring methods, and parameters for configuration. The document also outlines the status of jobs and processes, as well as the importance of load balancing and connectivity between application servers.

Uploaded by

amohammedasad212
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

WORKPROCESS overview:

These are monitored by using various options

1.DPMON

2.In OS level using commands

3.by using TCODES

4. by using MMC

They are few work processes:

1.DIALOGUE WP

2.BACKGROUND WP

3.UPDATE WP

4.SPOOL WP

5.GATEWAY WP

6.MESSAGE

7.ENQUEUE

8.ICM

1.DIALOGUE WORK PROCESS:


This is the only work process which is communicate with end user.
The average response time is 600ms
It serve around 5-10 users
It requires 75- 300 mb later 7.3 upto 1 GB

Sum of dialogue wp should be greater than other non dialogue wp


Parameter to configure rdisp/wp_no_dia=1
Wp is not restricted to user and user is not restricted to wp so it do multiplexing
Status of wp are running,stopped,waiting,on-hold,ended

We can see in t-code of sm50/dpmon


2.BACKGROUND WP:
This processes is used because those jobs will take more time. That
can be scheduled in background operation
This process is not restricted to time it take minutes hours days
weeks months
Standard house keeping jobs are scheduled in SM36
Parameter is rdisp/wp_no_btc.
We can monitor scheduled jobs in SM37
Monitoring jobs in SM37

Jobs status are


SCHEDULED,RELEASED,READY,ACTIVE,FINISHED,CANCELLED
3.UPDATE PROCESS:
Update Process is used to Update the Database. when more then one
transactional Dialog steps are involved in a Transaction Then Dialog
Updates them in Temporary tables which are updated into Main
tables by Update Process based on Update Modules.
Local Update: The Dialog Process Updates the Database main tables
directly, if there are few transactional dialog steps.
Background Process communicates directly with the database and
updates the Data.
A synch Update: The Process of updating the temp tables by a dialog
process until a commit/roll back is made.

Synch Update: Once all the Transactional Dialog steps are committed
in the Temp tables then they are updated into Database Main Tables
Synchronously. Synch Updates are performed by a dedicated Update
Process.

We have V1,V2,V3.
V1: CRITICAL UPDATES-high priority
V2: NON-CRITICAL UPDATE – low priority

4.Enque Process:
it is used to lock and unlock the Objects during an update. These
locks are displayed in SM12 and Held for longer hours until the
transaction is committed or roll back.
Enque Processes are configured by parameter rdisp/wp_no_enq=1.
Generally One Enque Process for system is sufficient,more then one
may be required in a massive update system.
The Lock table size on the memory ranges between 4mb to 100
mb(256 mb in the Netweaver 7.3 Systems)

It is defined by parameter enque/table_size=4mb to 256 mb.(NW


7.5)
For 4mb of enque table size the Number of
lock/owners/objects/arguments can be restricted up to 3715.

Enque Dead Locks:


Due to Modularity between the modules it is possible to lock the
same LUW from Different Modules.
User-A User-B
Transaction-1 Transaction -2
a+b=x(sugar) c+d=e(milk)
m+n=o (tea) t+r=a(coffee)
c+d=e(milk) b+e=l
z+x=c a+b=x(sugar)
Transaction-1 is waiting for a lock that is held by Transaction-2
(c+d=e).
5.MESSAGE SERVERS:
It is used to perform load balancing/failover when more then one
Application Server serving the same Group are Configured.
There will be only one Message Server for the Entire System.
TCODE for message server is SMMS
it is the First Process(server) to be started on a Hostname, IPAddress,
Internal Port for communication between applications servers
External port for load balancing
This log file is displayed in
/usr/sap/SID/DVEBGMS00/work/dev_ms(AL11/ST11 Transaction)
Define a Logon Group in SMLG and assign to the Instances which are
going to Participate in Load Balancing.
6.GATEWAY WP:
Gateway Process:
it is the process that is not displayed in SM50 along with Message
Server. Enque Server is also not displayed in SM50 from Netweaver
7.3.

it is used to establish the connectivity between Processes of different


Application Servers and External Programs.
By Default There will be only one Gateway installed for each SAP
System Application Server.
it is not possible to increase the gateway processes,instead
Additional Gateway Servers can be installed based on requirement on
a separate Instance Number.
This is Required on non-sap systems Generally the Installed Gateway
which comes along with SAP Installation is sufficient to handle the
load.
Gateway Process is Monitored in SMGW.
Gateway Connection details are used while defining RFC Connections
in SM59
Gateway host(Name of the Application Server) Gateway
Service(sapgw00).
Note: Generally No issues occurs with SAP Gateway Service Except
max Connections reached(SM21/ST22).
Gateway parameters:
gw/max_conn=500(Maximum Number of active Connection which
increased upto 4092)
gw/keepalive=300(Timer for check unused connections and
disconnect)
gw/timeout=10000ms(Timeout for connecting to other gateways)
gw/max_sys=2000
gw/max_overflow_size=25000000

SPOOL WP:
it is the Only Process that is used to output the documents to a
Printer,fax,email etc..
Spool Work Processes are created by using parameter
rdisp/wp_no_spo=1
it is possible to configure more then one spool work process based
on available resources. (300mb per process)
SP01- new spool requests,

SP02- old and new spool requests


SMICM: The ICM monitor (transaction: (SMICM) is used to monitor
and administrate the Internet Communication Manager, which sends
and receives requests to and from the Internet. The Internet
Communication Manager is running on the application server
instance. .

You might also like