Creating a Supervisor Destination 

Use

On the Maintain Supervisor Dest. tab in transaction SBGRFCCONF, you can define a supervisor destination for bgRFC processing. The supervisor destination gets the configuration settings for the bgRFC scheduler and starts or stops the schedulers as required on each application server.

The bgRFC can only function if a supervisor destination has been defined.

Prerequisites

You have used transaction SM59 to define the supervisor destination as an RFC destination. This destination must be defined as either an ABAP connection or a logical connection. The following prerequisites must be met.

ABAP Connection

No load balancing can be defined.

No system number can be entered.

No server can be entered.

Logical Connection

The only permissible entries as the reference for the logical connection are "NONE“ or initial (blank).

A user, password, and client must be entered for both connection types.

The user needs the authorizations in the SAP_BC_BGRFC_SUPERVISOR role.

Standard Settings

Enter the name of the RFC destination in the Destination Name field and choose Save.

This destination is then locked in transaction SM59, which means that it cannot be modified or deleted. If you want to change the destination, you must first create a new destination in transaction SM59 and then enter the required name as a supervisor destination. The previous destination is then unlocked in transaction SM59.

 Example

You have changed the setting for the maximum number of schedulers (see subsequent steps under “Configure Schedulers”). The supervisor destination now has the task of implementing these settings on all application servers.