IBM Maximo: My Configuration Tips: Difference between revisions

From Wiki
(Criou a página com " = System Properties= * mxe.mbocount=1 :This property is used to capture snapshot intervals of memory usage. * mxe.db.logSQLTimeLimit=1000 :Registrar as operações SQL...")
 
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
= System Properties=


Para detalhes veja artigo [[IBM Maximo: System Properties]]
mxe.crontask.donotrun and mxe.crontask.dorun
mxe.db.logSQLTimeLimit=1000
mxe.db.closelongrunconn=true
mxe.db.longruntimelimit=60
mxe.db.detectlongrunconninterval=30
mxe.mbocount=1
mxe.logging.CorrelationEnabled=1


= System Properties=


* mxe.mbocount=1
Caso esteja atrás de um load balancer
:This property is used to capture snapshot intervals of memory usage.


* mxe.db.logSQLTimeLimit=1000
mxe.system.usingLoadBalancer=1
:Registrar as operações SQL que excedem o limite de tempo (milissegundos)


* mxe.crontask.donotrun and mxe.crontask.dorun
= Java Virtual Machine =
:define a execução de Crontasks
* [[IBM Maximo: Java Virtual Machine Properties for IBM WebSphere]]


= Logging =
= Logging =


* Maximo DB Connection watchdog logger (log4j.logger.maximo.dbconnection)
* Maximo DB Connection watchdog logger (log4j.logger.maximo.dbconnection)=INFO
: Define to INFO. Generate this message on logs. BMXAA7084I - The DbConnectionWatchDog class has been trying to close the database connection for:
: Define to INFO. Generate this message on logs. BMXAA7084I - The DbConnectionWatchDog class has been trying to close the database connection for:
= Crontask & Escalation =
== Reduce CronTask History ==
Crontask/Escalation can store the task execution times. This feature is enable when mark ‘'''Keep history'''’ checkbox in crontask. This information is recorded in CRONTASKHISTORY table
I use the following table to define history records and reduce the size of CRONTASKHISTORY table:
{| class="wikitable"
|-
! Schedule !! History Records !! Description
|-
| less than 1d  || 100 || -
|-
| 1d to 1 week || 100 || history of the last 100 days (3 months)
|-
| 1w or greater || 10 || history of the last 10 weeks (3 months)
|}
== Disable unused Crontask ==
'''Important: Check if you not use these crontasks before disable it'''
* InstDepreciationCronTask – Asset depreciation calculator, if not used.
* KPICronTask
* Old Infolink Crontask - check for error BMXAA1477E on logs
= Communication Templates =
== Disable Comm Log Entry ==
In Communication Templates, there is a checkbox called '''Comm Log Entry''' which when checked records an entry in the COMMLOG table.
Disabling reduce database transaction and reduce size of table COMMLOG. Exists another checkbox '''Tracked Failed Messages?''', that record fails.


= Ver também =
= Ver também =

Latest revision as of 22:14, 23 June 2022

System Properties

Para detalhes veja artigo IBM Maximo: System Properties

mxe.crontask.donotrun and mxe.crontask.dorun
mxe.db.logSQLTimeLimit=1000
mxe.db.closelongrunconn=true
mxe.db.longruntimelimit=60
mxe.db.detectlongrunconninterval=30
mxe.mbocount=1
mxe.logging.CorrelationEnabled=1


Caso esteja atrás de um load balancer

mxe.system.usingLoadBalancer=1

Java Virtual Machine

Logging

  • Maximo DB Connection watchdog logger (log4j.logger.maximo.dbconnection)=INFO
Define to INFO. Generate this message on logs. BMXAA7084I - The DbConnectionWatchDog class has been trying to close the database connection for:


Crontask & Escalation

Reduce CronTask History

Crontask/Escalation can store the task execution times. This feature is enable when mark ‘Keep history’ checkbox in crontask. This information is recorded in CRONTASKHISTORY table

I use the following table to define history records and reduce the size of CRONTASKHISTORY table:

Schedule History Records Description
less than 1d 100 -
1d to 1 week 100 history of the last 100 days (3 months)
1w or greater 10 history of the last 10 weeks (3 months)

Disable unused Crontask

Important: Check if you not use these crontasks before disable it

  • InstDepreciationCronTask – Asset depreciation calculator, if not used.
  • KPICronTask
  • Old Infolink Crontask - check for error BMXAA1477E on logs


Communication Templates

Disable Comm Log Entry

In Communication Templates, there is a checkbox called Comm Log Entry which when checked records an entry in the COMMLOG table.

Disabling reduce database transaction and reduce size of table COMMLOG. Exists another checkbox Tracked Failed Messages?, that record fails.

Ver também