In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Thanks Diego. Good information and it looks like we have a lot of work in front of us. I'll inform the team of this tomorrow. This did send me off on a 'side search'. Does anyone have documentation of all that will be coming with the 9.1 version? Firm release date?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Hi @Richard Foster,
as for what's coming in the next release, I think IBM does a good job of keeping the What's New section of "feature channel" up to date:
What's new in the Maximo Application Suite feature channel for preview - IBM Documentation
(at the bottom, you will find links to the news for various applications, including Manage)

As far as I know, there is no official release date for 9.1, but I expect it to arrive before the summer.

Thanks Diego. Good information and it looks like we have a lot of work in front of us. I'll inform the team of this tomorrow. This did send me off on a 'side search'. Does anyone have documentation of all that will be coming with the 9.1 version? Firm release date?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Thanks again, Diego. I did see that link but nothing on 9.1. My understanding is that Tririga will now be avialable when that version is officially released. And I had heard around June 1 for the actual realease date. We are using the pre-release version which doesn't have a lot of new features as far as I can tell. 

------------------------------
Richard Foster

Original Message:
Sent: Sun March 30, 2025 11:30 AM
From: Diego Visentin
Subject: Transition to Java 17 from Maximo Application Suite 9.1 support announcement

Hi @Richard Foster,
as for what's coming in the next release, I think IBM does a good job of keeping the What's New section of "feature channel" up to date:
What's new in the Maximo Application Suite feature channel for preview - IBM Documentation
(at the bottom, you will find links to the news for various applications, including Manage)

As far as I know, there is no official release date for 9.1, but I expect it to arrive before the summer.

------------------------------
Diego Visentin

Original Message:
Sent: Thu March 27, 2025 06:01 PM
From: Richard Foster
Subject: Transition to Java 17 from Maximo Application Suite 9.1 support announcement

Thanks Diego. Good information and it looks like we have a lot of work in front of us. I'll inform the team of this tomorrow. This did send me off on a 'side search'. Does anyone have documentation of all that will be coming with the 9.1 version? Firm release date?

------------------------------
Richard Foster

Original Message:
Sent: Sun March 09, 2025 02:15 PM
From: Diego Visentin
Subject: Transition to Java 17 from Maximo Application Suite 9.1 support announcement

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

------------------------------
Diego Visentin
------------------------------

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Hi! Do you know, has Nashorn replaced by Graal for automation scripts?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Hi Andrey,
in March feature channel for preview it is used Nashorn at its very last release (Release release-15.6 · openjdk/nashorn · GitHub) 

PS:
I don't think using GraalJS was a viable option because in the latest versions, support for the JSR 223 scripting API has been removed in favor of the proprietary Context API, which Oracle says is better suited to support the polyglot nature of GraalVM.

Hi! Do you know, has Nashorn replaced by Graal for automation scripts?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Hi Diego,

I have a serious issue with getting BIRT 4.16 Designer to run reports. 

I have followed the instructions provided by IBM at this link: Downloading and installing BIRT Report Designer - IBM Documentation

I have downloaded JAVA 17, specifically jdk-17.0.16_windows-x64_bin.exe.

I can get BIRT 4.16 to come up, pointing to use the JAVA 17.

I can open an OOB MAS 9.1 report (login_history.rptdesign), but when I try to run it, I get nothing but these errors: see attached: birt416_mas91_errors.txt

And this image below is what shows up in BIRT 4.16:

If you have any information that could help me get past these errors, I would GREATLY appreciate it!

Our interim fix right now is to run the reports in BIRT 4.8, using JAVA 8 and MAS 9.1 libraries, which I know we shouldn't be with MAS 9.1, but we have no other choice since we cannot get these reports to run in BIRT 4.16 with the MAS 9.1 provided files and JAVA 17.

I hope there is a good solution to all this!

Thank you SO MUCH in advance,

Christie Smith

Hi Andrey,
in March feature channel for preview it is used Nashorn at its very last release (Release release-15.6 · openjdk/nashorn · GitHub) 

PS:
I don't think using GraalJS was a viable option because in the latest versions, support for the JSR 223 scripting API has been removed in favor of the proprietary Context API, which Oracle says is better suited to support the polyglot nature of GraalVM.

Hi! Do you know, has Nashorn replaced by Graal for automation scripts?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

Hi Christie,

Please update the Eclipse Preferences. It will resolve the issue

1. Open eclipse ->Preferences->Classpath and select the add external class folder.

Hi Diego,

I have a serious issue with getting BIRT 4.16 Designer to run reports. 

I have followed the instructions provided by IBM at this link: Downloading and installing BIRT Report Designer - IBM Documentation

I have downloaded JAVA 17, specifically jdk-17.0.16_windows-x64_bin.exe.

I can get BIRT 4.16 to come up, pointing to use the JAVA 17.

I can open an OOB MAS 9.1 report (login_history.rptdesign), but when I try to run it, I get nothing but these errors: see attached: birt416_mas91_errors.txt

And this image below is what shows up in BIRT 4.16:

If you have any information that could help me get past these errors, I would GREATLY appreciate it!

Our interim fix right now is to run the reports in BIRT 4.8, using JAVA 8 and MAS 9.1 libraries, which I know we shouldn't be with MAS 9.1, but we have no other choice since we cannot get these reports to run in BIRT 4.16 with the MAS 9.1 provided files and JAVA 17.

I hope there is a good solution to all this!

Thank you SO MUCH in advance,

Christie Smith

Hi Andrey,
in March feature channel for preview it is used Nashorn at its very last release (Release release-15.6 · openjdk/nashorn · GitHub) 

PS:
I don't think using GraalJS was a viable option because in the latest versions, support for the JSR 223 scripting API has been removed in favor of the proprietary Context API, which Oracle says is better suited to support the polyglot nature of GraalVM.

Hi! Do you know, has Nashorn replaced by Graal for automation scripts?

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1
  

@Diego Visentin Are there any instructions on how to apply the custom java references updates when applying a customization archive to MAS 9.1?  We want to be able to add the customization archive, that contains our java and other files, and apply the updates to the max tables (maxobject/maxobjectcfg/maxattribute/maxattributecfg) for the java references in the classname field.  Please let know something soon.

In a few months' time, version 9.1 of MAS will be available, bringing several updates to the Manage runtime and libraries, and moving the old Maximo EAM code up to date. In particular, it will use Java 17, which will have a number of implications, including an upgrade to BIRT v4.16 and the use of OpenJDK Nashorn libraries.
So get ready to recompile all your customizations in Java (more than the lack of compatibility mode, beware of module-based library isolation because it may cause some surprises), automation scripts and so on.
In this regard, IBM has published these technical notes:

• IBM Maximo Manage: Transition to Java 17 from Maximo Application Suite 9.1 support announcement
• IBM Maximo Manage: Guidelines for diagnostics and testing when migrating from Java 8 to Java 17 in Maximo Application Suite 9.1
• IBM Maximo Manage : Troubleshooting guide for Java 17 from Maximo Application Suite 9.1