You can view logs that are generated by the JSPM. You can also view logs generated by other applications that are integrated with the JSPM, for example, the SDM.
If JSPM is started, you can view logs using the integrated Log Viewer in the JSPM. If JSPM cannot be started, you can view LOG files with any text viewer or editor.
All logs that are generated by JSPM are stored in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/log directory. In addition, all logs that are generated by the SDM are copied to this directory.
You can view logs both from the current logon session and from previous sessions. Logs from every session are written to a subdirectory whose name contains the time stamp of the session.
The following table describes the most important log files and their content:
Log File | Contains Information About |
---|---|
JSPM_MAIN.LOG | Main JSPM processes. It may contain references to other log files that are generated by the JSPM or by other integrated applications, for example, the SDM. |
SCAN_INBOX.LOG | The scan of the content of the global EPS inbox directory. |
DETECT_SYSTEM_PARAMETERS.LOG | The system parameters that JSPM has detected during startup. |
DETECT_SYSTEM_COMPONENTS.LOG | The components deployed on the system that JSPM has detected. |
SDM_OPERATION.LOG | The update of the SDM. |
ENGINE_OPERATION.LOG | Starting and stopping of the system. |
EXCHANGE_KERNEL_BINARIES.LOG | Kernel update. |
EXCHANGE_IGS_BINARIES.LOG | IGS update. |
In addition to LOG files, you can view OUT and ERR files, which are standard output and error streams from external processes.
Each log message has a severity level. A severity level denotes the level of importance of a given record. The following are the possible severity levels with an increasing severity:
- DEBUG
Logs with this severity contain extensive and low level information that is relevant to debugging.
- PATH
Logs with this severity contain information that is relevant to tracing the execution flow, for example, entering and leaving a method.
- INFO
Logs with this severity contain information about what has been performed.
- WARNING
Logs with this severity are generated when the application can recover from an anomaly and perform a required operation, but attention from a user is required.
- ERROR
Logs with this severity are generated when the application can recover from an error but cannot perform a required operation due to the error.
- FATAL
Logs with this severity are generated when the application cannot recover from an error and the severe situation causes fatal termination.