Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

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,

  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 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Spectrum Symphony
Components Version 7.1
Created by Guest
Created on Mar 16, 2016

Dynamic SSM Resource Group History Files to SFS

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.

  • Guest
    May 27, 2021

    .Hi Andrew, I am closing this RFE as there is no current plan to further simplify how SFS is configured in application profile. Please feel free to create a new RFE if there are still gaps.
    Current the SFS path defined in application profile supports variables already (like SOAM_HOME, EGO_CONFDIR), so you do not really need to hardcode the path.

  • Guest
    Nov 24, 2020

    ..For future roadmap consideration, together with application profile consolidation by supporting flexible env variables in configuration.

  • Guest
    Mar 17, 2016

    Creating a new RFE based on Community RFE #85566 in product Platform Symphony.