BGRFC Destination Workload Test
For each destination created on the target SAP ABAP System, this test reports the total processible units and executable units running. This test also provides in-depth analysis of the tRFC and qRFC units. Using this test, administrators can figure out SYSFAIL error-prone tRFC and qRFC units. The tRFC and qRFC units that were waiting in the queue of each destination can be identified and thus the workload on each destination can be determined.
Target of the test : A SAP ABAP System
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each Destination Type: Destination created on the target SAP ABAP System 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. |
Application Server |
For the eG agent to connect to the target SAP ABAP System and collect metrics, this test should be configured with the IP address of any of the SAP ABAP Instances associated with the target SAP ABAP System. Specify such IP address in this text box. |
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. |
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 |
---|---|---|---|
Processible units |
Indicates the total number of processible units that were running for this destination during the last measurement period. |
Number |
|
Executable units |
Indicates the number of executable units that were running for this destination during the last measurement period. |
Number |
|
tRFC Processible units |
Indicates the number of tRFC processible units that were running for this destination during the last measurement period. |
Number |
|
qRFC Processible units |
Indicates the number of qRFC processible units that were running for this destination during the last measurement period. |
Number |
|
tRFC unit executions |
Indicates the number of tRFC units that were executed for this destination during the last measurement period. |
Number |
|
qRFC unit executions |
Indicates the number of qRFC units that were executed for this destination during the last measurement period. |
Number |
|
tRFC executable units |
Indicates the number of tRFC executable units available for this destination during the last measurement period. |
Number |
|
tRFC units with SYSFAIL error |
Indicates the number of tRFC units detected with SYSFAIL error for this destination during the last measurement period. |
Number |
|
Remaining tRFC units |
Indicates the number of tRFC units that were available for use for this destination during the last measurement period. |
Number |
|
tRFC units deleted after execution |
Indicates the number of tRFC units that were deleted after execution on this destination during the last measurement period. |
Number |
|
qRFC executable units |
Indicates the number of qRFC executable units for this destination during the last measurement period. |
Number |
|
qRFC units with SYSFAIL error |
Indicates the number of qRFC units detected with SYSFAIL error for this destination during the last measurement period. |
Number |
|
Remaining qRFC units |
Indicates the number of qRFC units that were available for use for this destination during the last measurement period. |
Number |
|
qRFC units deleted after execution |
Indicates the number of qRFC units that were deleted after execution on this destination during the last measurement period. |
Number |
|
qRFC units in Queues |
Indicates the total number of qRFC units available in the queues for this destination during the last measurement period. |
Number |
This measure is a good indicator of workload on the destinations. |
Total queues |
Indicates the total number of queues available for this destination. |
Number |
|
qRFC units per queue |
Indicates the average number of qRFC units available per queue for this destination during the last measurement period. |
Number |
This measure is a good indicator of workload on the destinations. |
qRFC units in longest queue |
Indicates the number of qRFC units available in the longest queue for this destination during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the tRFC oldest timestamp, qRFC oldest timestamp and the queue name for each qRFC unit. |
qRFC queues per unit |
Indicates the number of qRFC queues available per qRFC unit for this destination during the last measurement period. |
Number |
|