Skip to Main Content
Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Created by Guest
Created on Dec 17, 2021

Enable Options to store old config backups out of WAS installation Directory during restoreConfig.bat

IBM team in Case TS006197127, has requested below

To remove old backup configurations as we noticed the issues with that in the past. However we still see you keep old config backups under the profile please remove them from that folder and store them elsewhere outside the WAS installation directory (config.old, config.old_1, config.old_2). It's known that keeping backups from config folders under the profiles can cause several unpredictable problems and even prevent the application server to start.

Those config backups are automatically created by restoreConfig.bat not backupConfig.bat, We are specifying a backup location outside of WAS Installation directory and we are restoring it from the backup directory mentioned during the execution of backupConfig.bat. There is no parameters we could use to avoid config renaming while the restoring of WAS Profiles using restoreConfig.bat.

Hence, default behavior has to be changed so that users can specify location outside of WAS installation directory.

Idea priority High