Dialog Activity Test
The Dialog service is the one which responds to the user requests to an SAP ABAP server. This test reports performance statistics pertaining to the Dialog service of the SAP ABAP server.
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 the 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 |
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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Utilization of the dialog processes |
The percentage utilization of the dialog work processes of an application server. |
Percent |
|
Dialog work processes |
The number of dialog work processes. |
Number |
|
Dispatcher wait queue length |
The percentage utilization of the dispatcher wait queue. |
Percent |
With normal workload, this value is around 0%. A long wait queue is a sign that the application server has too few work processes or too high a CPU workload. |
Long runners |
Indicates how long the long-running dialog processes have been running. |
Secs |
Long-running tasks can block other users’ dialog steps and can produce a general degradation of dialog response time for interactive users. Resolving this problem requires analysis of long-running dialog steps. Corrective measures include moving users to another application server, asking users to schedule long-running reports or other actions as background jobs in off-peak time periods, etc. |
Dialog steps |
The number of dialog steps per minute. |
Steps/min |
A high value combined with a high Dialog process time points to a general overload; a very low value, indicates an error. |
Users logged in |
The number of users logged in. |
Number |
|