You enable RFC tracing with the Enable RFC Trace property. The trace file contains RFC API calls, and data sent to and received from the SAP R/3 host. The trace file is rfcnumber.trc.

For example, rfc00310_0156.trc

Yes or No.

The default mode is No; the RFC tracing is disabled.

If the Enable RFC Trace parameter is set to Yes, then it creates both the JCo and RFC Trace logs. Both are created in the same location under:

appserver\domains\domain1\
config

The JCoTrace log provides Java Runtime, version, and path information. It also provides a manifest.

If Enable RFC Trace parameter is set to No, then no trace file is generated.

Trace level specifies the complexity of the information in the trace file. 0 provides minimal trace logging and 5 provides the maximum trace logging of diagnostic information in the trace file.

Integer value from 0 (min) to 5 (max).

The default number is 0.

The Enable RFC Trace level only affects the JCo trace level. It has no effect on the RFC trace level.

Specify the number of RFC servers to create. The created RFC servers facilitate parallel processing when receiving multiple requests from SAP R/3.

A valid integer value.

The default number is 1.

Specifies the transaction mode. The transaction mode specifies whether tRFC is enforced. With RFC, transactions have unique TIDs and are processed only once by this Adapter.

A transaction mode of Non-Transactional or Transactional RFC(tRFC).

The default mode is Non-Transactional.

Specifies the location of the Transaction ID Verification database.

Specify the name of the file-based database which persists the TIDs. Provide the path to the database file that records the disposition of all transactions outgoing from this Adapter. The database records whether transactions are:

• C (committed)

• U (unprocessed or rolled-back)

• R (reserved or pending)

A valid path to the database file.

For example, the default location is:

C:\JavaCAPS6\data\SapTRFC.TIDdb