Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference

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 - View.

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 - View, you can monitor the status of the SAP system from JP1/IM - View.

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 - View.

Figure 5-1 Example of monitoring the status of an SAP system by linking with JP1/Base and JP1/IM - View
Note

The text file to which PFM - Agent for Enterprise Applications outputs system log information is in wraparound format, which means that data is overwritten when the capacity reaches a specified value. There is a header line of management information at the beginning of the file. If you use JP1/Base's log file trapping function to monitor this file, specify the following parameters in the log file trap definition file:
 
FILETYPE=WRAP1
HEADLINE=1
To monitor the SAP system log in SAP NetWeaver PI 7.1, you must change the SAP profile. This is because the default SAP local system log collection method is set to HTTP in the SAP central log function, so you must change HTTP to RFC. Specifically, add the following parameter to the SAP profile:
rslg/central/log/new = 0
Once you make this setting, the SAP central log function that requires HTTP will be disabled in a Windows version. This is not a problem if you use a JP1 product to collect SAP local system logs to achieve central management, because the SAP central log function is not used. There are no other limitations to the SAP NetWeaver functions.

[Contents][Back][Next]

[Trademarks]