qRFC

Using a qRFC, data can be exchanged between two application components in multiple queues on a first-in-first-out basis (FIFO) for the function modules.

The actual sending process is still executed by the tRFC (transactional Remote Function Call). Inbound and outbound queues are added to the tRFC, leaving us with a qRFC (queued Remote Function Call).

Although qRFCs are serialized tRFC LUWs, you cannot maintain or display these LUWs using the tRFC administration transaction SM58. You have to use the qRFC queue administration transaction SMQ1 for outbound queues and SMQ2 for inbound queues.

 

Technical Prerequisites

The following technical prerequisites have to be met in order to use the qRFC Monitoring:

  • The managed system is ABAP-based SAP system of Basis release ≥ 7.00

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

The available monitoring categories are:

  • qRFC: qRFC queues from and to the ABAP system (Monitoring transaction SMQ1 for outbound queues and SMQ2 for inbound queues).

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options

qRFC 

For qRFC Monitoring, you can collect all qRFC entries in the managed system. You can also use the following filter parameters, to restrict the data collection:

  • Direction: restricts the selection on either an inbound (I) or outbound (O) qRFC
  • Queue Name: the same or the queue group of the qRFC queue. The queue group defines a prefix to combine all single queues with the same prefix into a queue group.
  • RFC Destination: The name of the RFC as in SM59. The parameter "RFC Destination" is only relevant for outbound qRFCs.
 

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For interfaces of type qRFC the following metrics are collected:

qRFC 

  • Number of qRFC entries per queue group: Number of entries in the queue group(s) that fall in the selected status group
    Metric parameters:
    • STATE_GROUP = CRITICAL, INTERIM
    • OLDER_THAN_MINUTES = Only consider queues with entries older than X minutes 
  • Age of oldest qRFC entry per queue group: Age of the oldest entry in the queue group(s) that falls in the selected status group
    Metric parameters:
    • STATE_GROUP = CRITICAL, INTERIM
    • OLDER_THAN_MINUTES = Only consider queues with entries older than X minutes 
 

Further Information

The following status codes are taken into account for error and interim statuses:

Direction Severity qRFC Status Code
Outbound Critical ANORETRY, SYSFAIL, VBERROR
  Interim ARTRY, CPICERR, EXECUTED, MODIFY, NOSENDS, RETRY, RUNNING, STOP, SYSLOAD, WAITING, WAITSTOP, WAITUPDA
Inbound Critical ANORETRY, SYSFAIL
  Interim

ARETRY, CPICERR, MODIFY, NOEXEC, RETRY, RUNNING, STOP, WAITING, WAITSTOP