ABAP Instance Processes Test

In SAP environments, during peak business operations such as month-end financial closing, a large number of users execute intensive reports, batch jobs, and transactional postings simultaneously. In the process, dialog or background work processes may be fully occupied or stuck in a long-running state delaying critical postings. Similarly, inefficient custom ABAP programs or high data volume processing may consume excessive memory utilization. Administrators are therefore required to keep track on the processes accessed as well as the memory consumed by the processes. The ABAP Instance Processes test helps administrators in this regard.

For each process running on the target SAP ABAP Instance, this test reports the number of instances of the process that are currently running and the memory utilized. Using this test, administrators can figure out the process that is busy as well as consuming excessive memory resources.

Target of the test : A SAP ABAP instance

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every port on the target SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	Host name of the server for which the test is to be configured.
Port	Enter the port to which the specified host listens.
SAP ABAP Process
ClientName	Specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.
SAPUser	Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.
Password	The password of the specified SAPUser.
Confirm Password	Confirm the password by retyping it here.
SysNo	SysNo 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 SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SysNo will have to be specified as ‘01’. Therefore, in the SysNo text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
Router	If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the Router text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
InstanceName	This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time.
Timeout	Indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.
JCO Version	The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO Version – in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x.
Run Agent Based	In modern SAP environments, SAP ABAP Instances are typically hosted on SAP S/4 HANA Cloud, Private Edition (SAP PCE). To ensure that Operating System-level metrics are collected from these SAP ABAP Instances and reported seamlessly, the default configuration for this flag is set to No. This ensures that the eG remote agent collects the metrics upon execution of this test. However, if you prefer to monitor the target SAP ABAP Instance using an agent-based approach - which is the recommended approach, then, set this flag to Yes.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Processes running	Indicates the number of instances of this process currently executing on the target SAP ABAP Instance.	Number	This value indicates if too many or too few processes corresponding to an application are executing on the host. Compare the value of this measure across processes to figure out the process that is most used.
Memory utilization	Indicates the ratio of the resident set size of this process to the physical memory of the target host system, expressed as a percentage.	Percentage	A sudden increase in memory utilization for one/more process(es) may be indicative of memory leaks in the application. Compare the value of this measure across processes to identify the process that is consuming excessive memory resources consistently.