How To Stop an SAP Application Server

If the SAP component is offline, the plan will complete successfully without any further action. If the SAP component is not offline, the plan stops the SAP component.

If a normal stop fails and the user has selected the Force Stop option, the plan will perform a hard stop by killing the main process. The plan then verifies that the SAP component is offline. If it is, the plan completes successfully. If the SAP component is not offline, the plan fails. The processes used to determine the status follow:

• main dispatcher

• two dw processes which are children of the main dispatcher process

If the SAP Application Server is installed with the central script to start and stop it, then the plug–in stops the application server instance by using the central SAP script, as the following:

stopsap r3 Dinstance-num_logical-host

If the SAP Application Server is installed without the central script, then the plug–in stops it by using the following script in the home directory of user sidadm:

stopsap_Dinstance-num_logical-host

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the Application Server section of the SAP Tasks page, click Stop.

3. Click Run.

4. Select the target host or target host set.

5. Provide the plan variables.

   InstallPath of the SAP application server component to stop

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

   Force stop SAP application server after the graceful stop failed in the default environment

   This option is selected by default.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.