RKS - Timeouts

To enable a trouble-free RKS procedure with minimal inconvenience to system users, you have to consider carefully the values of RKS timeouts. The instances should be started separately one after the other. Only once an instance has been successfully started, should the next instance be started.

During the RKS procedure the system instances are started separately one after the other. To ensure that no requests or data are lost when an instance is closed, the soft shutdown function is used. When the RKS procedure is started, two timeout values can be set that are closely connected to the soft shutdown timeouts.

Soft Shutdown Timeout

The value of soft shutdown timeout determines the time after which running programs are terminated. In SAP MMC this value is preset with the value of the profile parameter rdisp/shutdown/max_time. The profile parameter specifies the maximum time for the soft shutdown. The greater the value, the more time is given in soft shutdown to operations still running. A large value results in less terminations, but possibly to longer runtimes of the RKS procedure.

Start Wait Timeout

The value of start wait timeout determines the wait time until the next instance is restarted. If this value is set too small, multiple instances in the system may not available during the RKS procedure. In SAP MMC this value is preset with a bigger value than the value of profile parameter rdisp/server_startup/max_time. This ensures that the RKS does not continue with the restart of the next instance until the application server restart procedure is completed.