How to Stop an SAP Central Instance

If the SAP component is offline, the plan will complete successfully without any further action. If the SPS component is not offline, the plan stops the SAP component. If a normal stop fails and you have selected the Force Stop option, the plan will perform a hard stop by killing the main processes. 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 are:

• main dispatcher

• message server

• At least two dw child processes

The plug–in stops the SAP CI instance by calling the SAP script stopsap_DVEBMGS_instance-num–logical-host.

Steps

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

2. In the SAP Central Instance section of the SAP Tasks page, click Stop.

3. Click Run.

4. Select a target host or target host set.

5. Provide the plan variables.

   Install path of the Central Instance component

   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 Central Instance after the graceful stop failed in the default environment

   This option is selected by default. In SC and AC environments, the corresponding Sun Cluster command or SAP AC command is called to start the component.

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

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