Upgrade checklist

You can use the upgrade checklist to check for tasks that you must do for upgrading from Maximo® Asset Management to Maximo Manage.

Before you upgrade

  • Ensure that you have Maximo Asset Management 7.6.0.10, 7.6.1.2, or 7.6.1.3 installed. For more information, see Installing Maximo Asset Management.
  • Plan for Maximo Application Suite installation requirements and preferences. For more information, see Planning.
  • Install and configure Red Hat® OpenShift® cluster for non-production and production environments, according to your requirements. For more information, see Installing Red Hat OpenShift Container Platform.
    Note: To know more about installing on Amazon Web Services, IBM Cloud® , Microsoft Azure, or using a command-line interface, see Supported installation paths.
  • Become familiar with authentication, encryption and security, and SMTP configuration methods. For more information, see Authentication and security and SMTP configuration.
  • Plan your upgrade schedule. For more information, see Planning your upgrade schedule.
  • Review current database settings. For more information, see Database settings.
  • If you are using Oracle Connector or SAP Connector, prepare it in Maximo Asset Management before you upgrade. For more information, see Preparing Oracle and SAP Connector before upgrade.
  • Check for industry solutions and add-ons compatibility. For more information, see Deployment of industry solutions and add-ons.
  • Disable custom triggers in any table of your database. For more information, see Custom triggers.
  • Commit any database configuration changes that are pending. For more information, see Configuring the database.
  • Backup your production database. For more information, see Backups.
  • Prepare a test database as a duplicate of the Maximo Asset Management production database. For more information, see Backups.
  • Complete any post-installation tasks for Maximo Asset Management before you upgrade. For more information, see Post installation tasks.
  • Create a customization archive to store specific changes, such as Java™ classes, XML files, and database scripts. For more information, see Migrating customizations using customization archive.
    • Create deployment descriptors, as needed. A deployment descriptor describes how a component, application, or module is to be deployed with specific security settings, container options, and configuration requirements. For more information, see Deployment descriptors.
  • Run Integrity checker in Maximo Asset Management 7.6.1.0, 7.6.1.2, or 7.6.1.3 and fix all errors reported. For more information, see Running Integrity checker.
  • Test the upgrade in testing environment. For more information, see Testing the upgrade
  • Use Maximo Manage logs to check and fix any errors you may run into while upgrading. For more information, see Troubleshooting the upgrade using Maximo Manage logs.
    Tip: Keep your testing environment with application servers started, so that you can better measure the actual downtime it will take considering the production environment.
  • Stop the application server only when you are nearing completion of Maximo Manage deployment as part of Maximo Application Suite.

During upgrade