User Session Memory Test
This test auto-discovers the users accessing the SAP ABAP instance server and for each user reports the count of sessions initiated and the memory related statistics. Using this test, administrators may be able to clearly identify the user who is utilizing the maximum amount of memory per session.
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 user who is currently logged into the SAP ABAP system.
| 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. |
|
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. |
|
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 the following authorization objects: S_RFC, S_RFC_ADM, S_TABU_DIS, S_XMI_PROD, S_TOOLS_EX, S_RZL_ADM. 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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
Include Users |
Specify a comma-separated list of users to be included for monitoring, by default, in this text box. By default, this is set to none. |
|
Exclude Users |
Specify a comma-separated list of users to be excluded from the scope of monitoring, in this text box.By default, this is set to none. |
|
Include eG SAP User |
By default, this flag is set to No. This means that the measures reported by this test will not, by default, consider the sessions launched by the eG agent on the SAP ABAP instance, as the configured SAP User. If you want the test to consider these sessions too when reporting metrics, set this flag to Yes. |
|
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:
|
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Current sessions |
Indicates the number of sessions initiated by this user. |
Number |
This measure is a good indicator of the load on the SAP ABAP instance server. |
|
Total memory |
Indicates the total memory utilized by this user. |
MB |
Compare the value of this measure across users to figure out the user who is utilizing the maximum/least amount of memory. |
|
Roll memory |
Indicates the amount of memory utilized by this user in the roll area. |
MB |
Roll memory is characterized by sequential memory allocation to several work processes and employs a relatively slow copying process. User context is first copied to part of roll memory. |
|
Page memory |
Indicates the amount of page memory utilized by this user. |
MB |
Page memory is used to extend the roll memory in runtime when large datasets or internal tables need to be handled. |
|
Extended memory |
Indicates the amount of extended memory utilized by this user. |
MB |
Extended memory is a shared memory which is one of the most important and used memory areas of SAP. Extended memory is characterized by sequential memory allocation to several work processes and employs a relatively fast copying process and uses swap space. |
|
Priv memory |
Indicates the amount of private memory utilized by this user. |
|
PRIV memory is the heap memory assigned solely to a work process to be held until the end of the user’s request. Work processes that have accumulated a lot of PRIV memory have to be restarted in order to free up and release the PRIV memory back to the Operating System. Load created by users consistently occupying a lot of PRIV memory need to be monitored closely. |
|
Maximum memory per session |
Indicates the maximum amount of memory utilized by this user per session. |
MB |
The detailed diagnosis of this measure lists the session handle, IP, Terminal, Tcode, Overall memory, total memory, roll memory, page memory, PRIV memory of the session and also indicates whether the session is still attached to the user. |
|
Maximum roll memory per session |
Indicates the maximum amount of memory utilized in the roll area by this user per session. |
MB |
The detailed diagnosis of this measure lists the session handle, IP, Terminal, Tcode, Overall memory, total memory, roll memory, page memory, PRIV memory of the session and also indicates whether the session is still attached to the user. |
|
Maximum page memory per session |
Indicates the maximum amount of page memory utilized by this user per session. |
MB |
The detailed diagnosis of this measure lists the session handle, IP, Terminal, Tcode, Overall memory, total memory, roll memory, page memory, PRIV memory of the session and also indicates whether the session is still attached to the user. |
|
Maximum extended memory per session |
Indicates the maximum amount of extended memory utilized by this user per session. |
MB |
The detailed diagnosis of this measure lists the session handle, IP, Terminal, Tcode, Overall memory, total memory, roll memory, page memory, PRIV memory of the session and also indicates whether the session is still attached to the user. |
|
Maximum priv memory per session |
Indicates the maximum amount of PRIV memory utilized by this user per session. |
MB |
|
|
Total memory per session |
Indicates the average memory utilized in a session by this user. |
MB |
|
|
Roll memory per session |
Indicates the average amount of memory utilized in the roll area by this user in a session. |
MB |
|
|
Page memory per session |
Indicates the average amount of page memory utilized by this user in a session. |
MB |
|
|
Extended memory per session |
Indicates the average amount of extended memory utilized by this user in a session. |
MB |
|
|
Priv memory per session |
Indicates the average amount of PRIV memory utilized by this user in a session. |
MB |
|
