Migrate Java customizations to Maximo automation scripts
MAS 9.1 moved to Java 17 — stricter rules, dropped legacy features
Custom MBO classes, deprecated API calls, and reflection-based UI extensions break
IBM recommends automation scripts (Jython/JavaScript) over Java where possible
Manual conversion is slow, error-prone, and expensive
Inventory all Java customizations — MBO classes, JSP files, bean overrides
Score each: convert to automation script, recompile for Java 17, or retire
Auto-create automation script templates with correct launch points
Test generated scripts against Maximo object structure
Push scripts to target environment via Sharptree-compatible deployment
Full Java Inventory
Complete customization inventory and dependency mapping
Auto Classification
Script-convertible vs Java-17-recompile vs retire
Launch Point Detection
Object events, Attribute validation, Action triggers
Script Generation
Template generation in Jython or JavaScript
Conflict Detection
Bean class overrides that cannot be scripted
Migration Report
Effort estimates per customization
Transparency builds trust. Here are the current limitations:
Bean class functionality with no script equivalent
Method suppression of inherited IBM logic
Framework hooks without launch points
