This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.