Skip to main content

RFC Trace File

The agtsapnw connector provides the Engage RFC trace logging target system address configuration option to allow for enabling RFC trace diagnostics and logging.

By default this is set to 0 which means that logging is turned off. This option can be set to the following log levels:

0

off

1

brief

2

verbose

3

full

When logging is enabled, a log file is created in the <Program Files path>\Bravura Security\Bravura Security Fabric\Logs\<instance> directory in the following format: rfc<PID>_<THREAD>.trc, where <PID> and <THREAD> are the initial rfc connect.

The log file contains various information such as:

  • Initial RFC options (parameters) passed into the connect.

  • Any errors, warnings, etc such as for example, authorization issues.

  • RFC calls that are made, for example:

    2024-03-02 02:13:46.582751 [39084] >> RfcGetFunctionDesc

    RfcGetFunctionDesc(BAPI_USER_GET_DETAIL) via handle 2133721882624

  • Table or row information passed back from RFC function calls, for example:

    BAPI_USER_GET_DETAIL

In this section: