TRFC calls Test

Transactional RFC (tRFC) and qRFC are variants of the Remote Function Call that make the data transfer between different systems more reliable and more secure. For each type of tRFC call, this test reports the number of calls that were recorded, the number of calls that were executed. Using this test, administrators may figure out how many calls were in states such as CPICERR, SYSFAIL, other states etc.

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

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.

LongWaitingCutoff

Specify the time duration in hours beyond which the tRFC calls are classified as stuck in the LongWaitingCutoff text box.

StuckStates

By default, tRFC calls are prone to get stuck when in MAILED or RECORDED states. In order to monitor those tRFC call that are stuck in these states, specify these states as a comma-separated list in the StuckStates text box. The default is MAILED,RECORDED. If you wish to monitor the tRFC calls that are stuck in HOLD state, then you can specify MAILED,RECORDED,HOLD in this text box.

Need DD For Other States

If you wish to disable the detailed diagnosis capability for the Calls in other states measure of this test, then set the Need DD For Other States parameter to No. By default, this is set 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 suite 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:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Calls recorded

Indicates the number of tRFC calls of this type that were recorded during the last measurement period.

Number

A sudden/gradual increase in the value of this measure could indicate issues such as insufficient configuration of connection resources for transactions.

Calls executed

Indicates the number of tRFC calls of this type that were executed during the last measurement period.

Number

 

CPICERR calls

Indicates the number of tRFC calls of this type with communication errors i.e., the number of tRFC calls in CPICERR state during the last measurement period.

Number

CPICERR error arises due to connection of communication issues with the target system or external component. CPICERR calls may be retried.

The detailed diagnosis of this measure if enabled, lists the details about these calls such as the host, process ID, timestamp, destination, function, user, retries, Tcode and error message.

SYSFAIL calls

Indicates the number of tRFC calls of this type that were in SYSFAIL state during the last measurement period.

Number

SYSFAIL error arises due to error in execution of tRFC call in target system or external component.

The detailed diagnosis of this measure if enabled lists the details about these calls such as the host, process ID, timestamp, destination, function, user, retries, Tcode and error message.

Number of calls mailed

Indicates the number of tRFC calls of this type for which CMC (protocol X400) connection was initiated during the last measurement period.

Number

 

Calls executed in target

Indicates the total number of tRFC calls of this type that were executed in the target SAP system during the last measurement period.

Number

 

Calls in other states

Indicates the number of tRFC calls of this type that were in intermediary states such as HOLD, WCONFIRM, SYSLOAD etc during the last measurement period.

Number

Tracking these calls become important when typical tRFC issues are encountered.

The detailed diagnosis of this emasure if enabled lists the details for these calls using which you can figure out any abnormal/error states.

Long waiting calls

Indicates the number of tRFC calls of this type that were stuck in any state beyond the time specified against the longwaitingCutOff parameter while configuring this test.

Number

tRFC calls can get stuck in certain states due to various reasons such as insufficient errors or intermediate errors, communication issues etc. Such calls need to be either manually processed or an appropriate report can be configured to process any known issues.

Use the detailed diagnosis of this measure for further analysis of such calls.