ABAP Host Memory Usage Test

The utilization of memory on a SAP ABAP instance involves comprehending how the memory is allocated, utilized, and managed across different components and processes in SAP ABAP System. This test monitors every memory type on the SAP ABAP instance and reports how efficiently the instance utilizes the memory resources of each type.

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 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.
PortNo	Enter the port to which the specified host listens.
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	This parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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	This parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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 parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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.
IsPassive	If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total memory	Indicates the total memory allocated to this instance.	GB
Free memory	Indicates the amount of memory available for use in this instance.	GB	A sudden decrease in this value could indicate an unexpected/sporadic spike in the memory utilization of the instance. A consistent decrease however could indicate a gradual, yet steady erosion of memory resources, and is hence a cause for concern.
Used memory	Indicates the amount of memory that is already utilized by this instance.	GB	A value close to the Total memory indicates that the instance is running out of memory resources. Administrators need to add additional memory resources.
Memory utilized	Indicates the percentage of memory utilized by this instance.	Percent	A value close to 100 indicates that the instance is facing severe memory contention. Administrators need to analyze such memory contentions and add additional memory resources as and when required.
Total swap space	Indicates the total swap space that is either allocated or reserved to this instance.	GB
Free swap space	Indicates the free swap space that is currently available for future reservation and allocation to this instance.	GB
Used swap space percentage	Indicates the percentage of swap space that is allocated or reserved.	Percent	A value close to 100% indicates that the swap space configured may not be sufficient.
Memory page ins	Indicates the rate at which memory pages are loaded from disk storage into the main memory (RAM).	Pages/sec	Memory page ins represent the operation of transferring memory pages from secondary storage (such as disk or swap space) into physical RAM. This usually happens when the system needs to access data that is not currently in RAM but is stored on disk due to memory constraints.
Memory page outs	Indicates the rate at which memory pages are moved from physical RAM to secondary storage.	Pages/sec	Memory page outs represent the operation of transferring memory pages from the RAM to disk-based virtual memory (such as swap space or paging file) when the system needs to free up physical memory for other processes or data. This value is a critical measure of the memory utilization on an instance. If this value never increases, then there is sufficient memory in the system. Instantaneous spikes of this value are acceptable, but if the value itself starts to rise over time or with load, it implies that there is a memory shortage on the instance.