eG Help

Background communication is a term used to describe various asynchronous communication methods. With all the methods, the data that is exchanged between calling and called applications is recorded in the database. The database can be used both by the caller and the called application.

From the database, the data is transferred according to either the push principle or the pull principle. With the push principle, the transfer from the database is triggered by one or more schedulers. With the pull principle, the receiver (the called application) collects the data from the database on its own. This procedure is also known as a no-send scenario in SAP terminology. In all cases, the system ensures the data is transferred once only with all the procedures. The caller can also determine precise adherence to the call order when the data is transferred to the called application.

The bgRFC (Background Remote Function Call) offers the developers an API that allows applications to transfer and record the data. The bgRFC organizes different calls using queues. A Background Remote Function Call (bgRFC) destination should be created for communication in an outbound queue or an inbound queue respectively. The most important tool in terms of bgRFC administration is the bgRFC monitor. This monitor allows you to display and edit the individual queues and units.

If a bgRFC destination is locked or does not have sufficient resources, then the information of the bgRFC call stored in the bgRFC destination cannot be accessed. Likewise, the count of the inbound schedulers and outbound schedulers that are running should also be monitored periodically to figure out if the load on the SAP ABAP System is constant throughout. For this purpose, it is required to monitor the health of the bgRFC destinations. The BgrfcHlthChkTest test helps administrators in this regard!

This test reports the count of inbound and outbound schedulers that were running on the target SAP ABAP System. Using this test, administrators can figure out the unreachable and locked bgRFC destinations and also the destinations that do not have sufficient resources. Additionally, administrators are also pointed to protocol conversion errors periodically so that remedial measures to curb such errors can be taken at the earliest. By periodically monitoring the metrics reported by this test, administrators can figure out the load on the target SAP ABAP System.

Outputs of the test : One set of results for the target SAP ABAP System being monitored.

Measurement	Description	Measurement Unit	Interpretation
InboundNoOfScheduler	Indicates the number of inbound schedulers that were running during the last measurement period.	Number	A large number of schedulers can help a system to process more queries in parallel if the system load is heavy. However, if the system load is light, too many schedulers will block each other and reduce throughput.
OutboundNoOfScheduler	Indicates the number of outbound schedulers that were running during the last measurement period.	Number
OtherNoOfResources	Indicates the number of bgRFC destinations that had insufficient resources during the last measurement period.	Number
OtherNoOfPerformDest	Indicates the number of bgRFC destinations that were unreachable during the last measurement period.	Number	The detailed diagnosis of this measure lists the destinations that were unreachable and the reason for why the destinations were unreachable.
OtherNoOfPingDest	Indicates the number of bgRFC destinations that were locked during the last measurement period.	Number	The detailed diagnosis of this measure lists the destinations that were locked and the reason for why the destinations were locked.
OtherNoOfErrConversion	Indicates the number of protocol conversion errors detected during the last measurement period.	Number
OtherNoOfError	Indicates the number of errors of Other category detected during the last measurement period.	Number