Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

Beware of a Straight Upgrade If You Are Moving Away From a Component

By Mark Robbins posted Mon July 09, 2018 12:00 AM

  

As organisations upgrade their systems they should take the opportunity to review the add-ons/solutions they have installed. In some cases components are retired because they are replaced by other components e.g. the Maximo Mobile being replaced by other solutions including Maximo Anywhere.

Maximo installations are sometimes upgraded in-place and that can lead to a problem if a component is being replaced.

The upgrade process normally doesn’t uninstall old components e.g. Maximo Mobile. This means that an installation can be left with incompatible Java classes/components

If your installation is being upgraded then ensure that your provider is handling this situation correctly and doesn’t leave you with a system that references incompatible components.

Incompatible components can cause a number of problems including:

  • JVM failing to start properly
  • Excessive/unnecessarily log messages caused by the incompatible components
  • Functionality broken or behaving unexpectedly
  • Your support from IBM may be restricted because of the references to the incompatible code

#AssetandFacilitiesManagement
#Maximo
2 comments
29 views

Permalink

https://community.ibm.com/community/user/blogs/mark-robbins/2018/07/09/beware-of-a-straight-upgrade-if-you-are-moving-awa

Comments

Mark Robbins
Thu July 12, 2018 01:41 PM

"You'd have to test the changes, so I imagine a separate test environment is required?"
My preferred solution is to use a virtual machine that you can rollback to a state before the components were installed.

If a VM isn't available then backing up the DB and all the components/servers is the next best thing.

"Do you build a separate generic environment with the new component installed?"
Realistically all the updated components would get installed and tested in a standard test process.

"Do you compare the differences?"
Comparing the differences is always a tricky issue because some differences are difficult to spot e.g. a change to a value that breaks an existing process.

I'll be blogging about testing and things to consider in the future. I have quite a few more topics before I get to that one. Feel free to contact with me on linkedin if you want to have a chat

"Uninstall components is fraught with its own issues never quite restoring you back to how things were before the component was installed."
Realistically uninstall isn't a safe option. I would much rather restore the servers/database back to their original configuration

SoCal Sun
Thu July 12, 2018 10:35 AM

You'd have to test the changes, so I imagine a separate test environment is required?

What are your thoughts on how to handle this situation? Do you build a separate generic environment with the new component installed? Do you compare the differences?

Uninstall components is fraught with its own issues never quite restoring you back to how things were before the component was installed.