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,
Post an idea
Upvote ideas that matter most to you
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 email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
WASPreUpgrade + WASPostUpgrade take days to run when processing large files
WASPreUpgrade and WASPostUpgrade allows a migration between two WAS versions, e.g. 8.0 to 9.0 or 8.5 to 9.0. The WASPreUpgrade process effectively exports the data from the original profile. The WASPostUpgrade effectively imports the data from the profile. In some situations, the WASPostUpgrade task will modify some of the data imported. In other situations, it makes no modifications to the data.
If a profile contains a large file, both WASPreUpgrade and WASPostUpgrade processes will continue to run, however, they may take days to complete successfully. The WASPostUpgrade process in particular appears to be the slower of the two processes. This can be reproduced by leaving large files - e.g. a core dump, trace files, sizable .ear applications - etc. in a profile during the WASPostUpgrade process.
A local fix for this issue is documented in an IBM APAR that was closed "SUG", or suggestion, not implemented in the code:
Remove any large files that should not be present in the
WebSphere file system
Further commentary - this is not an issue related to the underlying hardware speed. Adding more disk IOPS will not help here, this is purely an issue with the code in use. Manually copying the large file on the filesystem outside of the WASPostUpgrade code takes one minute at most, versus days within the WASPostUpgrade code.
Why is it useful?
Saves system administrators a significant amount of time when migrating to a new system.
Do not place IBM confidential, company confidential, or personal information into any field.