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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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 |