bgRFC:
Configuration
To ensure optimum performance of bgRFC communication, various settings need to be made.
You can perform all the relevant steps in transaction SBGRFCCONF.

To perform bgRFC configuration tasks, you need authorizations from authorization object S_BGRFC.
You have the following configuration options:
Basic Settings
Create supervisor destination
bgRFC cannot function if a supervisor destination has not been defined.
Creating Inbound Destinations
By creating separate inbound destinations for each application, you can distribute the load.
Assigning Queue Prefixes to Inbound Destinations
You need to make these settings in order to assign existing queue prefixes for a “classic” qRFC to an inbound destination, therefore ensuring that bgRFC works without errors.
Maintain logon server groups
By assigning server groups to an inbound destination, you can distribute the load.
Scheduler Configuration
To optimize system performance when using bgRFC, you can make various settings for the bgRFC schedulers.

If you do not want to make any changes here, the system takes the default values.
You can find information about the authorizations required for bgRFC configuration under:
The settings described above are on the various tab pages in transaction SBGRFCCONF.
For more information about the configuration options, see:
● Creating a Supervisor Destination
● Maintaining Inbound Destinations
● Application Server-Specific Settings
● Destination-Specific Settings
You can find more information about setting up system resources (work processes) for bgRFC under:
●
Configuration of
System Resources for aRFC, tRFC, qRFC