IBM Support

Logging to isolate and resolve problems

Technical Blog Post


Abstract

Logging to isolate and resolve problems

Body

Logging is not just the felling of trees and the cutting and preparing of timber for future use. Logging has different meanings, and so different purposes in different contexts. The purpose of Maximo logging functionality and its usage, is to provide you with meaningful and easy configurable logging to isolate and resolve problems quickly. In version 7.5.0.3 the information on logging has been enhanced.

The new content includes information on a new logger that leverages new OSLC capabilities.You can use the OSLC logger to identify any OSLC-based processing errors that are reported, and to determine what log level to set the OSLC logger to, in order to maximize the amount of information that is output to the log file.
 
A new feature, log correlation, was added in 7.5. In 7.5.0.3, information on log correlation and log correlation for UI requests is also provided in the new content. Information on integration framework, escalation, cron task, and automation script loggers and log levels has also been added. For more information see the information center here

Log file statements can sometimes be difficult to interpret, so a new scenario has been added to the wiki on SMC that details how to interpret log statements to resolve errors when application and SQL loggers are enabled. For more information, see this scenario on developerWorks here.


[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11134243

Page Feedback