Solution : https://service.sap.com/sap/support/notes/761921 (SAP Service marketplace login required)
Summary :
In SAP Exchange Infrastructure (XI), when facing issues with Java message processing and existing monitoring tools are insufficient, it's crucial to generate a trace file to diagnose the error. For environments like SAP XI/PI 3.0 and 7.0, one should use the Visual Administrator to adjust LogManager properties and Log Configurator settings. For Release XI 7.1, adjustments are made via the Config Tool and SAP NetWeaver Administrator. Properties like ConsoleLogs_UseSapAPI and ForceSingleTraceFile should retain their default settings to ensure no trace entries are overshot in the shared trace file. An advanced understanding of log management and tracing settings is pivotal for isolating and troubleshooting issues effectively.
Key words :
/usr/sap/[sid]/[instance]/j2ee/admin/logviewer-standalone/logviewer, directory/usr/sap/[sid]/[instance]/j2ee/cluster/server[, /usr/sap/[sid]/[instance]/j2ee/configtool/configtool, /usr/sap/[sid]/[instance]/j2ee/cluster/server[, instance -> log configuration -> destinations -> default_trace, global configuration -> server -> kernel -> logmanager, remote j2ee instance, j2ee instance number, command line log viewer, ]/log/systemcontains trace files
Related Notes :
| 1342846 | How to trace received MDM events by PI Adapter |
| 1330975 | Creating custom trace locations in Visual Administrator |
| 870270 | FAQ note for initiating Support related to ISpeak Adapters |
| 854536 | Adapter Framework: Information Required by SAP Support |
| 751915 | Differences between trace, log and audit log |
| 749197 | How to transfer Java log files to SAP and analyze them |
| 40024 | Transferring customer files to sapserv# using ftp |