Maximo

Maximo

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

 View Only

  • 1.  Uninstall ICD from MAM+ICD combination

    Posted Wed January 18, 2023 04:37 AM

    Hi,

    does anyone knows how to uninstall/remove ICD from a combination of MAM + ICD 7.6.1.3?

    With Installation Manager & Configtool (Config-/UpdateDB) the ICD data model, meta data and ICD data are not removed from the database to leave only a MAM without ICD parts.

    My try was just to install a new SMP only with MAM, but what about the existing db scheme? It references ICD classes and other dependencies.

    Maybe someone has (an idea for) a migration approach?

    I already tried to export configurations from MAM+ICD via migration packages, but there's an issue with dependencies too (e.g. unknown attributes or classes).

    Background is, that customers does not use ICD functionality anymore (and does not want to pay for it) and likes to migrate to Maximo Application Suite.



    ------------------------------
    Sven Jahnke
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: Uninstall ICD from MAM+ICD combination

    Posted Thu January 19, 2023 08:24 AM
    We've done it.  ICD creates a lot of interdependencies and links throughout MAM as you've found.  It's a painstaking process to go through and find/remove them all, but it has been done.  We have several clients going through or facing that process now, which is resulting in a lot of lessons learned.


    ------------------------------
    Amy Tatum
    Starboard Consulting
    Longwood FL
    14073923177
    ------------------------------

    Original Message


  • 3.  RE: Uninstall ICD from MAM+ICD combination

    Posted Thu January 19, 2023 03:52 PM
    My personal suggestion is to reimplement if you really want to drop Control Desk. It's difficult to know if something you're using is Control Desk specific because there is no prefix for any of the apps, objects, attributes, etc. like the other industry solutions which makes it significantly harder to remove. You can do some analysis by running a clean maxinst in an environment with Control Desk & Maximo and a clean maxinst without it to find new objects, attributes, apps, etc. But Control Desk extends the UI of the core applications (SR, WOTRACK, ASSET, etc.) so you'll have to review all the references (bean classes, attributes, objects, etc.) inside the applications, all the dialogs in the library XML, the menus, etc. 

    We plan to support Control Desk in the Maximo Application Suite so that may be an option for them if they're looking to move to MAS and don't want to spend the time or money to go through the effort of removing it.

    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 4.  RE: Uninstall ICD from MAM+ICD combination

    Posted Thu January 19, 2023 03:58 PM
    By reviewing the DBC install scripts you can figure out what was added and then work out how to back it out.  I have done that for HSE and it wasn't actually too bad.  All the objects, messages, classes etc are all in whose scripts so you just need to read through and develop the reverse statements.  It's tedious but thorough and relatively simple.  




    Original Message


  • 5.  RE: Uninstall ICD from MAM+ICD combination

    Posted Fri January 20, 2023 10:30 AM
    A pain point of Maximo customers is that add-ons and industry solutions can't be uninstalled. I know of companies that have gone through splits and one of the resulting companies is stuck paying for a license to an industry solution they don't use because there's no way to take it out.

    That said, given the the task to take it out anyway, this would be my rough plan for getting started -- with the agreed caveat that perfection is in no way guaranteed.

    1. Install a fresh environment.
    2. Fish out all the `classname="com.ibm.or.etc.ClassName"` references from everywhere in the old database. This would have to keep track of where the reference came from so you know where to go back and make changes.
    3. Run the fished out names through a tool that checks for their existence in the various locations, at least including under .../businessobjects/classes and .../maximouiweb/.../classes.
    4. Any classes not found in step 3, find the location in the new database and put what you find there back in place of the reference in the old. If the location doesn't exist in the new, then you need to delete it from the old.
    After that, it might just be a matter of brute force and testing. 

    Certainly not a project for the faint of heart. And you have to ask, Is the cost to take it out worth it?

    ------------------------------
    Blessings,
    Jason Uppenborn
    Sr. Technical Maximo Consultant
    Cohesive
    ------------------------------

    Original Message


Related Content