3 posts tagged “Customization Archive”

MAS 9.1 moved the JVM under every Maximo customization from Java 11 to Java 17. MAS 9.2 (June 2026) adds Java 25 at the platform and AI-Service level while Java 17 stays the baseline for Manage and your custom code. Here is what changes for existing extensions, why 9.2 is a mixed Java-17/Java-25 environment, how to test and remediate, and why the extension model endured while everything around it modernized.

How Maximo add-ons are activated in the MAS Manage component model, and how custom Java is now delivered as a Customization Archive baked into a container image on OpenShift instead of dropped into WebSphere — the old-world/MAS-world post for developers and upgrade teams.

A developer's deep dive into how IBM Maximo add-ons and industry solutions extend the core through Java — PLUS prefixes, MBO inheritance chains, product.xml, bytecode injection, the compatibility matrix, the MAS 9 Customization Archive, and the Java 17 shift.