What are the various traces generated by the TIBCO Adapter (TM) for SAP R/3?
Article ID: KB0088500
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
Description:
---------------
SAP adapter can generate three types of trace messages i.e., Information, Warning and Error. Informational messages indicate the normal adapter behavior, Warning message indicate an abnormal condition was found and Error messages indicate that an unrecoverable error occurred. Please note that SAP Adapter does not support debug traces i.e. the adapter does not create more detailed traces in the adapter log file if debug level tracing is enabled.
Adapter also generates additional trace files under the adapter home directory(by default) when tracing and debugging parameters like RFC_TRACE, ABAP Debug and USe SAPGUI are enabled in the adapter configuration.
ABAP Debug can be used to debug custom/standard RFC by setting it to “ON” for corresponding Client under R3Connections folder. When ABAP Debug is enabled, the adapter opens up the SAP GUI, and then you can debug your ABAP code in SAP.
Please note that to use ABAP debug, you should have SAP GUI installed on the machine on which the adapter is being executed.
When you are running adapter to execute RFC at SAP and when that particular RFC is invoked then a SAP GUI will be invoked and you will be able to debug the execution of RFC along with data received. Please note that you need to have SAPGUI installed in the same machine where the adapter is running to use ABAP Debug and SAP GUI is pre-requisite to use this feature. Please refer to TIBCO Adapter for R/3 User’s Guide-->Chapter 4 Configuring the Adapter with Advanced Options for further details.
When the RFC TRACE is "ON", interactions between Adapter and SAP is logged in the adapter log, .trc and CPITRC files. This trace file can be generated by enabling tracing in SAP or in SAP adapter. For more details on how to enable the RFC trace, please refer to solution SOL1-A7K66R. Although the RFC trace can be turned on to see more traces, we cannot read the data using them. Since this an extensive detailed logging this can slow down the performance of the adapter.
In case of any SAP related errors are thrown, the adapter will log entries in the dev_rfc.trc file, by default.
Environment :
--------------------
Operating System: All
Description:
---------------
SAP adapter can generate three types of trace messages i.e., Information, Warning and Error. Informational messages indicate the normal adapter behavior, Warning message indicate an abnormal condition was found and Error messages indicate that an unrecoverable error occurred. Please note that SAP Adapter does not support debug traces i.e. the adapter does not create more detailed traces in the adapter log file if debug level tracing is enabled.
Adapter also generates additional trace files under the adapter home directory(by default) when tracing and debugging parameters like RFC_TRACE, ABAP Debug and USe SAPGUI are enabled in the adapter configuration.
ABAP Debug can be used to debug custom/standard RFC by setting it to “ON” for corresponding Client under R3Connections folder. When ABAP Debug is enabled, the adapter opens up the SAP GUI, and then you can debug your ABAP code in SAP.
Please note that to use ABAP debug, you should have SAP GUI installed on the machine on which the adapter is being executed.
When you are running adapter to execute RFC at SAP and when that particular RFC is invoked then a SAP GUI will be invoked and you will be able to debug the execution of RFC along with data received. Please note that you need to have SAPGUI installed in the same machine where the adapter is running to use ABAP Debug and SAP GUI is pre-requisite to use this feature. Please refer to TIBCO Adapter for R/3 User’s Guide-->Chapter 4 Configuring the Adapter with Advanced Options for further details.
When the RFC TRACE is "ON", interactions between Adapter and SAP is logged in the adapter log, .trc and CPITRC files. This trace file can be generated by enabling tracing in SAP or in SAP adapter. For more details on how to enable the RFC trace, please refer to solution SOL1-A7K66R. Although the RFC trace can be turned on to see more traces, we cannot read the data using them. Since this an extensive detailed logging this can slow down the performance of the adapter.
In case of any SAP related errors are thrown, the adapter will log entries in the dev_rfc.trc file, by default.
Environment :
--------------------
Operating System: All
Issue/Introduction
What are the various traces generated by the TIBCO Adapter (TM) for SAP R/3?
Feedback
Yes
No
Powered by
