Show TOC

Function documentationbgRFC Scheduler: Destination-Specific Settings Locate this document in the navigation structure

 

On the Scheduler: Destination tab page in the transaction SBGRFCCONF, you can configure the bgRFC scheduler for outbound and inbound processing at destination level.

Note Note

The settings you make here might not be activated immediately; instead they might only become active when a scheduler starts to process calls for this destination.

End of the note.

Prerequisites

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

Standard Settings

Define the following fields as required:

Number of Schedulers

(Number of schedulers for this destination)

  • Default value: -1 (means unending)

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

Maximum Number of Automatic Retries

(Maximum number of automatic retries per unit in the event of communication errors)

If a communication error occurs when a unit is sent to a destination, the unit is executed again after a specified period of time. This parameter determines how often the unit is retried before it is flagged as an error and locked.

You can make further automatic settings for the wait time between two retries.

  • Default value: 30

  • Value range: >= 0

Wait Time per Unit

(Wait time between two communication attempts in seconds (in the event of communication errors))

The wait time must be at least 60 seconds. If a communication error occurs when a unit is sent to a destination, the scheduler can retry the unit. This parameter defines the wait time between two retries.

You can use a further parameter to define the number of automatic restarts.

o Default value: 900

o Value range: >= 60

Wait Time per Destination

(Wait time (in seconds) between two automatic communication attempts to a destination in the event of a communication error)

The wait time must be at least 60 seconds. If there are frequent communication errors when sending units to a destination, the scheduler can lock this destination for a specified time. This parameter controls how long the lock on a destination is retained.

You can make further retry settings in the event of communication errors at the unit level.

  • Default value: 900

  • Value range: >= 60

Processing Time for Destination

(Maximum processing time for a destination in seconds)

This parameter defines how long a scheduler can process a destination before releasing it to be processed by other schedulers.

  • Default value: 0 (= infinite)

  • Value range: >= 300

Number of Connections per Destination

(Number of open connections (tasks) per destination)

  • Default value: 10

  • Value range: >= 0

Number of Automatic Checks

(Maximum number of automatic checks to see whether a unit is still being processed)

  • Default Value 30

  • Value range: > 0

Unit History Active

If this flag is set then all the units created by the Scheduler are logged with their processing status.

Note Note

You can display these logs with transaction SBGRFCHIST.

End of the note.
Additional Settings
Check Class

If you want to define an access protection in addition to the bgRFC authorizations that already exist for processing queues and units or for the schedule configuration, you can enter a relevant class here. To activate the write protection, set the active/inactive flag.

Note Note

Check classes can be implemented using the following interfaces:

  • IF_BGRFC_APPL_CHECK_MON_IN (Inbound Scheduler)

  • IF_BGRFC_APPL_CHECK_MON_OUT (Outbound Scheduler)

End of the note.