Question & Answer
Question
Can Loggers not visible in the Logging application "out of the box" be made visible?
Answer
Out of the box Root Loggers cannot be deleted. In certain upgraded environments, these loggers do not appear in the Logging application, because of incorrect MAXLOGGERID to PARENTLOGGERID references. Below are the out of the box MAXLOGGER tables for Maximo 7.6.1.2, and the corresponding Loggers that should appear under the Root Loggers. If these values don't appear in the Logging application, you will need to update the MAXLOGGER table with a SQL editor to change PARENTLOGGERID values to the correct MAXLOGGERID.
For example, the sql Root Logger has three Loggers:
Out of the Box Loggers
LOGGER | DEFAULT VALUE | LOGKEY | MAXLOGGERID |
---|---|---|---|
sql |
ERROR |
log4j.logger.maximo.sql |
1 |
|
INFO |
log4j.logger.maximo.sql.crontask.EmailNotification |
19 |
|
ERROR |
log4j.logger.maximo.sql.crontaskmgr |
37 |
|
INFO |
log4j.logger.maximo.sql.WORKORDER.WOSTATUS |
13 |
service |
ERROR |
log4j.logger.maximo.service |
2 |
|
ERROR |
log4j.logger.maximo.service.BIRTREPORT |
31 |
|
INFO |
log4j.logger.maximo.service.CONFIGURE |
11 |
|
INFO |
log4j.logger.maximo.service.SYSTEM.IBMCONTENTCATALOG |
46 |
|
INFO |
log4j.logger.maximo.service.WORKORDER |
10 |
|
INFO |
log4j.logger.maximo.service.WORKORDER.WOSTATUS |
12 |
application |
ERROR |
log4j.logger.maximo.application |
3 |
|
INFO |
log4j.logger.maximo.application.rsconfig |
41 |
|
INFO |
log4j.logger.maximo.application.scconfig |
51 |
|
INFO |
log4j.logger.maximo.application.WOTRACK |
14 |
workflow |
ERROR |
log4j.logger.maximo.workflow |
4 |
crontask |
ERROR |
log4j.logger.maximo.crontask |
5 |
|
INFO |
log4j.logger.maximo.crontask.ESCALATION.ESCRECONTICKET |
39 |
|
INFO |
log4j.logger.maximo.crontask.LSNRCRON |
17 |
|
INFO |
log4j.logger.maximo.crontask.KPICronTask |
15 |
|
INFO |
log4j.logger.maximo.crontask.LDAPSYNC |
16 |
|
ERROR |
log4j.logger.maximo.crontask.REPORTSCHEDULE |
32 |
|
INFO |
log4j.logger.maximo.crontask.ReconciliationCronTask |
18 |
|
INFO |
log4j.logger.maximo.crontask.ESCALATION.ESCTLOAMPROMOTE |
47 |
|
INFO |
log4j.logger.maximo.crontask.TLOAMSWKBT |
48 |
datadictionary |
ERROR |
log4j.logger.maximo.datadictionary |
6 |
mail |
ERROR |
log4j.logger.maximo.mail |
7 |
|
ERROR |
log4j.logger.maximo.mail.mfmail |
57 |
|
ERROR |
log4j.logger.maximo.mail.sendfailed |
58 |
event |
ERROR |
log4j.logger.maximo.event |
8 |
integration |
ERROR |
log4j.logger.maximo.integration |
9 |
security |
ERROR |
log4j.logger.maximo.security |
20 |
maximo |
INFO |
log4j.logger.maximo |
21 |
exception |
ERROR |
log4j.logger.maximo.exception |
22 |
dm |
ERROR |
log4j.logger.maximo.dm |
23 |
report |
ERROR |
log4j.logger.maximo.report |
24 |
|
ERROR |
log4j.logger.maximo.report.directprint |
65 |
|
ERROR |
log4j.logger.maximo.report.birt |
25 |
|
ERROR |
log4j.logger.maximo.report.birt.admin |
26 |
|
ERROR |
log4j.logger.maximo.report.birt.viewer |
33 |
|
ERROR |
log4j.logger.maximo.report.birt.queue |
34 |
|
ERROR |
log4j.logger.maximo.report.birt.admin.osgibundle |
27 |
|
ERROR |
log4j.logger.maximo.report.birt.script |
28 |
|
ERROR |
log4j.logger.maximo.report.birt.sql |
29 |
|
ERROR |
log4j.logger.maximo.report.birt.sql.script |
30 |
crontaskmgr |
ERROR |
log4j.logger.maximo.crontaskmgr |
36 |
dbconnection |
WARN |
log4j.logger.maximo.dbconnection |
38 |
interaction |
INFO |
log4j.logger.maximo.interaction |
40 |
uisession |
INFO |
log4j.logger.maximo.webclient.uisession |
42 |
autoscript |
ERROR |
log4j.logger.maximo.script |
43 |
SCHEDULER |
INFO |
log4j.logger.maximo.scheduler |
49 |
|
INFO |
log4j.logger.maximo.scheduler.ui |
75 |
SCHEDULERSQL |
ERROR |
log4j.logger.maximo.scheduler.sql |
50 |
REST |
ERROR |
log4j.logger.maximo.rest |
52 |
JMS |
ERROR |
log4j.logger.maximo.jms |
53 |
eventtracking |
INFO |
log4j.logger.maximo.webclient.eventtracking |
54 |
trace |
INFO |
log4j.logger.maximo.trace |
55 |
oslc |
ERROR |
log4j.logger.maximo.oslc |
56 |
lictrack |
ERROR |
log4j.logger.maximo.lictrack |
60 |
uiframework |
ERROR |
log4j.logger.maximo.webclient.uiframework |
61 |
|
ERROR |
log4j.logger.maximo.webclient.uicache |
62 |
expression |
ERROR |
log4j.logger.maximo.expression |
63 |
nullmbopointer |
ERROR |
log4j.logger.maximo.nullmbopointer |
66 |
tokenlic |
ERROR |
log4j.logger.maximo.tokenlic |
68 |
|
ERROR |
log4j.logger.maximo.tokenlic.checkinout |
79 |
|
ERROR |
log4j.logger.maximo.tokenlic.cleanupandlist |
80 |
jsoneditor |
WARN |
log4j.logger.maximo.jsoneditor |
69 |
mapcontrol |
ERROR |
log4j.logger.maximo.map |
70 |
srvad |
ERROR |
log4j.logger.maximo.srvad |
71 |
amcrew |
ERROR |
log4j.logger.maximo.amcrew |
72 |
OPTIMIZATION |
ERROR |
log4j.logger.maximo.service.OPTIMIZATION |
73 |
ODMADAPTER |
ERROR |
log4j.logger.maximo.optimization.odmadapter.sql |
74 |
linearasset |
WARN |
log4j.logger.maximo.linear.asset |
76 |
pushnotification |
ERROR |
log4j.logger.maximo.pushnotification |
82 |
digitaldata |
ERROR |
log4j.logger.maximo.digitaldata |
84 |
For example, the sql Root Logger has three Loggers:
EmailNotification - log4j.logger.maximo.sql.crontask.EmailNotification
crontaskmgr -
log4j.logger.maximo.sql.crontaskmgr
WOSTATUS - log4j.logger.maximo.sql.WORKORDER.WOSTATUS
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m50000000CbI0AAK","label":"System->Logging"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.0;7.6.1","Type":"MASTER"},{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"ARM Category":[{"code":"a8m500000008b3TAAQ","label":"Miscellaneous Category (Portal, UI, Maximo, Install)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.0;7.6.1","Type":"MASTER"}]
Was this topic helpful?
Document Information
Modified date:
30 August 2021
UID
swg21500757