If unexpected behavior or errors occur during runtime you should check the system log output first. It usually provides clues as to the cause of the error or unexpected behavior. The PPM system uses the log4J interface to output system messages. This enables you to obtain more detailed information on the error cause by changing the configuration of the output of system messages by adjusting (refining) the log levels during PPM server runtime. Chapter PPM system messages describes the configuration of system message output in detail. Connection to external support desk systems, such as SAP Solution Manager, is not supported by PPM.
If errors occur during the import of data or configuration the log output of the PPM system is very important for the analysis. First, you analyze the messages of the import program on the console or in the log file specified. Many times, you can already determine the cause of the error this way. The chapter on Command line programs describes in detail how to handle system message output of command line programs. The system messages of the PPM client and analysis servers can support your error analysis. PPM client and analysis servers each write their system messages in a file. The location where these files are saved is specified in the relevant appenders in the file Server_Log_settings.properties or Analysisserver_Log_settings.properties. The default directory is <installation directory<\ppmmashzone\server\bin\work\data_ppm\log\<client>; the log files have the name pattern <client>_<type>.log, and analysis server log files have the suffix _as following the client name. For example, the analysis server of the umg_en client writes error messages to the file umg_en_as_error.log in the <installation directory>\ppmmashzone\server\bin\work\data_ppm\custom\umg_en\log\.
System messages of the PPM servers can be processed in different ways, e.g., by using individual appenders. Chapter System messages (log output) describes in detail the configuration of system message output.
Errors occurring during the analysis using the PPM front-end are displayed in the front-end session in a separate dialog window. You can add the output of the program's run time messages (stack traces) to the system message display. To do this, click the error dialog's Details button.
If you report an error to the manufacturer's support your message needs to include the following information:
You can determine the versions of the software installed as follows:
All applications always use the same Java version.
To identify the version, execute the command line <installation directory>\ppmmashzone\server\jre\bin\java -version in a command prompt.
Example
C:\> SoftwareAG\ppmmashzone\server\jre\bin\java -version
To determine the PPM version installed, execute the runppmreport command line program with the option -version.
Example
C:\> cd SoftwareAG\ppmmashzone\server\bin\agentLocalRepo\.unpacked\ppm-client-run-prod-95.1.0-RC8-trunk-20130404.122823-4-runnable.zip\ppm\bin & runppmreport -version
S: 21.04.11 08:59:16: [SRV] application: 95.1.0 (10055)
S: 21.04.11 08:59:16: [SRV] database schema: 95
When starting, the PPM server outputs messages stating which database and JDBC driver versions are used. You can also retrieve this information from the server's log files.
Examples
I: ...: [SRV] Database version used: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
I: ...: [SRV] JDBC driver used: Oracle JDBC driver (10.2.0.4.0).
I: ...: [SRV] Database version used: SQL09013.
I: ...: [SRV] JDBC driver used: IBM DB2 JDBC Universal Driver Architecture (3.4.65).
I: ...: [SRV] Database version used: 8.00.2039.
I: ...: [SRV] JDBC driver used: Microsoft SQL Server 2005 JDBC Driver (1.1.1501.101).