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
Post 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 product management 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 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.
Dynamic SSM resource groups work well in Symphony 7 but for one issue. By definition a dynamic resource group does not contain management hosts but consists of regular compute hosts. These hosts do not know of the shared file system where session history files need to be written so the session history info can be viewed in the PMC and database. To make this work right now, the path to the shared file system needs to be hardcode in the application profiles. A much better way to do this is to pass down the high level path to the shared file system to the SSM from the SD so history files can be written relative to that using an environment variable or similar construct.
Do not place IBM confidential, company confidential, or personal information into any field.