Question & Answer
Question
How can we configure JCO tracing for SAP JCo independently from the WebSphere Adapter for SAP Software?
Answer
The information contained in this document has been moved to developerWorks Answers located here. This technote will be archived in 60 days. Please bookmark the new location.
The WebSphere Adapter for SAP Software V6.0, V6.1, or V6.2 uses SAP JCo V2.1.8 to connect to and exchange data with the SAP EIS (Enterprise Information System). Version 7 of the adapter uses SAP JCo V3.0.x.
SAP JCo has two levels of tracing - RFC tracing (this is tracing from the DLL/SO files - native library tracing) and JCO tracing (tracing by the Java™ code which invokes the libraries).
The following steps describe how to activate the JCo tracing on your application server independently from the WebSphere Adapter for SAP Software configuration using command-line parameters.
Open the Administration Console for WebSphere Process Server
- Select the "Configuration Tab".
- Select "Server Infrastructure" -> "Java and Process Management"
- Select "Java Virtual Machine"
- In "Generic JVM Arguments" insert the following parameter:
-Djco.trace_level=<int> -Djco.trace_path=<path>
For example,
'-Djco.trace_level=5 -Djco.trace_path=.'
According to SAP Note 628962, a trace level of 5 for diagnostics is recommended for JCo 2.1.x and trace level 8 for JCo 3.0.x.
Further trace levels (taken from SAP Note 628962):
- "0: no trace files are written
1: logging of the SAP JCo Java API is switched on
3: logging of the SAP JCo JNI API is switched on
5: important information for error diagnostic is switched on "
Note that the adapter JCo tracing activation will be ignored when setting the trace globally using JVM parameter.
Further information on SAP JCo tracing such as trace levels can be found from the related links.
Related Information
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21404884