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
- Install and configure Maximo Application Suite. For more information, see Installing Maximo Application Suite.
- Configure SMTP in Maximo Application Suite before you create the admin user. Otherwise, the email with the generated password cannot be sent. For more information, see SMTP server.
- Create and log on as the admin user in Maximo Application Suite. For more information, see Administering users and user access.
- Prepare Maximo Manage for deployment. For more information, see Preparing to upgrade.
- Deploy Maximo Manage. For more information, see Deploying in Maximo Application Suite.
- Set server bundle properties in Maximo Application Suite. For more information,
see Adding server bundle properties.
- Set
mxe.oslc.webappurl
to point to the route address for each server bundle, by using bundle level properties.
- Set
- Activate Maximo Manage. For more information see Activating Maximo Manage.
- Check Maximo Manage deployment status. For more information, see Checking Maximo Manage deployment status.
- Update system settings like mxe.doclink.path01 and others with the new path. For more information, see Updating system settings path.
- If the database requires an SSL connection, you must obtain the certificate for the database. For more information, see Obtaining SS certificate for database.
- Import additional certificates as needed in Maximo Application Suite. For more information, see Importing additional certificates in Maximo Application Suite.
- Enable monitoring in Red Hat OpenShift cluster. For more information, see Installing Logging.
- Check Maximo Manage logs for any errors and fix them. For more information, see Troubleshooting using Maximo Manage logs.
- Check for user synchronization from Maximo Application Suite to Maximo Manage. For more information, see Managing users post upgrade.
- Configure Oracle Connector if you are using it. For more information, see Configuring Oracle Connector after upgrade.
- Configure SAP Connector, if you are using it. For more information, see Configuring SAP Connector after upgrade.
-
Tip: The following points are optional as per your specific requirements.
- Maintain attached documents for your applications in persistent storage or cloud object storage, that is, S3. For more information, see Configuring attached documents.
- Use the External Systems application in Maximo Manage to initiate export and import of data, for example, integrate data by using files. For more information, see Exporting and importing file-based data.
- Use XSL maps to transform messages for outbound transactions in the integration framework provided with Maximo Manage. For more information, see XSL mapping.