To guarantee high availability for your SAP System for all software and hardware components, use the standalone enqueue. The use of the standalone enqueue server means that the crucial enqueue server with lock table is kept as small as possible. Instead of the entire application server with enqueue work process and lock table, you have one slimline central instance consisting of the enqueue server and the message server only. Making this one central instance a high availability (HA) solution.
The standalone enqueue server provides the following benefits:
The enqueue clients (SAP application servers) and the enqueue server communicate directly. The work process has a TCP connection to the enqueue server.
You can implement the standalone enqueue server as part of the high availability enqueue server solution with replication server. The enqueue server is then more reliable.
SAP AC is not supported.
This section describes the following tasks:
This task creates an SAP Enqueue Server component in the SPS database. The SAP Enqueue Server is created by the user at the OS level outside of the SAP plug–in.
This task is a markOnly task.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Create.
Click Run.
In the Plan Parameters table, select the variable settings for the Enqueue Server 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 Enqueue Server 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.
This is a required field. The resourceName must equal the Sun Cluster resource name for the Sun Cluster envType.
This is a required field. Identifies whether this component is deployed to a default or Sun Cluster environment. Value can be default or sc. Default value: default.
Identifies the installer of the component.
Required for the default and Sun Cluster environment. The SAP system ID consists of three uppercase alphanumeric characters. The first character must be a letter.
Required for the default and Sun Cluster environment. The SAP Central Instance number consists of two digits.
Required for the default and Sun Cluster environment. The full path to the SAP Enqueue Server profile.
The signal used to stop the SAP Enqueue Server. Default value: 2
The Solaris Resource Management (SRM) project name. Default value: default.
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 a target host or a 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 Enqueue Server component in SPS database. The SAP Enqueue Server created by the user at the OS level will not be deleted.
This is a markOnly task.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Delete.
Click Run.
Select a target host or a 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 Enqueue Server, the plug-in does not check any dependencies. After the startup, the plug-in verifies that the main process is running. The main process for the SAP Enqueue Server is the enserver process.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Start.
Click Run.
Select a target host or target host set.
Provide 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 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 you have 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 offline, the plan completes successfully. If the SAP component is not offline, the plan fails. The process used to determine the status is the enserver process.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Stop.
Click Run.
Select a 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.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue 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.
The main process is the enserver process.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Online Status.
Click Run.
Select a target host or a target host set.
Only select one host.
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 not present on the system, the plug-in identifies the resource as offline.
The main process is the enserver process.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the SAP Enqueue Server section of the SAP Tasks page, click Offline Status.
Click Run.
Select a target host or a target host set.
Only select one host.
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.