Do not delete saved files in IBM Installation Manager

I barely remember having read about an issue with deleting saved files in IBM Installation Manager and it recently bit me – I stupidly disregarded the warning, although I had known it might hurt. Once burnt, twice shy – isn’t it how the saying goes?

For IBM WebSphere BPM product family, including IBM WebSphere Integration Developer (WID), it’s IBM Installation Manager (IM) that helps managing your product installations. After I upgraded WID to the latest version 7.0.0.4, I thought about some cleaning and decided to press the “infamous” button Delete saved files (in Files for Rollback menu in Preferences). I wish I had not done it – I’d have almost lost a day if I’d not had a copy of the virtual image (!) [*].

With the files for rollback deleted, WID showed very few components in the assembly diagram – untyped component, import, export and references and no other drawers in the palette. Without the components it’s nearly impossible to design an integration module in WID (well, you can always revert to modifying raw XML files, but the point of using an IDE or WID in particular is to avoid doing it in the first place, isn’t it?)

The first thought was to downgrade WID to the previous versions 7.0.0.302 or earlier.

I imagined that having downgraded the product, the missing jars would’ve likely been downloaded if they’re needed. With the downgrade to 7.0.0.302 I ended up with the following error message in IM.

Problem during session finalization.
   Validation of Eclipse installation configuration failed because it references features or bundles in its "platform.xml" file that do not exist.
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.common_7.0.300.200906011400.jar"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.query.parser_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.query.parser_7.0.200.200906011400.jar"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.cei.ui_7.0.300.v20100825_1011"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.common_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.core_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.customactivities.dma.runtime_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.migration.feature_7.0.301.v20101103_1147"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.customactivities.dma.runtime_7.0.200.200906011400.jar"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.cei.ui_7.0.300.v20100825_1011.jar"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.runtime.core_7.0.200.v20100422_1028"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.runtime.core_7.0.200.v20100422_1028.jar"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.core_7.0.300.200906011400.jar"

The lowest version of the missing jars was 7.0.200, and with no such version on the list, there was no other way as to downgrade to the version 7.0.0.0. It didn’t work well, either.

Problem during session finalization.
   Validation of Eclipse installation configuration failed because it references features or bundles in its "platform.xml" file that do not exist.
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.query.parser_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.cei.ui_7.0.300.v20100825_1011"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.common_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.core_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.customactivities.dma.runtime_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.migration.feature_7.0.301.v20101103_1147"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.runtime.core_7.0.200.v20100422_1028"

The list of the missing jars was shorter, but the problem was still there – WID was unusable. The last attempt to fix it was to upgrade the product back to the version 7.0.0.4. I too got no joy from doing it as IM reported the following error.

Problem during session finalization.
   Validation of Eclipse installation configuration failed because it references features or bundles in its "platform.xml" file that do not exist.
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.query.parser_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.cei.ui_7.0.300.v20100825_1011"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.common_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpc.core_7.0.300.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.bpe.customactivities.dma.runtime_7.0.200.200906011400"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.migration.feature_7.0.301.v20101103_1147"
      Bundle not found: "C:\IBM\SDPShared\plugins\com.ibm.wbit.runtime.core_7.0.200.v20100422_1028"

This time, however, I had no luck of running WID at all. After an hour of trying to fix it, I gave up and restored the image from a backup.

“What’s the lesson?”, you ask? It reminds me the saying “Premature optimization is the root of all evil”. I had no reasons to delete these files, and since they were not an issue, why did I even bother myself with them? I’ll keep that in my mind now – the lesson learnt.

I still wonder whether or not I should disable the option “Save files for rollback”. It defaults to keep the files from previous versions of a product, but since the feature didn’t work for me, these files are hardly useful, aren’t they?

p.s. I’m unable to find the IBM technote to not use the feature of IM because of possible troubles (or was it about something else?)

[*] I’d appreciate if you could check the sentence from English grammar’s point of view.

Be Sociable, Share!
This entry was posted in WebSphere.

One Response to Do not delete saved files in IBM Installation Manager

  1. IM seems to be so loudly applauded product that nobody cares so far to look down at such “useful” features that could be removed with no harm to overall functionality. As for me, IM does not pay back with it’s features for its clumsiness, triple installation time and disk consumption.

Leave a Reply

%d bloggers like this: