SAP Locks Test

In SAP NetWeaver Application Server, locks serve a fundamental role in managing concurrency and ensuring data consistency within the SAP system. The locks are essential for preventing conflicts in SAP NetWeaver Application Server environments with multiple concurrent users. By managing locks effectively, SAP ensures the reliability and integrity of business processes running on the SAP platform. The SAP Locks test reveals the count of the different types of locks and how well the connections are used on the target server. In the process, this test also reports the count and percentage of threads and query entries used on the target server.

Target of the test : A SAP NetWeaver Application Server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the target SAP Web Application server being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	Specify the server for which the test is to be configured.
Port	The port number at which the specified server listens.
WSDL Port	This test uses the SAPControl web service to pull metrics on application and service status. To enable the test to communicate with the web service, you need to configure the test with the port number of the web service. Therefore, specify the port number of the SAPControl web service against WSDL Port. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP WAS being monitored. If the port number is not declared in the etc/services file, you can specify the default port number of the web service against WSDL Port. If the web service is not SSL-enabled, then the default port number of the web service will be: 5<NR>13. Similarly, if the web service is SSL-enabled, then the default port number of the web service will be: 5<NR>14. <NR> in the port number refers to the system number of the SAP server being monitored. The system number is an indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the system number will be ‘00’. Similarly, if the SAP server port is 3201, the system number will have to be specified as ‘01’. Accordingly, the default port number of an SSL-enabled SAPControl web service will be 50014 , if the system number is 00, or 50114, if the system number is 01.
OS Username and OS Password	To enable the test to access the SAPControl web service and determine component state, you need to configure the OS Username and OS Password parameters of the test with the credentials (i.e., name and password) of an OS user, who fulfills one of the following conditions: The name of the OS user should be declared using the service\admin_users profile parameter; (OR) The name of the user group to which the OS user belongs should be declared using the service\admin_groups profile parameter; (OR) The OS user should have the permission to execute the sapstartsrv executable
Confirm Password	Confirm the OS Password by retyping it here.
SSL	Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Exclusive locks	Indicates the number of exclusive SAP locks in the Enqueuer server.	Number	An exclusive lock protects the locked object against all types of locks from other transactions. Only the same lock owner can reset the lock (accumulate). A steady increase in this measure could mean a program error locking up system resources and not freeing them up.
Exclusive non-cumulative locks	Indicates the number of exclusive noncumulative SAP locks in the Enqueue server.	Number	Exclusive but non-cumulative locks can be called only once from the same transaction. Each further lock request will be rejected. A steady increase in this measure could mean a program error locking up system resources and not freeing them up.
Other locks	Indicates the number of non-exclusive SAP locks in the Enqueuer server.	Number	Other lock types include shared locks and optimistic locks. In case of shared locks, several users (transactions) can access locked data at the same time in display mode. A request for another shared lock is accepted, even if it comes from another user. An exclusive lock set on an object that already has a shared lock will be rejected. Optimistic locks initially behave like shared locks and can be converted into exclusive locks. For instance, these locks are used when the user displays data in change-mode. If the user wants to save the data, these locks have to be converted to exclusive locks.
All locks	Indicates the total number of SAP locks in the Enqueuer server.	Number	If this value approaches the configured maximum number of locks, lock table overflow error occurs. Either the lock table size is set too low or there is an errant program that is cumulatively consuming and not releasing its locks.
Percentage threads created	Indicates the percentage of instantiated worker threads that are currently processing requests.	Percentage
Percentage created threads running	Indicates the percentage of instantiated worker threads that are currently running.	Percentage
Maximum threads	Indicates the maximum number of threads that are allocated to the server.	Number
Maximum connections	Indicates the maximum number of connections that can be handled by the server.	Number
Maximum queue threads	Indicates the maximum number of threads that are currently in queue.	Number
Used connections	Indicates the number of connections that are opened by the worker threads.	Number	If the value of these measures are consistently high, then, try increasing the size of the worker connections.
Percentage connections used	Indicates the percentage of connection that are opened by the worker threads.	Percentage
Used queue entries	Indicates the number of queue entries occupied with incoming requests.	Number	If the value of these measures are consistently high, then, try increasing the maximum number of queue entries.
Percentage queue entries used	Indicates the percentage of queue entries occupied with incoming requests.	Percentage