STARTUP MECHANISM

Startup Mechanism:
  1. sapstartsrv is an executable(library) that starts as a service in windows or as /usr/sap/services in Linux Environments.
  2. Startsap start the Database Instance along with all the associated central and dialog Instances.(Primary and Additional Application Servers)
  3. startsap r3 starts only the Application Servers. startdb script is used to start a database.
  4. Database is started by using command ‘startdb’ and writes logs into startdb.log,stderr0,stderr1…..Check the Database traces in /oracle/SID/saptrace/background/alert<SID>.log
    from 12C /oracle/SID/………………..
  5. Copy Kernel executables using command ‘sapcpe’.
    sapcpe is an executable/script that is used to copy the kernel from shared/Global Directory to local directory.
    i.e /sapmnt/SID/exe to /usr/sap/SID/DVEBMGS00|D01/exe
    i.e /sapmnt/SID/exe to /usr/sap/SID/ASC01|SCS01/exe
    it writes the log files into sapcpe.log
  6. Starts the Message Server by using executable/script ‘msg_server(exe)’ and writes logs into dev_ms
  7. Starts the Dispatcher by using executable/script ‘disp+work(exe)’ and writes logs into dev_disp
  8. Starts the workprocesses by using executable/script ‘disp+work(exe)’ and writes logs into dev_w0,w1,w2,w3,w4..wn-1
The Other Processes like gateway, Internet Communication Manager, HostAgent, Internet Graphics Server are started and writes the logs into the home directory of SIDADM and work Directory.

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

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...
Read more

ENQUEUE WORK 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 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...
Read more

DIALOG PROCESS

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 ...
Read more