Application and add-ons upgrade prerequisites

Before you upgrade, you must consider whether the IBM® Maximo® Application Suite applications and add-ons are available for upgrade. If the applications or add-ons are no longer available, you must deactivate and delete those applications and add-ons.

Upgrading to 9.1

If you are upgrading to Maximo Application Suite 9.1, review the following prerequisites:
Stand-alone Maximo Health no longer a suite application
Maximo Health is no longer available as a stand-alone suite application but remains an add-on in Maximo Manage.
If Maximo Health is deployed as a stand-alone suite application and you are upgrading to 9.1, you must add Maximo Health as an add-on in Maximo Manage 9.0. Then, you upgrade to 9.1. For more information, see Upgrading Health stand-alone 9.0 to Manage with Health 9.1
IBM Maximo Assist renamed IBM Maximo Collaborate
Starting in Maximo Application Suite 9.1, IBM Maximo Assist is now named IBM Maximo Collaborate. If Maximo Assist is deployed in Maximo Application Suite 9.0 or earlier and you upgrade to Maximo Application Suite 9.1, the name is automatically changed in the user interface.
Note: In the Maximo Application Suite documentation, Maximo Assist is now referred to as Maximo Collaborate.

Upgrading to 9.0

If you are upgrading to Maximo Application Suite 9.0, review the following prerequisites:
MRO Inventory Optimization

Starting in Maximo Application Suite 9.0, MRO Inventory Optimization is no longer available to be added as an externally configured application. If MRO Inventory Optimization is configured as an external launcher and you are upgrading to Maximo Application Suite 9.0, you must remove MRO Inventory Optimization before you can complete the upgrade.

To remove MRO Inventory Optimization as an external launcher, you delete the solution portal URL for MRO Inventory Optimization on the External launcher page. When the product URL is removed, users can no longer access from the suite navigator. For more information, see Configuring external launchers.

Support for MongoDB 5.0 and 6.0
MongoDB 5.0 and 6.0 are supported in Maximo Application Suite.
If you are upgrading from an earlier version of MongoDB to MongoDB 5.0 or 6.0, consider the following requirements:
  • Before you upgrade MongoDB, create a backup.
  • If you are using a cloud-hosted instance of MongoDB, such as on IBM Cloud®, refer to the documentation for that cloud host for more information about how to support and upgrade MongoDB.
  • If MongoDB is hosted in another way, such as on premises, refer to the upgrade documentation for MongoDB for that host.
  • If you are using the MongoDB community operator with automation that is provided by Maximo Application Suite, refer to the Maximo Application Suite Ansible® documentation.

Upgrading to 8.11

If you are upgrading to Maximo Application Suite 8.11, review the following prerequisites:

IBM Parts Identifier
Starting in 8.11, the IBM Parts Identifier add-on is no longer available. If Parts Identifier is installed, and you are upgrading to 8.11, you must deactivate and delete Parts Identifier before you can complete the upgrade.
IBM Maximo Health and Predict - Utilities
Starting in 8.11, the Maximo Health and Predict - Utilities add-on is no longer available. If Maximo Health and Predict - Utilities is installed, and you are upgrading to 8.11, you must deactivate and delete Maximo Health and Predict - Utilities before you can complete the upgrade.
If you want to use your existing health models or data loader of Maximo Health and Predict - Utilities, in the Integrations and dependencies section, configure the Watson Studio project ID and the dashboard URL for App Connect that was used for Maximo Health and Predict - Utilities. For more information, see Deploying Maximo Health.
Note: The Maximo Models for Electrical Distribution accelerator replaces Maximo Health and Predict - Utilities in Maximo Application Suite 8.11.

Upgrading to 8.10

If you are upgrading to Maximo Application Suite 8.10, review the following prerequisites:
  • The installation method that you use determines how Maximo Application Suite is upgraded. If you install the Maximo Application Suite manually by downloading and running an installer script, you upgrade the Maximo Application Suite the same way. Depending on your chosen approval strategy, the upgrade begins automatically or after you approve it.

Upgrading to 8.9

If you are upgrading to Maximo Application Suite 8.9, review the following prerequisites:
Service Binding Operator
Uninstall Service Binding Operator (SBO) because it is not a dependency from Maximo Application Suite 8.9. Therefore, before uninstalling SBO from the cluster, ensure your Maximo Application Suite instances (core and all applications) are upgraded to the latest Maximo Application Suite available fixes.

To uninstall, in Red Hat® OpenShift® operators, go to Operators > Installed operators, and search for Service Binding Operator 1.0.1 and click Uninstall Operator.

Cloud Pak for Data
Optionally upgrade to IBM Cloud Pak® for Data 4.5.x. For more information, see Installing IBM Cloud Pak for Data.
Red Hat OpenShift
Optionally upgrade your Red Hat OpenShift cluster to 4.10. For more information, see Updating clusters, worker nodes, and cluster components.
Maximo Safety
In Maximo Application Suite 8.9, Maximo Safety is not longer available. If Maximo Safety is deployed and active in your environment and you are upgrading to Maximo Application Suite 8.9, you must deactivate and delete Maximo Safety before you can complete the upgrade.
IBM Maximo Optimizer
If Maximo Optimizer is deployed in your environment and you are upgrading to Maximo Application Suite 8.9, Maximo Optimizer must be version 8.2.2, or higher before you can complete the upgrade.
Maximo Health and Predict - Utilities

If Maximo Health and Predict - Utilities is installed, optionally upgrade the IBM App Connect dashboard. For more information, see Updating Maximo Health and Predict - Utilities.

Upgrading to 8.8

If you are upgrading to Maximo Application Suite 8.8, review the following prerequisites:
Maximo Scheduler Optimization
If Maximo Scheduler Optimization is deployed in your environment and you are upgrading to Maximo Application Suite 8.8, you must uninstall Maximo Scheduler Optimization before you can complete the upgrade. For more information, see Upgrading from Maximo Scheduler Optimization to Maximo Optimizer.