Memory Management Test
This test monitors the basic functions of the SAP Memory Management System and advises on how best to configure the system depending upon the platform used, the available resources, etc. It also sheds light on the hardware and operating system usage.
This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick SAP ABAP as the desired Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.
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.
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 |
Password |
The password of the specified SAPUser. |
Confirm Password |
Confirm the password by retyping it here. |
SysNo |
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. |
IsPassive |
If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP INSTANCE 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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Heap memory total allocation |
The total size of heap memory (private memory). |
MB |
|
Heap memory peak use |
A high watermark of heap memory usage. |
Percent |
|
Heap memory recent peak use |
The peak usage of heap memory in recent times. |
Percent |
|
Heap memory actual usage |
The percentage of heap memory actually used. |
Percent |
|
Extended memory allocated |
Indicates the total size of the extended memory. |
MB |
|
Extended memory peak use |
The high watermark of the stack memory usage since startup. |
Percent |
|
Extended memory rec peak use |
Indicates the peak usage achieved in the recent period for extended memory. |
Percent |
|
High extended memory usage |
The actual usage of extended memory. |
Percent |
|
High extended memory attached |
The percentage of extended memory in user contexts that is active in WPs now. |
Percent |
|
Number of extended memory slots |
The number of extended memory slots. |
Number |
|
Extended memory slot peak use |
Indicates the peak usage of the extended memory slots. |
Percent |
|
Extended memory slot rec peak use |
The peak usage of the extended memory slots in recent times. |
Percent |
|
Usage of extended memory slots |
The percentage of extended memory slots actually used. |
Percent |
|
Private work processes |
The number of restarted private work processes. |
Number |
|
Dialog work processes restarted |
The number of restarted dialog processes. |
Number |
|
Non-dialog work process restarts |
The number of non-dialog processes restarted. |
Number |
|