Showing results for 
Show  only  | Search instead for 
Did you mean: 

IdentityIQ tracing for SAP Direct (JCO and RFC Tracing)

IdentityIQ tracing for SAP Direct (JCO and RFC Tracing)

Beyond the IdentityIQ Connector logging available via log4j, there is additional tracing options for the SAP Direct connector. This additional traces uses the tracing available via the SAP JCO libraries.


This is only recommended for use in non-production or for specific troubleshooting. It will result in large trace files and will greatly impact performacne of IdentityIQ.


For all options below, this parameter needs to be added to the java start up options (either CATALINA_OPTS or JAVA_OPTS):

     -Djco.trace_path=<path to logfiles>   (Example:  -Djco.trace_path=c:/jco/logs)


The first option is for rfc level tracing of each connection from identityiq to a sap application. This will create jco_rfcXXXXX.trc files in the jco.trace_path specified in the java start up options. This is done on a per-application basis.

  1. Open IdentityIQ and navigate to the Debug page

  2. Open the Application that tracing is desired

  3. Add this entry into the application xml: <entry key="jco.client.trace" value="1"/>

  4. Remove the entry to discontinue tracing


The second option is for JCO level tracing. This option applies tracing to all JCO calls for all applications.  This will create JCO######.trc files in the jco.trace_path directory. The additional details link at the bottom of this document details the different jco.trace_level options

  1. Add -Djco.client.trace=1 and -Djco.trace_level=X to the JAVA_OPTS or CATALINA_OPTS in the application server startup files.

The value of X will be a number between 0 (no tracing) and 8 (maximum tracing)

Both options can be combined to provide extensive tracing of the SAP communications.

Version history
Revision #:
3 of 3
Last update:
‎Aug 11, 2023 01:14 AM
Updated by: