Soft Shutdown in SAP Application Server
To ensure that no requests or data are lost when ending an SAP instance, use the soft shutdown function. A soft shutdown waits for transactions to be completed in a specific order. Some of these states have a timeout, which can be configured with profile parameters.
Some states have no timeout. Therefore, it cannot be guaranteed that the soft shutdown will terminate within a certain time span (sum of all timeouts).
The figure below shows the soft shutdown procedure.
The following overview describes the actions of the system in the various states.
State |
Description |
Can timeout be configured? |
|---|---|---|
CHECK_SERVER |
Check whether the server can be closed. Here the wait time cannot be configured. |
No |
CHANGE_STATE |
Switch state of server from active to shutdown. You can view this is transaction SM51. |
No |
WAIT_FOR_LOAD_BALANCE_UPDATE |
Wait until the RFC/HTTP clients no longer consider the server for calls with load balancing. The wait time is restricted by the rdisp/shutdown/load_balance_wait_time parameter. |
Yes |
DISABLE_EXTERNAL_LOGIN |
External logons (SAP GUI) are no longer permitted if profile parameter rdisp/shutdown/disable_login = ON is set. |
No |
DISABLE_SCHEDULES |
Deactivate internal scheduling (batch jobs, BG-RFC, QRFC) |
No |
WAIT_FOR_END_OF_LONGRUNNER |
Wait for the end of the long-runner (batch, update, and so on). The wait time is restricted by the rdisp/shutdown/longrunner_timeout parameter. |
Yes |
WAIT_FOR_END_OF_EXCLUSIVE_ACTIONS |
Wait for the exclusive actions to start. These are unique clean up actions in the SAP kernel and the ABAP runtime environment which are started when the shutdown starts. The wait to read ABAP actions can be configured by the rdisp/shutdown/trigger_timeout profile parameter. |
Yes |
WAIT_FOR_END_OF_SESSIONS |
Wait for the end of the active sessions. An automatic log off can be activated for online sessions by using the rdisp/shutdown/auto_logout profile parameter. |
Yes |
TERMINATE_PERIODIC_TASKS |
All kernel-internal periodic tasks (for example AUTOABAP, BUFFER-REFRESH) are no longer started |
No |
CLOSE_LISTEN_PORTS |
Close ports to GUI, RFC, and HTTP communication |
No |
WAIT_FOR_IDLE_WPS |
Wait until all work processes are in waitung status and there are no more requests in the dispatcher queue. The maximum wait time can be configured using the rdisp/shutdown/idle_wp_timeout profile parameter. |
Yes |
HALT |
Close instance and clean up resources |
No |