This article explains which file to look in and which components are likely to write entries.

SystemOut.log file holds the key messages

The key messages are stored in the SystemOut.log file and to a lesser extent the SystemErr.log file.

I discussed the SystemOut.log file in this article:

http://www.linkedin.com/pulse/introduction-most-important-maximo-log-file-mark-robbins

If you are starting a JVM then it is critical to check the log messages stored in this log.

The SystemErr.log file is normally used to log errors and should be checked for entries generated during the startup process.

Some of the key components mentioned in the log file

There are lots of components referenced in the log file and this series will reference the following ones:

• Database – this is used to store Maximo details/records
• JMS Engine / JMS Connection Factory – this is used to store details
• Websphere applications – these contain the code to be executed e.g. the Maximo class files
• EJB components – Components used to allow Websphere/Maximo connect to the outside world via network ports/URLs

This isn't a complete list. Vetasi supported customers can request a copy of the guide with the full list of components and messages.

Some components will be started by Websphere and will generate Websphere messages while others will be Maximo and so will have the Maximo log format.

This is an example of a Websphere message note the I indicating an Informational message.

• [9/19/18 22:03:05:940 BST] 0000000a ManagerAdmin I  TRAS0017I: The startup trace state is *=info.

This is an example of a Maximo message. Note the O indicating it is a Websphere output message – the output being provided by the Maximo application

• [9/19/18 22:04:40:978 BST] 0000006a SystemOut    O 19 Sep 2018 22:04:40:978 [WARN] [] [] BMXAA6422W - The value for MAXPROP mxe.mt.demo.extratenants could not be cached. The name in the properties file is not defined in the MaxProp table.

 I'll discuss some of the important messages in the following weeks.