Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

Maximo EAM post upgrade or update checklist 

Fri November 21, 2025 03:17 AM

Background:

After performing numerous Maximo EAM upgrades and updates, we found ourselves performing repeatable set of tasks to validate and confirm that the Maximo application works as expected. 

I would like to share what we termed as the "Maximo post upgrade/update checklist". This is a high level list and worked for most of our clients. 
 

The Checklist:

 

No.  Type Tasks
1 System Properties 1. Confirm and update Maximo System Properties - MAXPROPVALUE table.
    2. Run "Post refresh" SQL scripts.
2 Custom Java Classes Check and update custom class file names in MAXOBJECT/MAXOBJECTCFG/MAXATTRIBUTE/MAXATTRIBUTECFG tables. (These get reverted back to out-of-the-box class names by updatedb.bat.)
3 Attachments (DOCLINKS) 1. Check and update httpd.conf settings.
    2. Check and update System Properties.
    3. Check and update DOCLINKS, DOCINFO, DOCTYPES tables, as required.
    4. Copy ".../doclinks" folder from source server to new server/VM.
    5. Confirm users can attach documents.
    6. Confirm users can view documents.
    7. Confirm users can download documents.
4 BIRT Reports 1. Confirm reports run on BROS JVM.
    2. Check and confirm Direct Print.
    3. Confirm reports can be exported to PDF and Excel.
    *4. Check and run BIRT SQL?
    5. Confirm Barcode fonts (3of9) exist in Windows/Linux OS.
    6. Confirm "Scheduled" reports are running and emailed to end users.
5 Cron Tasks Confirm Cron Tasks are Active and running in Maximo.
6 Integrations (MIF/JMS) 1. Confirm JMS buses and message engines are running.
    2. Confirm JMS Sequential and Continuous Queues are working.
    3. Test and confirm inbound and outbound messages are working from/to Maximo.
    *4. Confirm Web Services are deployed and working.
7 Maximo configuration 1. Confirm UI session timeout.
    2. Run Integrity Checker in Report Mode and review log file for errors.
8 Browser compatibility Test Maximo in Edge (IE), Chrome and FireFox browsers.
9 Java Confirm IBM Java JDK version.
10 Server/VM 1. Check disk space and RAM on server/VM.
    2. Check and/or set system Date/Time and Time Zone.
11 WebSphere configuration 1. Check Clusters and JVMs (count and types).
    2. Check JVM ports and properties for each JVM.
    3. Check Virtual Hosts (count and ports).
    4. Check Global Security settings - (LDAP on or off).
    *5. Check LDAP configuration.
    *6. Check SSO configuration.
    *7. Import SSL certificates for external servers (e.g. LDAP, SSO, Web Services)
12 HTTPServer configuration 1. Check settings in httpd.conf file.
    2. Check *key.kdb file for SSL certificates.
    3. Check SSL certificates. Import missing certificates as required.
    4. Check plugin-cfg.xml file.
13 Applications 1. Navigate to commonly used applications (i.e. Work Order Tracking, Assets, Item Master, Inventory, Purchase Requests, Purchase Orders, Job Plans, etc.).
    2. Confirm the applications display all screens (tabs) and fields.
    3. Confirm the List Tab displays all rows and Filter and Sort works as expected.
    4. Confirm adding, updating and saving a record in each respective application.
* = Optional tasks

#Maximo
#bestpractices

Statistics
0 Favorited
20 Views
0 Files
0 Shares
0 Downloads

Comments

Mon November 24, 2025 04:07 PM

Thank you for the great feedback, Jess. 

Fyi, I had a nicely formatted table to present but it did not copy over nicely in this article. I'll try to make it look better. 

Mon November 24, 2025 11:06 AM

Thanks for the share! Lists like these are so valuable in ensuring repetitive steps aren't forgotten. Depending on the Maximo work being done, BIRT reports not displaying with the error "Request pages haven't been generated." is a response I've seen more than once. Having a procedure like the one you've created can save a lot of headaches.