IBM Support

IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 17 to Java 25 in Maximo Application Suite 9.2

Troubleshooting


Problem

When migrating from Java 17 to Java 25, it is crucial to perform diagnostics and testing to ensure that customizations, BIRT reports, web services, XSLT data transformations, Jython scripts, and automation functions continue to work as expected. Failing to thoroughly test these components may lead to compatibility issues and operational disruptions.

Resolving The Problem

Essential and recommended testing for user environment

  • Customization review

    You should conduct a thorough review of any existing customizations to ensure compatibility with Java 25. This includes checking for deprecated or changed features that may impact custom functionality.

  • BIRT report testing

    With the BIRT version updated to 4.21, while no functional impact is anticipated, it is strongly recommended that you test your existing reports to confirm compatibility with the new version.

  • Web services testing

    Users must test their SOAP-based web services to ensure proper functionality and communication between systems, confirming that there are no disruptions.

Non-mandatory (but recommended) test cases

  • JMS queue testing

    Java Message Service (JMS) facilitates communication between Java-based applications and other software components. Testing the JMS queue ensures that message exchanges are functioning as expected.

  • Kafka messaging provider

    Users should test the integration of Apache Kafka, which is used for processing messages between Maximo Application Suite and external systems. Ensuring the correct message flow between systems is essential.

  • Reports re-testing

    It is advisable to retest various reports with different supported file types and formats. This includes testing options like printing with attachments, printing without attachments, and duplex printing to ensure all report features work as expected.

  • XSLT data transformation

    Verify the Maximo integration framework (MIF) transaction with XSLT for inbound messages. Additionally, test XSLT transactions that involve integrations with external systems or data storage solutions such as S3 buckets.

By focusing on these mandatory and recommended test cases, you can ensure that the environment remains stable and that integrations, automations, and customizations continue to function smoothly with Java 25 and the updated platform components.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLPL8","label":"IBM Maximo Manage"},"ARM Category":[{"code":"a8m50000000CbOcAAK","label":"General-\u003EMaximo Base"},{"code":"a8m50000000CbPBAA0","label":"Industry Solutions"},{"code":"a8m3p000000F82dAAC","label":"Maximo Application Suite-\u003EMAS Applications-\u003EManage-\u003EAdd-ons"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"and future releases"}]

Document Information

Modified date:
29 April 2026

UID

ibm17270577

Page Feedback