Start and Shutdown Processing under Windows NT 

Start Processing

  1. Start the R/3 services.
  2. When the Windows NT system is booted, the R/3 service ( SAP<SAPSID>_<Instance number> , e.g. SAPC11_00 ) is always started automatically. The service evaluates entries from the Windows NT Start Profile and reads the necessary environment variables from the registry.

  3. Start the R/3 processes.

You can start the R/3 processes using the Microsoft Management Console (MMC). To do this, select an instance and choose Start from the context menu. For more information, see Microsoft Management Console: Windows NT.

DCOM communication is set up with the R/3 service and messages for starting the appropriate R/3 instance are sent to the service. The R/3 service interprets the Windows NT start profile (see the section Evaluating the start profile below) and starts the processes the instance consists of (the processes are started by the program sapstartsrv.exe ).

The message for starting the appropriate instance can also be issued by the command line program sapstart.exe .

The following diagram illustrates the interaction of the individual processes in the start procedure:

See also:

Registry Entries

Windows NT Start Profile

SAP Service Manager

Windows NT: R/3 Program Overview

Evaluating the Start Profile

When you start an instance, the R/3 service executes all commands in the Windows NT start profile that have an Execute_ statement.

The R/3 service then starts the processes of the R/3 instance in the order in which the Start_Program_ statements are listed in the profile.

It is possible to set the parameter autostart = 1 in the Windows NT start profile. If this parameter is set, the R/3 service and the R/3 System are started when the Windows NT system is booted. Bear in mind, however, that the individual processes are not synchronized automatically. This means, for example, that the administrator must ensure that the application servers are not started until the database server has been started successfully.

Shutdown Processing

The R/3 system can be stopped as follows:

The R/3 service waits for a stop message from the MMC or a command line program (for example, sapsrvkill ). It then stops the R/3 System as described in the section Evaluating the Start Profile. The service itself is not stopped.

From the list of services, select the service of the R/3 instance ( SAP<SAPSID>_<Instance number> , for example SAPC11_00 ) you want to stop. The R/3 service then stops the R/3 System as described in the section Evaluating the start profile. The service itself is then stopped.

The database is not stopped in this shutdown procedure.

Evaluating the Start Profile

The R/3 service executes stop commands for the R/3 processes it has started itself. Only those processes started with Start_Program_ statements are stopped. Processes started with Execute_ statements are not taken into account.

The R/3 service logs the start and shutdown of the R/3 System. You can display this log, for example, from the SAP Service Manager. For further information on error situations, see R/3 System on Windows NT: Problem Analysis.

The R/3 System can also be started and stopped using appropriate scripts.

The processes under which these scripts are started (for example, at schedule service) may not be started under the user ADMINISTRATOR or with the SYSTEM Account. In the following you will find examples of these scripts. The variables (name of the R/3 System, names of the instances…) still need to be adapted to the specific R/3 System:

Example: Script for Starting the R/3 System

Example: Script for Stopping the R/3 System

Example: Script Using DCOM Interface

 

See also:

Starting an R/3 System: Windows NT

Stopping an R/3 System: Windows NT

R/3 System on Windows NT: Problem Analysis