Standalone Enqueue Server 2

11/13/2020
Standalone Enqueue Server 2

Generated on: 2020-11-13 19:32:52 GMT+0000
| 2020
PUBLIC
Original content: https://help.sap.com/viewer/cff8531bc1d9416d91bb6781e628d4e0/202009.000/en-US
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/viewer/disclaimer.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23146476&topics=902412f09e134f5bb875adb6db5… 1/22
11/13/2020

The Standalone Enqueue Server 2 is the successor to the standalone enqueue server. It is a component of the SAP lock concept
and manages the lock table. This principle ensures the consistency of data in an ABAP system.
 Note
As of AS ABAP Release 7.55 (ABAP Platform 2020), Standalone Enqueue Server 2 is no longer delivered. For more information
about which version of the standalone enqueue server is used in which release, see SAP Note 2630416 .
Use
Just like the old standalone enqueue server, the new Standalone Enqueue Server 2 runs together with the message server on the
ABAP central services instance (ASCS instance). The Standalone Enqueue Server 2 prevents multiple users from simultaneously
accessing the same data by using the lock table to hold all current user locks in the main memory.
Implementation Considerations
The new Standalone Enqueue Server 2 offers the following advantages:
Improved scalability
Advanced administration and monitoring options using transaction SMENQ
Simpli ed high availability architecture with the new replication mechanism and an improved failover process
Functions of Standalone Enqueue Server 2

The Standalone Enqueue Server 2 has the following functions:
Management of lock table
Execution of lock operations
Collision check for locks using the lock table
If there is a lock con ict, the Standalone Enqueue Server 2 rejects the requested lock operation.
There is no lock entry, Standalone Enqueue Server 2 performs the requested enqueue operation by and includes it in the lock
table. The lock table contains lock entries with the following information:
Lock owners
Lock mode
Lock mechanism
Name and elds (lock argument) of the locked table
 Recommendation
For the administration of the new Standalone Enqueue Server 2, you should use transaction SMENQ . You can nd more
information on the page: Administration and Monitoring of Standalone Enqueue Server 2 and Enqueue Replicator 2.
11/13/2020
Lock Modes
The following lock modes exist:
Shared lock (S lock): Multiple users have read access to the data secured by the S lock. ABAP users can request their S
lock multiple times since the lock is cumulated.
Optimistic lock (O lock): Multiple users have read access to the data secured by the O lock. ABAP users can request their
O lock multiple times since the lock is cumulated. If the data is then changed, the optimistic lock must be converted into an
exclusive lock. This invalidates optimistic locks of other users to the same data.
Exclusive lock (E lock): A user has read and write access to the data protected by the E lock. ABAP users can request this E
lock multiple times since the lock is cumulated. As soon as another ABAP user requests a lock to the same data, a collision
occurs.
Exclusive Non-cumulative Lock (X lock): A user has read and write access to the data protected by the X lock. ABAP users
can request this X lock only once at any one time since this lock is not cumulated. A collision occurs as soon as the user
requests a further lock on this data, or another ABAP user requests a lock on the same data.
 Note
A lock can be set multiple times (cumulation) except for an X lock. To do this, name, argument, and lock mode must be the
same. The cumulation counter is incremented by one with each successive cumulation, and reduced by one each time a lock is
released.
Lock Collisions
A lock collision occurs in the following cases:
An ABAP user is holding an exclusive lock (E lock) and another ABAP user requests read or write access to the same data.
If an ABAP user is holding an exclusive, non-cumulative lock (X lock), a collision occurs as soon as another ABAP user
requests read or write access to the same data.
An ABAP user is holding a shared lock (S lock) and another ABAP user requests a write access to the same data.
Processes of Standalone Enqueue Server 2

The following graphic shows the various processes of Standalone Enqueue Server 2.
11/13/2020
Each work process (WP) in an ABAP application server instance functions as an enqueue client, and opens a network connection
to Standalone-Enqueue-Server 2 using TCP. Here you have to specify in pro le parameters in the default pro le of AS ABAP at
least the host and instance number of ASCS instance.
For more information, see:
Request Processing in Standalone Enqueue Server 2
In Standalone Enqueue Server 2 incoming requests can be processed in parallel. Multiple threads are implemented for this. These
are started by the main thread. The watchdog thread accepts connection requests and puts them in a request queue. From there
they are passed to a free worker thread (WT).
The following les are stored on the server side:
Backup le: Standalone Enqueue Server 2 holds critical data in the lock table in the main memory: Locks that were passed
to the update system are stored both in the lock table and in a backup le. When Standalone Enqueue Server 2 is restarted,
the locks are read from the backup le and entered in the lock table. This ensure that update locks do not get lost if the
enqueue server is shut down.
Export le: Lock table is saved if there is a rolling kernel switch (RKS). Created automatically during an RKS before
Standalone Enqueue Server 2 is closed. When Standalone Enqueue Server 2 is restarted, this le is used to restore the lock
table with the existing lock entries.
Request trace Records requests that are sent to Standalone-Enqueue-Server 2. By default, the recording is not activated.
It can be activated or deactivated in ABAP transaction SMENQ. For performance reasons, the request trace should only be
activated if problems with request processing have to be analyzed. Afterwards you should deactivate the request trace
again.
11/13/2020
Event trace: Records important events happening in Standalone Enqueue Server 2, for example, Server started and
Server stopped.
Developer trace Trace entries of Standalone Enqueue Server 2.
Related Information
Installation of the Standalone Enqueue Server 2
SAP Lock Concept
High Availability with Standalone Enqueue Server 2

The usage of the new Standalone Enqueue Server 2 and Enqueue Replicator 2 provides an improved high availability architecture
with robust and fast replication, and failover.
Overview
If you want your system to become part of a high availability (HA) solution, you must use the Enqueue Replicator 2. Alternatively,
you can use the replication mechanism that is provided by an external library.
Replication with Enqueue Replicator 2

The High Availability Enqueue Server consists of the Standalone Enqueue Server 2 and the Enqueue Replicator 2 that run on
different hosts.
High Availability Enqueue Server
Each work process (WP) of an ABAP instance (enqueue client) has a separate connection to the Standalone Enqueue Server 2.
The Standalone Enqueue Server 2 uses several connections to the Enqueue Replicator 2.
For HA reasons and to prevent port con icts, the Standalone Enqueue Server 2 has to be running on the ABAP Central Service
(ASCS) instance and the Enqueue Replicator 2 on the Enqueue Replication Server (ERS) instance.
11/13/2020
When enqueue clients set (enqueue) or release (dequeue) locks, they make changes to the lock table of the Standalone Enqueue
Server 2. Each change made to the lock table is automatically replicated to the replication table of the Enqueue Replicator 2.
The Standalone Enqueue Server 2 sends the response to the client only when the Enqueue Replicator 2 has acknowledged a
successful replication.
Alternative Replication Mechanism

An alternative way to replicate the lock table of the Standalone Enqueue Server 2 is to use an external library. In this case, the
Enqueue Replicator 2 is no longer used.
This replication mechanism is only available for System z Cross Coupling Facility. For more information, see 1753638 .
Related Information
Con guration of the Enqueue Replicator 2
Failover
Failover
In an HA setup, if the old Standalone Enqueue Server failed, it had to be started on the host where the Enqueue Replication Server
was running. Due to an improved replication and failover process, both Standalone Enqueue Server 2 and Enqueue Replicator 2
enhance the high availability of the SAP lock concept.
Initial Con guration

The gure shows an example con guration of the ABAP Central Services (ASCS) and Enqueue Replication Server (ERS) instances.
The ASCS instance consists of Standalone Enqueue Server 2 and Message Server (not shown in the gure). The ERS instance
contains the Enqueue Replicator 2.
Configuration of ASCS and ERS instances
11/13/2020
Standalone Enqueue Server 2 and Enqueue Replicator 2 run on different hosts.
In the example, the Standalone Enqueue Server 2 is running on the physical host HOST1. It can be addressed by the virtual host
name ASCS_HA.
The Enqueue Replicator 2 is running on the physical host HOST2 and can be addressed by the virtual host name ERS_HA.
At one given point in time, the virtual host ASCS_HA is assigned to one of the physical hosts (HOST1, HOST2, HOST3, or HOST4).
The same applies for the virtual host ERS_HA.
Failover of the ASCS Instance

If there is a failover, the old Standalone Enqueue Server was required to "follow" the Enqueue Replication Server. That is, the HA
software had to start the ASCS instance on the host where the ERS instance is currently running.
In contrast to the old Standalone Enqueue Server, the new Standalone Enqueue Server 2 and Enqueue Replicator 2 no longer have
these restrictions. The Message Server, which is also part of the ASCS instance, behaves the same as the Standalone Enqueue
Server 2.
Failover of the ASCS Instance
If the Standalone Enqueue Server 2 that is running on HOST1 fails, the HA software starts the ASCS instance (including
Standalone Enqueue Server 2 and Message Server) on another host (for example, on HOST3).
The newly started Standalone Enqueue Server 2 then retrieves the replication table from the Enqueue Replicator 2 over the
network and uses it as the lock table.
The HA software ensures that connection attempts from clients are automatically directed to the ASCS instance that is running on
HOST3.
Failover of the ERS Instance
11/13/2020
Failover of the ERS Instance
If the Enqueue Replicator 2 that is running on HOST2 fails, the HA software starts it on another host (for example, on HOST4).
The newly started Enqueue Replicator 2 waits until the Standalone Enqueue Server 2 starts an initial transfer of the lock table.
The HA software ensures that connection attempts from the Standalone Enqueue Server 2 are automatically directed to the ERS
instance that is running on HOST4.

To use the Standalone Enqueue Server 2 and Enqueue Replicator 2, you have to install the ABAP Central Services (ASCS) and
Enqueue Replication Server (ERS) instances.
Installing ASCS and ERS Instances

The Standalone Enqueue Server 2 is part of the ASCS instance. The Enqueue Replicator 2 is running on the ERS instance.
If you are interested in the lock functionality of the Standalone Enqueue Server 2 without the replication mechanism, install only
the ASCS instance.
If you want your system to be an HA solution, install both the ASCS and the ERS instances. For the installation, use the Software
Provisioning Manager installation tool (installer), which is the successor to the SAPinst tool.
To nd more information about the installation of the ASCS and ERS instances that already include the Standalone Enqueue
Server 2 and Enqueue Replicator 2, see the installation guide as of release SAP NetWeaver AS for ABAP 7.52.
The following procedure describes how to download the installation guide:
1. Go the SAP Support Portal Home (https://support.sap.com ).
2. In the navigation bar, choose Tools Overview Software Logistics Tools .
11/13/2020
3. On the Software Logistics Toolset (SL Toolset) page, go to the System Provisioning section and open Install a System
using Software Provisioning Manager.
4. In Installation Option of Software Provisioning Manager 2.0 SP 00, choose Installation Guides - Application Server
Systems that navigates you to the SAP Help Portal.
5. In the dynamic table, choose your operating system.
6. You can download the corresponding installation guide as a PDF le or open it in an HTML format.
Related Information
Con guration of the Standalone Enqueue Server 2
Con guration of the Standalone Enqueue Server 2

In older releases, to use the Enqueue Server 2 you needed to switch from the old Enqueue Server to the new one after you have
installed the ABAP Central Service (ASCS) instance. As of now the Enqueue Server 2 is installed by default.
For more information about the con guration of the Enqueue Server 2, see Con guration of the Enqueue Server 2.
In high availability (HA) scenarios, you had to install the Enqueue Replication Server (ERS) instance and con gure Enqueue
Replicator 2 manually after you have switched to the Enqueue Server 2. Now the Enqueue Replicator 2 is installed automatically
with the Enqueue Server 2.
For more information about the con guration of the Enqueue Replicator 2, see Con guration of the Enqueue Replicator 2.
Con guration of the Enqueue Server 2

The con guration of the Enqueue Server 2 should look as follows:
Default Pro le
The following parameters should be set in the default pro le as they need to be identical on all instances:
enq/serverhost=<host of ASCS instance>
enq/serverinst=<number of ASCS instance>
ASCS Instance Pro le
UNIX Platforms
_ENQ = enq.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_ENQ)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_server$(FT_EXE) $(_ENQ)
Restart_Program_01 = local $(_ENQ) pf=$(_PF)
Windows
_ENQ = $(DIR_EXECUTABLE)/enq_server$(FT_EXE)
 Note
11/13/2020
The Execute_* and the Restart_Program_* parameters must have the number that is not yet used.

The con guration of the Enqueue Replicator 2 should look as follows:
Default Pro le
The following parameters should be set in the default pro le as they need to be identical on all instances:
enq/serverhost=<host of ASCS instance>
enq/serverinst=<number of ASCS instance>
enq/replicatorhost=<host of ERS instance>
enq/replicatorinst=<number of ERS instance>
 Tip
To ensure the synchronization between the lock table and the replication table, we recommend that you set the parameter
enq/client/max_async_requests = 0 in the client pro le.
ASCS Instance Pro le
UNIX Platforms
enq/server/replication/enable = TRUE
_ENQ = enq.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_ENQ)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_server$(FT_EXE) $(_ENQ)
Windows
enq/server/replication/enable = TRUE
_ENQ = $(DIR_EXECUTABLE)/enq_server$(FT_EXE)
 Note
The Execute_* and the Start_Program_* parameters must have the number that is not yet used.
ERS Instance Pro le
UNIX Platforms
_ENQR = enqr.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_ENQR)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_replicator$(FT_EXE) $(_ENQR)
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23146476&topics=902412f09e134f5bb875adb6db… 10/22
11/13/2020
Start_Program_01 = local $(_ENQR) pf=$(_PF)
Windows
_ENQR = $(DIR_EXECUTABLE)/enq_replicator$(FT_EXE)
Start_Program_01 = local $(_ENQR) pf=$(_PF)
 Note
The Execute_* and the Start_Program_* parameter must have the number that is not yet used.
Comparison of Old and New Pro le Parameters

This page compares the pro le parameters of the Standalone Enqueue Server 2 to the pro le parameters of the Standalone
Enqueue Server that was available in previous releases.
Use
If you have installed the old Standalone Enqueue Server and you want to switch to the Standalone Enqueue Server 2 now, there
are some new pro le parameters that you need to set instead of the old parameters. The table shows all pro le parameters that
have been changed for the Standalone Enqueue Server 2.
 Note
If a pro le parameter is not listed in the table, you need to remove it from the pro le because the parameter is not valid
anymore.
 Note
If the default value of a pro le parameter of the Standalone Enqueue Server 2 is sufficient, do not set the parameter in the
corresponding pro le.
Standalone Enqueue Server Standalone Enqueue Server 2
Parameter Parameter Subparameter Pro le Comments
enque/async_req_max enq/client/max_async_requests Default
enque/backup_file enq/server/backup_file ASCS
enque/delay_jitter enq/client/delay_jitter Default
enque/delay_log_level enq/client/delay_log_level Default
enque/delay_log_time enq/client/delay_log_count Default
enque/delay_max enq/client/delay_max Default
enque/delay_max_refine enq/client/delay_max_refine Default
enque/deque_wait_answer enq/client/max_async_requests Default If you have set enque/

enq/client/max_as
enque/encni/port enq/serverport Default
enque/log_file enq/server/request_file ASCS
11/13/2020
Standalone Enqueue Server Standalone Enqueue Server 2
Parameter Parameter Subparameter Pro le Comments
enque/server/acl_file enq/io/server_port_0 ACLFILE ASCS Set the example ACL
 Example
enq/io/server_p
PROT=ENQUEUE,PO
enque/server/max_clients enq/io/max_conn ASCS
enque/server/replication enq/server/replication/enable ASCS
enque/server/replication_dll enq/server/replication/library ASCS
enque/server/replication_local enq/server/replication/type ASCS If you have set enque/

enq/server/replic
enque/server/session_quota enq/server/schema_0 SESSION_QUOTA ASCS You can set the session
 Example
enq/server/sche
enque/server/threadcount enq/io/max_threads ASCS The new Standalone E

Server. Therefore, do n
enque/serverhost enq/serverhost Default
enque/serverinst enq/serverinst Default
enque/sync_dequeall enq/client/max_async_requests Default If you have set enque/

to 0.
enque/table_size enq/server/schema_0 MAX_LOCKS ASCS The old parameter enq

parameter MAX_LOCKS
in the lock table.
You can, however, use t
You can increase the m
 Example
enq/server/sche
To nd the list of pro le parameters of the Standalone Enqueue Server 2 and Enqueue Replicator 2, check out the Related Links
section below.
Related Information
Pro le Parameters of Standalone Enqueue Server 2
Pro le Parameters of Enqueue Replicator 2
Administration and Monitoring of Standalone Enqueue Server 2 and Enqueue

Replicator 2
You can administrate and monitor the new Standalone Enqueue Server 2 and the Enqueue Replicator 2 in transaction SMENQ.
11/13/2020
Transaction SMENQ
After executing the transaction SMENQ you can see the following views:
Standard: In the standard view, application developers and end users can search for their locks and remove locks.
Server Administration: Here you can administrate and monitor the Standalone Enqueue Server 2. This view is relevant for
system administrators and SAP Support.
Replicator Administration: This view is only visible if you con gured Enqueue Replicator 2 for the replication. Here you can
administrate and monitor the Enqueue Replicator 2. This view is relevant for system administrators and SAP Support.
SMENQ Functions:
Function Description of Functions
Overview For example, here you can see if the server is running. Other
information includes the kernel release, the instance on which the
server is running, the ll level of the lock table.
Lock Table You can search the lock table using different lter settings. In
addition, you can also delete lock table entries here.
Top Usage: Lock owners holding more than 20 locks at the same time are
displayed here.
Available only in the Server Administration view.
Statistics In the statistics you can nd details about system load in

Standalone Enqueue Server 2 and Enqueue Replicator 2.
Connections Here the current client connections are displayed.
Threads Here all the threads of the Standalone Enqueue Server 2 or Enqueue
Replicator 2 are listed with their current action.
Parameters Here you can see the pro le parameters of Standalone Enqueue
Server 2 or Enqueue Replicator 2, and change their values.
Pro le The pro le le that you downloaded is displayed here.
Access Points Here information required to open a connection to Standalone

Enqueue Server 2 or or Enqueue Replicator 2 is displayed.
Functional Tests Some tests are available to check Standalone Enqueue Server 2.
These are used for support purposes.
Over ows If the lock table over ows, more details are displayed here. The
information is required for support purposes.
System Trace Here you can check for diagnostic and analysis purposes how many
enqueue requests were sent in your system, when they were sent,
and from which client. In the trace table you can nd more details
about the individual system traces.
Developer Trace: The information is required for support purposes.
Request Trace The information is required for support purposes.
11/13/2020
Function Description of Functions
Orphaned locks The information is required for support purposes.
For more information about managing the lock table in SMENQ, see Managing Lock Entries using SMENQ.
SAP Management Console

If you use a Windows platform, you can also use the SAP Microsoft Management Console (SAP MMC) to monitor the
Standalone Enqueue Server 2 and Enqueue Replicator 2.
In SAP MMC the following information to the Standalone Enqueue Server 2 and Enqueue Replicator 2:
Functions Description of Functions
Process List The list contains the executable le of the Standalone Enqueue
Server 2 or Enqueue Replicator 2, as well as information such as
current parameter values and trace les.
Syslog This contains the system log messages of the Standalone Enqueue
Server 2 or Enqueue Replicator 2.
Access Points The function displays the list of combinations of address and port
on which the Standalone Enqueue Server 2 or the Enqueue
Replicator 2 is waiting for connections.
Enqueue Locks This function displays the content of the lock table that is managed
by the Standalone Enqueue Server 2 or Enqueue Replicator 2.
Enqueue Statistics This function shows statistics on the lock table and the request
processing for the Standalone Enqueue Server 2 or Enqueue
Replicator 2.
Related Information
Trace Files

To enable the lock function in an SAP system using the Standalone Enqueue Server 2, you need to set pro le parameters to
con gure it correctly.
For the pro le parameters of Enqueue Server 2, there is a difference between the general parameters that you have to set in the
default pro le and the remaining client and server parameters.
You always have to explicitly set the general parameters in the default pro le, plus parameter enq/serverport, which you only
have to set if you want to override the port of Standalone Enqueue Server 2.
With the client parameters you can con gure the request processing for Enqueue Server 2.
The server parameters are used for con guring Enqueue Server 2.
If you want to extend the lock table, change the parameters enq/server/schema accordingly. You do not have to change other
parameters.
11/13/2020
The following table contains the general parameters that you have to set in the default pro le because they must identical in all
instances of an SAP system:
General Parameters
Parameter Name Description
enq/serverhost Speci es the name of the host on which the Enqueue Server 2 is running.
enq/serverinst Speci es the instance number of the Enqueue Server 2.
enq/serverport Speci es the port of the Enqueue Server 2. Normally, you do not have to set the port because it is
derived from instance number (enq/serverinst).
The table below contains further client pro le parameters of Enqueue Server 2:
Enqueue Client Parameters
enq/client/max_async_requests Speci es the maximum number of asynchronous requests that can be set in succession. If this
value is exceeded, the enqueue client converts ensuing asynchronous request into a
synchronous request.
If the value of the pro le parameter is set to 0, the enqueue client converts all asynchronous into
synchronous requests.
enq/client/timeout Speci es the maximum time an enqueue client request is allowed to take.
Each work process is an enqueue client that opens a separate connection to Enqueue Server 2. If
the timeout is reached, an error message is sent to the application.
The table below contains all server pro le parameters of the Enqueue Enqueue Server 2:
Enqueue Server Parameters
enq/io/conn_close_timeout Speci es how long the Enqueue Server 2 waits before it closes a connection to the enqueue client
with a hard shutdown. It may take some time to close the connection if data is present that was
not sent to the client or server. This is particularly relevant for SSL connections because a
message about the closure was sent to the client or server before the connection was actually
closed.
 Example
If this parameter is set to 10000, the Enqueue Server 2 waits up to 10 seconds while the
connection is closed with a soft shutdown. After 10 seconds the Enqueue Server 2 closes the
connection with a hard shutdown.
enq/io/listen_queue_len Speci es the maximum number of connections kept in the queue while a connection is opened. If
the queue is full, the Enqueue Server 2 declines further connection requests.
enq/io/max_conn Speci es the maximum number of network connections of Enqueue Server 2 that can be open at
the same time.
To manage overload situations better, the maximum number of network connections is increased
by the maximum number of threads.
enq/io/max_threads Speci es the number of threads to use of the Enqueue Server 2. This number is therefore the
number of network connections than can be processed at the same time.
11/13/2020
enq/io/max_timeout_wp Speci es how long a thread waits for data from the network before the connection is passed to an
identi ed monitoring thread for monitoring.
enq/io/req_queue_len Speci es the maximum number of waiting requests that can be kept in the queue. You should set
the value to a size large enough so all the requests have space in the queue. A good indication
would be the total number of work processes in the system
enq/io/server_port Speci es which port of Standalone Enqueue Server 2 is used for enqueue clients to connect with
the server.
This is a vector parameter in the form <Parametername>_<Index>. Currently, only one port
(enq/io/server_port_0) is supported. You can enter the service name or the port number.
By default the port is set to sapdpXX (XX is the instance number of the enqueue server). If you
want to use a different port number, you have to enter the parameter enq/serverport in the
default pro le because it has to be identical in all instances of an SAP system.
You can still set the following options for the parameter:
ACLFILE: This option speci es the le that is used as the access control list, ACL). If the
pro le parameter is set, the le must exist and its syntax be correct.
MAX_RECEIVE_TIMEOUT: This option speci es the maximum time in seconds that is

allowed for the protocol handshake. The connection is closed if the time is exceeded.
enq/io/ssl_handshake_timeout Speci es how long the Enqueue Server 2 waits for a response with SSL handshake.
enq/io/stacksize_KB Speci es the size of the stack of a worker thread of Enqueue Server 2.
enq/server/backup_file Speci es the name of a backup le. You must enter the full path.
The backup is le is used to enter the locks, which are transferred to the update, in the lock table
again after Enqueue Server 2 is restarted.
enq/server/export_file Speci es the name of the export le. You must enter the full path.
In the export le at speci c times, for example during the rolling kernel switch, the whole lock
table is written.
enq/server/request_file Speci es the name of the request trace le. You must enter the complete path.
All requests that are sent to Enqueue Server 2 are recorded In the request trace le. By default,
the recording is not activated. It can be activated or deactivated in ABAP transaction SMENQ. For
performance reasons, the request trace should only be activated if problems with request
processing have to be analyzed. The request trace should be deactivated again afterwards.
11/13/2020
enq/server/schema With this parameter a schema is created in the lock table. This is a vector parameter in the form
<Parametername>_<Index>. Currently, only one schema (enq/server/schema_0) is
supported.
Information:
MAX_LOCKS: Speci es the maximum number of locks.
SESSION_QUOTA: Speci es the maximum number of locks for a single ABAP session.
The value is speci ed as a percentage of the total size of the lock table. A value of 100
percent removes the limit.
 Example
If you want to increase the table to 400000 lock entries, in the ASCS instance pro le you set
parameter enq/server/schema_0 =
NAME=$(SAPSYSTEMNAME),MAX_LOCKS=400000,SESSION_QUOTA=100
enq/server/trace/backups Speci es the number of saved developer trace les.
 Example
If the number is set to three, the trace contents are saved in the trace les ".old", ".old.1" and
".old.2".
The following table contains the pro le parameters, with which you con gure the Enqueue Replicator 2:
Enqueue Server Replication Parameters
enq/server/replication/enable You use this parameter to specify whether the replication mechanism activated and therefore the lock
table of the Enqueue Server 2 is to be replicated. To do this, you must set the parameter to TRUE .
If you do not want to activate the replication mechanism, set the parameter to FALSE.
 Caution
Note that the default value of this parameter is FALSE.
enq/server/replication/type With this parameter you decide, which replication type of Enqueue Server 2 you want to use.
If you set the parameter to the default value "replicator", Enqueue Replicator 2 is used for the
replication. Alternatively, you can set the value to “library”. Then replication is performed by an external
library.
This parameter is only relevant if the replication was activated with parameter
enq/server/replication/enable=TRUE.
enq/server/replication/library With this parameter you specify the path of the external library that is responsible for replicating the
lock table in the Standalone Enqueue Server 2.
This parameter is only relevant if the replication was activated with

enq/server/replication/enable=TRUE, and the replication type was selected with
enq/server/replication/type=library.
Related Information
11/13/2020
Con guration of the Enqueue Server 2

As part of a high availability solution for your SAP system, you need to have the new Enqueue Replicator 2. To con gure the
Enqueue Replicator 2, you have to set speci c pro le parameters.
For the pro le parameters of Enqueue Replicator 2, there is a difference between the general parameters that you have to set in
the default pro le and the remaining parameters of the Enqueue Replicator 2.
You always have to explicitly set the general parameters in the default pro le. You only set parameters enq/serverport and
enq/replicatorport if you want to override the default ports of Enqueue Server 2 and Enqueue Replicator 2.
The following table contains the general parameters that you have to set in the default pro le because they have to be identical in
all instances of an SAP system:
General Parameters
enq/serverhost Speci es the name of the host on which the Enqueue Server 2 is
running.
enq/serverinst Speci es the instance number of the Enqueue Server 2.
enq/serverport Speci es the port of the Enqueue Server 2. You do not have to set
the port because it is derived from instance number
(enq/serverinst).
enq/replicatorhost Speci es the name of the host on which the Enqueue Replicator 2 is
running.
enq/replicatorinst Speci es the instance number of the Enqueue Replicator 2.
enq/replicatorport Speci es the port of the Enqueue Replicator 2. You do not have to
set the port because it is derived from instance number
(enq/replicatorinst).
The table below contains all server pro le parameters of the Enqueue Replicator 2:
Enqueue Replicator 2 - Parameters
enq/io/conn_close_timeout Speci es how long Enqueue Replicator 2 waits before it closes a

connection to Enqueue Server 2 with a hard shutdown. It may take
some time to close the connection if data is present that was not
sent to the Server or Replicator. This is particularly relevant for SSL
connections because a message about the closure was sent to the
server or replicator before the connection was actually closed.
 Example
If this parameter is set to 10000, the Enqueue Replicator 2 waits
up to 10 seconds while the connection is closed with a soft
shutdown. After 10 seconds Enqueue Replicator 2 closes the
connection with a hard shutdown.
11/13/2020
enq/io/listen_queue_len Speci es the maximum number of connections kept in the queue

while a connection is opened. If the queue is full, the Enqueue
Replicator 2 declines further connection requests.
enq/io/max_conn Speci es the maximum number of network connections of

Enqueue Replicator 2 that can be open at the same time.
To manage overload situations better, the maximum number of

network connections is increased by the maximum number of
threads.
enq/io/replicator_port Speci es the port of Enqueue Replicator 2 through which Enqueue

Server 2 can connect.
This is a vector parameter in the form

<Parametername>_<Index>. Currently, only one port
(enq/io/replicator_port_0) is supported. You can enter the
service name or the port number.
By default the port is set to sapdpXX (XX is the instance number of

Enqueue Replicator 2). If you want to use a different port number,
you have to enter parameter enq/replicatorport in the default
pro le because it has to be identical in all instances of an SAP
system.
ACLFILE: This option speci es the le that is used as the

access control list, ACL). If the pro le parameter is set, the
le must exist and its syntax be correct.
MAX_RECEIVE_TIMEOUT: This option speci es the

maximum time in seconds that is allowed for the protocol
handshake. The connection is closed if the time is
exceeded.
enq/io/ssl_handshake_timeout Speci es how long the Enqueue Replicator 2 waits for a response
with SSL handshake.
enq/io/max_timeout_wp Speci es how long a thread waits for data from the network before
the connection is passed to an identi ed monitoring thread for
monitoring.
enq/io/req_queue_len Speci es the maximum number of waiting requests that can be

kept in the queue. You should set the value to a size large enough so
all the requests have space in the queue. A good indication would
be the total number of work processes in the system
enq/io/stacksize_KB Speci es the size of the stack of a worker thread of Enqueue

Replicator 2.
enq/replicator/request_file Speci es the name of the request trace le. You have to enter the
full path in this parameter.
All requests that are sent to Enqueue Replicator 2 are recorded In

the request trace le. By default, the recording is not activated. It
can be activated or deactivated in ABAP transaction SMENQ. For
performance reasons, the request trace should only be activated if
problems with request processing have to be analyzed. The request
trace should be deactivated again afterwards.
11/13/2020
enq/replicator/trace/backups Speci es the number of saved developer trace les.
 Example
If the number is set to three, the trace contents are saved in the
trace les ".old", ".old.1" and ".old.2".
Related Information
Checking the Status of the Replication

The SMENQ transaction allows you to check if the Enqueue Replicator 2 has been activated and is running correctly.
Prerequisites
You have started the ABAP Central Services (ASCS) instance in your SAP system.
You have started the Enqueue Replication Server (ERS) instance in your SAP system (if you are using the replication by the
Enqueue Replicator 2).
Context
You want to check the replication mechanism by using the SMENQ transaction.
Procedure
1. In your system, execute the SMENQ transaction.
2. On the screen, choose view Server Administration.
3. In the Overview section, check the status of the replication mechanism.
Results
In the table, the Replication status should be Active.
Possible values are:
Not Con gured
The replication mechanism is not con gured. For more information, see Con guration of the Enqueue Replicator 2.
Active
You have con gured the replication mechanism and the replication table is up-to-date.
Active (update pending)
You have con gured the replication mechanism, but due to errors (for example, network errors) the replication table is not
up-to-date. The Standalone Enqueue Server 2 tries to update the replication table in the background. The status is
automatically switched back to Active after the replication table has been successfully updated.
11/13/2020
 Tip
You can see the changes made to the Replication status in the system log.
Troubleshooting
If any errors occur in the Standalone Enqueue Server 2 or Enqueue Replicator 2, you can correct them, for example, by importing
patches.
Prerequisites
You have obtained package ENSA2_<X>.SAR from the SAP Support Portal Home (https://support.sap.com ) to operate the
Enqueue Server 2 and Enqueue Replicator 2.
Info:
To download the package, proceed as follows:
1. On the SAP Support Portal Home, choose Download Software.
2. In the search eld, enter the search term 'AS ABAP'.
3. In the SOFTWARE CATEGORIES view, choose an appropriate release for a maintenance product.
4. 4. In the Downloads view, choose the most recent SAP KERNEL release. A download table opens.
5. Choose lter option #DATABASE INDEPENDENT and your platform.
6. Download the package ENSA2_<X>.SAR. Choose the most recent patch level.
For UNIX platforms, the package contains the following les:
enq_admin(.exe)
enq_server(.exe)
enq_replicator(.exe)
For Windows, the package contains the following additional les:
enq_admin.pdb
enq_server.pdb
enq_replicator.pdb
 Note
You can nd out the package version by executing each program with option -v (for example, enq_server -v). Each
program outputs the entire information about the version and patch level.
Context
You want to x problems in the Standalone Enqueue Server 2 or Enqueue Replicator 2 by importing patches.
Procedure
11/13/2020
1. Copy the above package les and replace them in the executable directory. The old package les are then overwritten.
 Caution
Both les enq_server(.exe) and enq_replicator(.exe) should always belong to the same package version.
You are not allowed to have different versions.
2. Trigger a failover of the ABAP Central Services (ASCS) instance. The exact procedure depends on your cluster solution. In
case of emergency, you can also terminate the enq_server process at the operation system level.
The Enqueue Server 2 is then shut down and the new version is started on a new host. The Enqueue Server 2 retrieves the
replication table from the still running Enqueue Replicator 2 and uses it as the new lock table.
3. Trigger a failover of the Enqueue Replication Server (ERS) instance. The exact procedure depends on your cluster solution.
In case of emergency, you can also terminate the enq_replicator process at the operation system level.
The Enqueue Replicator 2 is then shut down and the new version is started on a new host. The Enqueue Server 2 connects
to the Enqueue Replicator 2 and updates the replication table by sending its own lock table.
Trace Files
Use
Trace les provide important information for error analysis.
Both the Standalone Enqueue Server 2 and the Enqueue Replikator 2 write trace les to the work directory. You can view these
les in transaction SMENQ, or using SAP Management Console (or SAP Microsoft Management Console MMC if you use Windows).
 Note
The Standalone Enqueue Server 2 works internally with multiple threads that write to a trace le.
Unlike Standalone Enqueue Server 2, the new Enqueue Server 2 writes to only one trace le:
dev_enq_server: Information about when Enqueue Server 2 was started and what problems occurred is written to this
le. Other threads also write to this le.
Enqueue Replicator 2
Enqueue Replicator 2 also writes to only one trace le:
dev_enq_replicator: Information about all the components of Enqueue Replicator 2 is written to this le.
 Tip
You can deliver these trace les to Support for analysis if you open a problem message.

Standalone Enqueue Server 2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Standalone Enqueue Server 2

Загружено:

Авторское право:

Доступные форматы

11/13/2020

Standalone Enqueue Server 2

Original content: https://help.sap.com/viewer/cﬀ8531bc1d9416d91bb6781e628d4e0/202009.000/en-US

For more information, please visit the https://help.sap.com/viewer/disclaimer.

Standalone Enqueue Server 2

Advanced administration and monitoring options using transaction SMENQ

Functions of Standalone Enqueue Server 2

Management of lock table

Execution of lock operations

Collision check for locks using the lock table

Name and elds (lock argument) of the locked table

The following lock modes exist:

A lock collision occurs in the following cases:

Processes of Standalone Enqueue Server 2

For more information, see:

Request Processing in Standalone Enqueue Server 2

The following les are stored on the server side:

Developer trace Trace entries of Standalone Enqueue Server 2.

High Availability with Standalone Enqueue Server 2

Replication with Enqueue Replicator 2

High Availability Enqueue Server

Alternative Replication Mechanism

Initial Con guration

Configuration of ASCS and ERS instances

Failover of the ASCS Instance

Failover of the ASCS Instance

Failover of the ERS Instance

Failover of the ERS Instance

Installation of the Standalone Enqueue Server 2

Installing ASCS and ERS Instances

The following procedure describes how to download the installation guide:

1. Go the SAP Support Portal Home (https://support.sap.com ).

2. In the navigation bar, choose Tools Overview Software Logistics Tools .

5. In the dynamic table, choose your operating system.

Con guration of the Standalone Enqueue Server 2

Con guration of the Enqueue Server 2

enq/serverhost=<host of ASCS instance>

enq/serverinst=<number of ASCS instance>

ASCS Instance Pro le

Execute_01 = local rm -f $(_ENQ)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_server$(FT_EXE) $(_ENQ)

Restart_Program_01 = local $(_ENQ) pf=$(_PF)

Restart_Program_01 = local $(_ENQ) pf=$(_PF)

Con guration of the Enqueue Replicator 2

enq/serverhost=<host of ASCS instance>

enq/serverinst=<number of ASCS instance>

enq/replicatorhost=<host of ERS instance>

enq/replicatorinst=<number of ERS instance>

ASCS Instance Pro le

Execute_01 = local rm -f $(_ENQ)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_server$(FT_EXE) $(_ENQ)

Restart_Program_01 = local $(_ENQ) pf=$(_PF)

Restart_Program_01 = local $(_ENQ) pf=$(_PF)

ERS Instance Pro le

Execute_01 = local rm -f $(_ENQR)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enq_replicator$(FT_EXE) $(_ENQR)

Start_Program_01 = local $(_ENQR) pf=$(_PF)

Comparison of Old and New Pro le Parameters

Standalone Enqueue Server Standalone Enqueue Server 2

Parameter Parameter Subparameter Pro le Comments

enque/async_req_max enq/client/max_async_requests Default

enque/backup_file enq/server/backup_file ASCS

enque/delay_jitter enq/client/delay_jitter Default

enque/delay_log_level enq/client/delay_log_level Default