Solution : https://service.sap.com/sap/support/notes/628962 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the configuration and utilization of trace files for the diagnosis of issues in SAP Java Connector (JCo). To generate trace logs, users can set up start-up parameters (-Djco.trace_level and -Djco.trace_path) in the Java Virtual Machine or use API methods (JCO.setTraceLevel() and JCO.setTracePath()) within their Java programs. Additionally, SAP JCo enhances RFC tracing through JCO.Client.setTrace() and JCO.Server.setTrace() for toggling logging at client or server levels. For J2EE servers, traces can be activated at startup using configuration tools or at runtime via NWA or Visual Administrator, depending on the version. Trace levels range from 0 (disabled) to 5 (detailed for error diagnostics).
Key words :
start <sap j2ee 640 installdir>\usr\sap\<sid>\<instid>\j2ee\configtool\configtool, start <sap j2ee 700 installdir> \usr\sap\<sid> \<instid>\j2ee\admin\, sap j2ee engine solution standalone application, server<node#> -> services -> jco rfc provider, j2ee/cluster/server /log directory, 10 / sap netweaver 04s / sap netweaver 04, sap j2ee visual administrator, sap jco jni api, jco sap jco offers, sap java application server
Related Notes :
| 1340604 | Locomotive Management System Tracing Procedures |
| 1261193 | |
| 947376 | Troubleshooting JCo and AdaptiveRFC in Web Dynpro for Java |
| 645876 | |
| 636912 | Frequent installation problems with SAP Java Connector |
| 532918 | RFC trace generation scenarios |