Viewing Log Files 

Use

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 in a human readable format using the Log Reader.

By default, all logs that are generated by the 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.

You can filter and view list formatted logs with different severity levels. 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.

Procedure

...

Viewing Logs Using the Integrated Log Viewer in the JSPM

       1.      To view log files, choose the Logs tab.

If You Want To	Then
View a log from the current logon session	In the navigation area on the left, browse Log Files ® Current Log Files and select the log file you want to view.
View a from a previous logon session	In the navigation area on the left, browse Log Files ® Old Log Files and from the subdirectory whose name contains the time stamp of the session you want to view, select the log file you want to view.

Log files are displayed in one of the following ways:

○     List formatted – all records are displayed in a table. The newest record is displayed at the bottom.

○     Non list formatted – only the complete message text is displayed.

       2.      Filter and search the log files.

If You Want To	Then
Filter the list formatted log files by severity level	...        1.      From the <Select Severity> dropdown box, select the severity level you want. Log records with the selected severity level are displayed in a table. The newest record is displayed at the bottom.        2.      To display all list formatted log records again, from the <Select Severity> dropdown box, select All Severities.
Search for a string in the complete message text of a non list formatted log file	Choose  Find, enter the string you want and choose Find.

Viewing Logs Using the Log Reader

...

       1.      In the file system, go to the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/log directory.

       2.      To start the Log Reader, run the log_reader script file.

       3.      If you want to convert a LOG file to a human readable format and save it as a new file, enter the following command:

○     On Microsoft Windows:

log_reader.bat <Full path to source file> <Full path to destination file>

○     On UNIX:

log_reader.sh <Full path to source file> <Full path to destination file>.

The LOG file is converted to the format that you have specified and it is saved to the directory that you have specified.

       4.      If you want to view a LOG file in a human readable format in the command line, enter the following command:

○     On Microsoft Windows:

log_reader.bat <Full path to source file>

○     On UNIX:

log_reader.sh <Full path to source file>.

The LOG file is converted to a human readable format and it is displayed in the command line.