There are several tasks relating to managing your log files, such as specifying log file formats and locations, and associating loggers with appenders.
Creating logging.properties files
If you do not want to replicate the same logging configuration
on all of your servers, maintain a separate logging.properties file
on each server instance.
Managing appenders
You can create, change, or delete appenders in the Logging
application.
Automation scripts loggers
All logging that is related to scripts is done by the autoscript
logger. The log level is set, by default, to ERROR. Only errors that
are encountered during script execution, are output to the system
console or to the product log file.
Cron task loggers
When cron tasks fail to run successfully, the root logger
cron task can be set to different levels to obtain more detailed logs.
If a particular cron task fails to run successfully, additional loggers
can be set up to isolate the cause of the failure.
Escalation loggers
If an escalation fails to run, the failure can be caused
by the escalation engine, the email notifications, or actions triggered
by the escalation. You can troubleshoot the cause of the failure by
setting the correct log level.
Integration framework loggers
The integration framework has four root loggers: integration,
REST, interaction, and Open Services Lifecycle Collaboration (OSLC).
To receive the maximum amount of information set the root loggers
to DEBUG.
Enabling the EventTracker filter
To enable the EventTracker filter, uncomment
the filter definition and filter mapping in the web.xml file,
which is located in Tpae root\applications\maximo\
maximouiweb\webmodule\WEB-INF\ directory.
Configuring custom log messages to help resolve bugs
To
identify the section of a log file that contains statements or messages
that are relevant to product use, problem creation, or a debugging
activity, you can configure custom log messages. You specify start
and end messages that are included in the log file. You can review
the statements or messages that are shown in between the custom log
start and end messages in the log file to help you trace a scenario
or resolve an issue.
Scenario: Interpreting log file statements to resolve errors
Marco, a system administrator, wants to isolate and resolve
an error that occurs when someone tries to save a work order. Marco
can troubleshoot the problem by setting the Word Order Tracking root
logger to DEBUG and the SQL root logger to INFO.