The following procedures install, uninstall, and manage the SAP Application Server.
How To Check the Online Status of an Application Server Instance
How To Check the Offline Status of an Application Server Instance
This task creates an SAP Application Server entry in the SPS database.
This task is a markOnly task.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Create.
Click Run.
In the Plan Parameters table, select the variable settings for the AppServer component.
If the variable settings have been created for this component, select the appropriate settings from the drop-down menu.
If the variable settings are not available from the drop-down menu:
Click Select From List.
The Select Variable Settings From List window displays.
To create a new variable settings set, click Create Set and type a Set Name.
The following list provides commonly updated variables for the AppServer component. To create a value for the component variable, click the check box in the component variable's row.
For information about component variables ending in UserExit, see User Exits.
This is a required field.
In the Sun Cluster environment, the groupName must equal the Sun Cluster resource group name.
A description of the group.
Required for the Sun Cluster environment.
Identifies whether this component will be deployed to a default, Sun Cluster, or SAP AC environment. Value can be ac, sc, or default.
Identifies the installer of the component.
Required for default install only. This value names the Central Instance logical host.
Required for the default environment. This value names the Application Server logical host.
Required for the default environment. The SAP system ID consists of three uppercase alphanumeric characters. The first character must be a letter.
Required for the default environment. Application Server instance number. Generate from variable input.
Application Server instance size which is generated from variable input. Possible values are small, medium, or big. Default value: medium.
Required for the SAP AC environment. The service ID of the SAP Application Server instance (only applicable in the SAP AC environment).
The Solaris Resource Management (SRM) project name. Default value: default.
Required for the default environment. The Central Instance name (as in the SAP Central Instance start profile).
Required for the default environment. TRUE means the central scripts are used to start and stop the application server. FALSE means instance–specific start and stop scripts from the SAP user home directory will be used to start and stop the application server. Default value: TRUE.
Click Save.
To use component variables from another component, click Import Set.
For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.
Select the target host or target host set.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.
This task deletes an SAP Application Server entry from the SPS database.
This task is a markOnly task.
In the Common Tasks section of the Sun N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Delete.
Click Run.
Select the target host or target host set.
Provide the plan variable.
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.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.
Prior to starting the SAP Application Server, the plug-in does not check any dependencies. After the startup, the plug-in verifies that the main processes are running. The main processes for the SAP Application Server are:
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 starts the application server instance by using the central SAP script like the following:
startsap r3 Dinstance-num_logical-host |
If the SAP Application Server is installed without the central script, then the plug–in starts it by using the following script in the home directory of user sidadm:
startsap_Dinstance-num_logical-host |
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Start.
Click Run.
Select the target host or target host set.
Provide the plan variables.
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.
This option is required when the target host does not meet the SAPS requirement to start the SAP instance. See the SAP Installation Guide for the minimum requirements for starting the SAP instance.
This option is only applicable in the SAP AC environment.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.
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 |
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Stop.
Click Run.
Select the target host or target host set.
Provide the plan variables.
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.
This option is selected by default.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.
When executing this task, the Hosts Where Installed table is displayed with entries for each SAP Application Server installation.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click View All.
The Hosts Where Installed table is displayed.
If the main processes are present on the system, the resource is considered online. If any of the main processes are not present on the system, the plug-in identifies the resource as offline.
SAP AC is not supported.
The main processes are:
main dispatcher
two dw processes which are children of the main dispatcher process
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Online Status.
Click Run.
Select the target host or target host set.
Provide the plan variable.
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.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.
If the main processes are present on the system, the resource is considered online. If any of the main processes are present on the system, the plug-in identifies the resource as not offline. If none of the main sap processes are present on the system, the plug-in identifies the resource as offline.
The main processes are:
main dispatcher
two dw processes which are children of the main dispatcher process
SAP AC is not supported.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server section of the SAP Tasks page, click Offline Status.
Click Run.
Select the target host or target host set.
Provide the plan variable.
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.
Click the Run Plan (Includes Preflight) button.
The Deployment Results page is displayed. If the plan fails, error messages are displayed.