RFC Settings allow you to override the default behavior of the ABAP Agent in areas like exit-call handling and backend naming. To configure data collectors for business transactions, maintain data collectors under
Instrumentation settings.
By default, unresolved RFC backends (remote services) generated by the ABAP Agent have technical names RFC_<host/program>. This behavior can be changed using the Verbose RFC backend names checkbox.
| RFC Destination Type | Default Name | Verbose Name |
|---|
| ABAP Connection | RFC_<hostname> | RFC ABAP: <description>* (<hostname>) |
| TCP/IP Connection | RFC_Program: <program> | RFC TCP: <description>* (Program: <program>) |
*When SM59 description text is empty, the RFC destination name is used instead
Exit calls to RFC destination types not listed here are not supported.
RFC exit call support depends on specific Business Transaction type. See Match Rule Types.
When remote services with default names are already registered on the controller, they need to be manually deleted and all HTTP SDK instances must be restarted before remote services with verbose names appear.
Several components of the ABAP Agent attempt to continue business transactions in RFC exit-calls using custom RFC function module calls to the RFC destination target system. When the custom RFC call fails, an automatic RFC blacklist functionality silences the problematic RFC destination for one hour. RFC destinations are blacklisted if:
- ABAP Agent (ABAP Connection) or JCo extension (TCP/IP Connection) is not installed on the RFC destination target system.
- User associated with the RFC destination does not have sufficient authorizations to call function modules /DVD/APPD_RFC* on the target system. See ABAP Agent Authorizations.
This automatic behavior can be adjusted using the RFC Blacklist settings. When Make automatic blacklist entries permanent is checked, RFC destinations with problems will remain blacklisted until they are removed or adjusted manually.
The RFC Settings tab contains a table with all RFC blacklist records. Existing records can be toggled between permanent and temporary, and new blacklist entries can be added manually. When new RFC destinations are added to the blacklist without the Mark as Permanent flag, a timestamp with current date and time is added to them as soon as the settings are saved.