Watson Supply Chain Ideas

Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with users and IBM experts on the B2B Collaboration Community

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

During uninstall/install do not remove/modify data, archive, maps, cmgr directories

when upgrading from one release to another (LINUX install), the uninstall/install processes should not touch the directories data, archive, maps, or cmgr as these contain business data, not installation software. It is necessary to backup and recreate these directories, which can add significant time to the install. The install can create directories as required if they do not exist, but never destroy data.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 19 2018
  • Planned for Future Release
How will this idea be used?

will save time during install.

What is your industry? Travel & Transportation
What is the idea priority? Medium
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Luke Raiano commented
    September 05, 2018 15:30

    IBM is planning to change the way we install on top of Linux (generally).  Rather than requiring an uninstall prior to installing the new version,  we plan to provide the relevant TAR files that can be dropped onto the customer's directory structure.  Also, best practice would be to ensure maps and other artifacts are deployed/stored separately from the runtime directory structure.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 05, 2018 18:02

    That should be much more effective. BTW, I eventually realized that we could change the permissions to 400 for the uninstall because it ignored the warning/error messages and then we changed back to normal permissions after the uninstall/install was complete. Your comment about best practice seems a little disingenuous since the install attempts to create these directories under the install directory. On the other hand, perhaps using something like /var/xxx/archive instead of the /opt/xxx/archive could be used effectively when the install directory is /opt/xxx. Maybe next time. Thanks for your answer.