5.1 Overview of the system log information extraction function

You can use PFM - Agent for Enterprise Applications to output periodically to text files the system log information that constitutes a record of the events and errors that occur in the SAP system. The system log information extraction function provided by PFM - Agent for Enterprise Applications can output the following system log information to a text file:

Message recording time
Server that recorded the message
User who recorded the message
Program that recorded the message
Message number
Message

By linking other programs, you can use the system log information in a text file to monitor the status of the SAP system. This section presents an example of status monitoring by linking to JP1/Base and JP1/IM.

The log file trapping function of JP1/Base enables you to convert system log information to JP1 events. By monitoring these JP1 events from JP1/IM, you can monitor the status of the SAP system from JP1/IM.

The following figure shows an example of monitoring the status of an SAP system by linking PFM - Agent for Enterprise Applications with JP1/Base and JP1/IM.

Figure 5‒1: Example of monitoring the status of an SAP system by linking with JP1/Base and JP1/IM

There are two different file formats used by PFM - Agent for Enterprise Applications to store system log information. They are described below.

WRAP1 format

This file is in wraparound format, which means that data is overwritten when the amount of system log information reaches a specified value. There is a header line of management information at the beginning of the file. Only one WRAP1-format file can be used for storing system log information. If you use the WRAP1 format to monitor system log information, specify the following parameters in the operation definition file:
```
FILETYPE=WRAP1
HEADLINE=1
```
WRAP2 format

In this file format, when the amount of system log information reaches a specified value, all data in the file is deleted and then new data is written from the beginning of the file. Multiple WRAP2-format files can be used to store system log information. If you use the WRAP2 format to monitor system log information, specify the following parameter in the operation definition file:
```
FILETYPE=WRAP2
```

Note

To monitor the SAP system log in SAP NetWeaver PI 7.1 or SAP NetWeaver PI 7.1 EHP1 of the prerequisite software on the same unit, you must add the following parameter to the SAP profile. You must also change the SAP system log collection method from HTTP to RFC.

This is because the SAP local system log collection method for the SAP central log function is set to HTTP by default.

rslg/central/log/new = 0

Once you make this setting, the SAP central function, which is a prerequisite of HTTP, is disabled. Therefore, check the effect on applications that use the SAP central function before the change. Note that this change does not affect PFM - Agent for Enterprise Applications because it does not use the SAP central function.
The maximum length of a message might be less than 255 bytes depending on the version of the SAP system you use. This occurs because the maximum length of a message returned from a SAP system differs depending on the version of the SAP system.
When the jr3slget command is executed directly to extract system log information while the TZ environment variable is defined in the command execution environment, problems might occur such as abnormal command termination or extracted system log information for invalid time ranges. As such, do not define a time zone for the TZ environment variable of the command execution environment. The applied time zone will be the one defined in the Windows Date and Time Properties dialog box.

To Page Top