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.2

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

IBM Db2® version 12 licensing requirements: Upgrading from Db2 11 to 12 requires explicit opt-in activation and a valid IBM Db2 Warehouse license file. Without a valid license, Db2 12 operates under a 30-day trial license that causes production system outages after expiration.; Before upgrading Db2 from 11 to 12, you must obtain a valid Db2 Warehouse license file from IBM and set the db2_v12_upgrade flag to true. The upgrade fails if the license file is not provided, preventing silent downgrade to a trial license. For more information, see Upgrading Db2 from version 11 to 12 by using the CLI and Upgrading Db2 from version 11 to 12 by using Ansible.; Important: New Db2 12 installations do not require a license file. Only upgrades from 11 to 12 enforce this requirement.

Administrative permission modes: Starting in Maximo Application Suite 9.2, you can choose from three administrative permission modes during installation - cluster mode, namespaced mode, and minimal mode.
The administrative permission mode cannot be modified during the upgrade process. When you upgrade from Maximo Application Suite 9.1 to 9.2 by using mas upgrade command in the CLI, the administrative permission is automatically set to cluster mode because the cluster mode is used in 9.1 and this configuration is inherited during the upgrade.
For more information, see Requirements to install in an existing Red Hat OpenShift cluster.

User authentication: Before you upgrade to Maximo Application Suite 9.2, review the upgrade process for user authentication change. For more information, see Upgrading user authentication changes from Maximo Application Suite 9.1 to 9.2.

User management APIs

The following APIs for user management are removed in 9.2.

User creation APIs: The endpoints that are responsible for registering new users.
Workspace assignment APIs: The endpoints that are used to link users to specific workspaces.
Role assignment APIs: The endpoints that are used to assign fixed roles, such as user and administrator, within applications.

If your integrations or scripts use the deprecated APIs, update them to use the new APIs before you upgrade to 9.2. For more information, see Managing users with APIs in Maximo Application Suite 9.1 and later.

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:

Maximo Inventory Optimization

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

To remove Maximo Inventory Optimization as an external launcher, you delete the solution portal URL for Maximo 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.

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.

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.