SAP CONTENT

Gateway Process is Monitored in SMGW. It listens on Port 3300.Secured gateway listens on port 4800. 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 occur with SAP Gateway Service Except max Connections reached(SM21/ST22). Gateway parameters: gw/max_conn=500(Maximum Number of active Connection which increased up to 4092) gw/keepalive=300(Timer for check unused connections and disconnect) gw/timeout=10000ms(Timeout for connecting to other gateways) Gateway Proces is monitored in SMGW–>Menu–>Go to–>logged on Clients it displays the currently connected clients. By Default, a Gateway Connection for Application Server and IGS(Internet Graphics Server) are established. IGS Server is installed by default to provide the Graphics Services. Installation of Additional Gateway Servers: Use SAP Installation Master Software/SWPM Select Gateway Inst...

It is used to perform load balancing when more than one Application Server serving the same Group are Configured. It is also used to obtain the locks for Additional Application Server Processes.It is the First Process(server) to be started on a Hostname, IP address, Hardware Key(Customer key), Internal Port for Locking 3900, an External port for load balancing 3600 and HTTP port 8000(8100) etc.This log file is displayed in /usr/sap/SID/DVEBGMS00/work/dev_ms(AL11/ST11 Transaction) It is monitored by using SMMS. it displays the types of services configured on each Application Server(DIA, BTC, UPD, SPO, ICM) Enqueue Server and Message Server are installed together in a separate Instance with instance number from Netweaver 7.3 which is referred as ABAP SAP Central Service(ASCS) Precisely Message Server is used for Login Load Balancing/Fail over(This is required only when more than one Application Server for the same purpose(group) are deployed). Obtaining Locks for Appli...

Spool Process: 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 risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...

Update Process is used to Update the Database.when more than one transnational Dialog steps are involved in a Transaction Then Dialog Updates them in Temporary tables which are updated into Main tables by Update Process. When Ever a Direct Update is performed on the Database then rollback is not possible. 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.Background Process Updates all the transactional dialog steps in one go into the Database main tables. Synch Update: Once all the Transactional Dialog steps are committed to the Temp tables then they are updated into Database Main Tables Synchronously. Synch Updates are performed by a dedicated Update Process. Asynch Update: the Process of updating the temp tables by a dialog process until a commit/roll back is made. Update Processes(TYPES): There are three types of U...

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 rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...

1.The Programs which are timed out due to restriction of time,i.e long running programs,time consuming programs,periodic jobs and memory expensive programs are defined(scheduled) to run in the background mode during off peak hours. Background Process handles the entire transaction in one step. it is dedicated to the user task and waits until the task is completed.The background process could not be timed out due to the process timeout parameter.it may run for minutes, hours and days.Background processes may be thrown out of the system due to memory issues. Standard SAP House Keeping jobs are scheduled in SM36. Standard Jobs–>Default Scheduling. Standard SAP DB House Keeping jobs are scheduled in DB13. Customer background jobs can be defined in SE38/SA38 or from any Executable Transaction. Background Process Flow: 1.A User Submits a Request to execute an expensive program. 2.The Dialog Process handles the Request and Stores them in the TBTC* Tables TBTCP—Program th...

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...