UNIX / LINUX
Start
SAP Web Dispatcher
1)
Login from SIDADM
2)
Go to the profile directory
3)
F:\usr\sap\sid\SAPWEBDISP\sapwebdisp.pfl
4)
Execute below command.
5)
sapwebdisp pf=PROFILE-NAME
Stop SAP Web Dispatcher
1)
Login from SIDADM
2)
Find the process ID for SAP Web Dispatcher by
executing command ps -ef and grep the dev_webdisp_SID
3)
Kill the PID
Example:
ps -ef | grep dev_webdisp_SID
root 24498 1234 0 May
29 /usr/sap/../run/sapwebdisp pf=SID.pfl dev_webdisp_SID
Kill -2 1234
Windows
1)
You can start or stop SAP Web Dispatcher from
Windows Services or from Computer Management MMC
2)
Computer Management MMC - > Services - >
Stop sapwebdisp.
Although the SAP Web dispatcher
can run in any directory, we recommend that you install it in a separate
directory:
·
Windows: C:\Program
Files\SAP\SAPWebDisp
·
UNIX: /usr/sap/<SID>/sapwebdisp
Startup Shutdown logs
·
/usr/sap/TST/DVEBMGS00/work.
·
We can also view the file via transaction AL11.
Find and select Directory parameter DIR_INSTANCE, then drill down into this
directory…
2. Gateway Restart:
Gateway:
Gateway is a service which
enables SAP systems and external programs to communicate with one another. Each
SAP instance has a gateway.The gateway enables communication between work
processes and external programs, as well as communication between work
processes from different instances or SAP Systems.
Gateway consists of 2 processes.
1)
Gateway Read Process
2)
Gateway Monitor
Restart Gateway:
SMGW -> Goto
-> Expert Functions -> Soft/Hard Shutdown
Soft Shutdown:Soft shutdown terminates the gateway –the gateway
accepts no new connections and closes as soon as there are no more active
connections.
Hard Shutdown:The hard shutdown terminates the gateway immediately
(no checks made).
3. ECC System Startup and
shutdown
Stop Procedure:
A. Stop Application server running at dtc-sapecpa01
1)
Logon to dtc-sapecpa01 as ecpadm.
2)
ps –ef|grep ECP --- to check processes.
3)
stopsap
4)
ps –ef|grep ECP --- to check processes
5)
cleanipc <instance number> remove
B. Stop Application server running at dtc-sapecpa02
1)
Logon to dtc-sapecpa02 as ecpadm.
2)
ps –ef|grep ECP --- to check processes
3)
stopsap
4)
ps –ef|grep ECP --- to check processes
5)
cleanipc <instance number> remove
C. Stop Central Instance running at dtc-sapecp
1)
Logon to dtc-sapecp as ecpadm.
2)
ps –ef|grep ECP --- to check processes.
3)
stopsap
4)
ps –ef|grep ECP --- to check processes makes
sure ci, scs and db stopped.
5)
Cleanipc<instance number> remove
Start Procedure:
A. Start DB and Central Instance at dtc-sapecp
1)
Logon to dtc-sapecp as ecpadm.
2)
ps –ef|grep ECP --- to check processes.
3)
Startdb
-- Make sure you get success message.
4)
Startsap
-- Make sure you get success message.
5)
ps –ef|grep ECP --- to check processes to makes
sure ci, scs and db started.
B. Start Application server-1 at dtc-sapecpa01
1)
Logon to dtc-sapecpa01 as ecpadm.
2)
ps –ef|grep ECP --- to check processes.
3)
startsap
4)
ps –ef|grep ECP --- to check processes
C. Stop Application server-2 at dtc-sapecpa02
1)
Logon to dtc-sapecpa02 as ecpadm.
2)
ps –ef|grep ECP --- to check processes
3)
startsap
4)
ps –ef|grep ECP --- to check processes
Stop Procedure:
A. Stop Live Catche running at dtc-saplcp
1. Logon to
dtc-saplcp as lcpadm.
2. dbmcli -d LCP -u
control,password db_state -- Output of
this command should be: -
OK
State
ONLINE
3. dbmcli -d LCP -u
control,password db_offline --Output of
this command should be: -
OK
4. dbmcli -d LCP -u
control,password db_state -- Output of this command should be:
OK
State
OFFLINE
B. Stop Central Instance running at dtc-sapscp
1. Logon to
dtc-sapscp as scpadm.
2. ps –ef|grep SCP
--- to check processes.
3. Stopsap
4. ps –ef|grep SCP
--- to check processes makes sure ci, scs and db stopped.
5.
Cleanipc<instance number> remove
A. Start DB and Central Instance at dtc-sapscp
1. Logon to
dtc-sapscp as scpadm.
2. ps –ef|grep SCP
--- to check processes.
3. Startdb -- Make sure you get success message.
4. Startsap -- Make sure you get success message.
5. ps –ef|grep SCP
--- to check processes to makes sure ci, scs and db started.
B. Start Live Catche at dtc-saplcp
1. Logon to
dtc-saplcp as lcpadm.
2. dbmcli -d LCP -u
control,password db_state -- Output of
this command should be: -
OK
State
OFFLINE
3. dbmcli -d LCP -u
control,password db_online --Output of
this command should be: -
OK
4. dbmcli -d LCP -u
control,password db_state -- Output of this command should be:
OK
State
ONLINE
5. Message Server
Restarting message server after crash(nohup msg_server pf = profile name from sidadm)