Windows NT Start Profile 

The start profile determines which actions the R/3 service executes. The profile can start all processes which are required by the R/3 System in this Windows NT host system. The start profile used by the service is specified when you install the service.

Start profiles are stored in the central profile directory of your R/3 System so that they can be called from any application server.

A start profile is generated automatically during system installation.

 

A distinction is made between processes started synchronously and asynchronously.

The next step in the start profile is not processed until the process has been completed. The system does not check how (that is with which Exit Code ) the process was completed.

Synchronous processes can be recognized by the addition immediate in the start profile.

Program strdbs.cmd - starts the database

Program sapcpe - copies the necessary executables to the application server.

The next step in the start profile is processed as soon as the process has been started.

Program msg_server.exe - starts the message server

Program disp+work.exe - starts the dispatcher

Program gwrd.exe - starts the gateway (provided this is just a gateway instance)

 

Changing or Replacing the Windows NT Start Profile

You can change entries in the start profile using the CCMS, for example. Changes to the start profile do not become effective until you have stopped and restarted the R/3 service. Note that when the R/3 service is stopped, the appropriate R/3 System is also stopped but not the database.

In the Microsoft Management Console, you can activate the new profile settings by restarting the R/3 start service without stopping the R/3 System. For more information see Microsoft Management Console: Windows NT.

To stop an R/3 service:

If you want to start an R/3 instance under another start profile, you must de-install the R/3 service and reinstall it.

 

See also:

Start and Shutdown Processing under Windows NT