Installation of the Standalone Enqueue Server
If you want to use the standalone enqueue server, you must install an ABAP central services instance (ASCS instance) in your SAP system. If you want a high availability system, you can also configure the enqueue replication server, which runs on the enqueue replication server instance (ERS instance).
Installing ASCS and ERS Instances
To install the ASCS instance (standalone enqueue server and message server) and the ERS instance, you use the installation program Software Provisioning Manager. This is the successor to the installation program SAPinst. For more information, see the installation guide.
To open the installation guide, proceed as follows:
-
Open the SAP Support Portal Home page (https://support.sap.com
). -
In the navigation bar, choose .
-
On the Software Logistics Tools (SL Toolset) screen, in the section System Provisioning, choose Install a System using Software Provisioning Manager.
-
In the section Installation Option of Software Provisioning Manager 1.0 SP 23, choose Installation Guides - Application Server Systems.
-
This takes you to a dynamic table on an SAP Help Portal page. Filter the table by your operating system and database.
-
You can download the relevant installation guide in PDF or HTML format.
Post-Installation Checks
After installing the standalone enqueue server and the enqueue replication server, you should carry out some tests to ensure that the replication server is running correctly.
The procedure for UNIX platforms is described in the section Replication Server: Check Installation. You can find the post-installation checks for Windows in the installation guide.
Start and Stop Order
They must be shut down and restarted in the correct order.
Stop Sequence:
-
Stop the enqueue server
-
Stop the replication server
This ensures that the enqueue server does not receive any more requests if the replication server is no longer running, and therefore no requests can get lost.
Start Sequence:
-
Start replication server
-
Start enqueue server
This ensures that the replication server deletes its old replica first (that is, it cleans up its shared memory), and therefore avoids any unwanted replications.

