Show TOC

bgRFC Scheduler: Application Server-Specific SettingsLocate this document in the navigation structure


On the Scheduler: App.-Server tab page in the transaction SBGRFCCONF, you can configure the bgRFC scheduler for outbound and inbound processing at application server level.


The settings you make here do not become active immediately; instead they only become active when AUTOABAP next runs.


Use this transaction only if you do not want to use the default settings.

Standard Settings

Define the following fields as required for each entered server:


If you want to define your own defaults for your application servers, you can create a server entry with the name BGRFC_INSTANCE_DEFAULTS and enter the required values for this entry. These settings then apply to all application servers that do not have different values entered.

Number of Schedulers

(Number of outbound or inbound schedulers per application server)

Number of inbound schedulers (per application server). 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.


At least three dialog work processes must be available on each application server where a scheduler is to be started. Another dialog work process must be made available for each further scheduler. No scheduler can be started on application servers with fewer than three dialog work processes. Make sure that both inbound and outbound schedulers have enough dialog work processes.

The values have the following meanings:

o -1: The number of schedulers is determined by the load (default).

o 0: Application server/destination is locked for bgRFC.


o > 0: Maximum number of running schedulers for application server/destination.

Application server/destination

  • Default value: -1

  • Value range: >= -1, 0 = locked

Number of Connections per Server

(Maximum number of open connections (tasks) per application server)

This parameter defines how many open connections (tasks) can be held by a server. All non-processed bgRFC calls for this destination are counted. Using these

parameters you can prevent destinations from being overloaded by bgRFC calls.

For TCP/IP connections (external server programs), generally only one connection should be permitted.

You can also specify the number of permitted open connections at the scheduler level. If the number of possible connections for each scheduler is less than the number at destination level, or if this has to be distributed across multiple destinations, the maximum

number of open connections per destination is not always reached.

The maximum number of open connections that can be held by the Task Handler is a further restriction.

o 0: Destination is locked against bgRFC calls.


Default value: 500

Value range: >= 0

Percentage of Gateway Resources

(Percentage of available gateway resources)

Specifies the percentage of currently available (free) gateway resources that can be used by a scheduler.

You can use this parameter setting to avoid gateway overloads.

  • Choose a percentage between 1% and 100%.

  • If you choose a percentage that is too large, you may overload the gateway. If you choose a percentage that is too small, the throughput may be restricted.

    • Default value: 50

    • Value range: 1 < x < 100

Scheduler Idle Time

(Idle time of a scheduler in seconds)

The idle time determines how long the scheduler waits if no queries are currently waiting to be processed. If there are no queries after this time, the scheduler terminates.

  • Default value: 300

  • Value range: >= 60

    Destinations per Server

    (Maximum number of destinations processed by a scheduler)

  • Default value: 10

  • Value range: Value range: >=1and <= < Maximum number of open connections per server> (see Number of Connections per Server).

    Lifetime of Entries

    (Maximum lifetime of load balancing entries in seconds)

    Automatic load balancing data is collected created for systems that receive tRFC or qRFC calls. Under normal circumstances, these entries are refreshed by returning calls.

    The system actively requests information only if an entry is older than the setting in this parameter.

  • Default value: 10

  • Value range: >= 1