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.
[RFE][MS] - Improve LIM communication to handle MTU size
Symphony (i.e. EGO) relies on OS MTU configuration. When LIM exceeds the OS MTU limitation, LIM/ELIM data is not transported. Provide a mechanism to allow LIM communication to transport the data when the LIM data exceeds the MTU size.
[Security] - Active Directory Single Sign-On for ego & soam utilities
We use SOAM utilities such as soamdeploy and soamreg in PowerShell scripts to upload new Symphony applications to our clusters. When we tried uploading applications on our test cluster with the Active Directory security model installed, the two ut...
[Security][CE] - Hybrid Symphony / Active Directory integration security model
The Symphony Active Directory integration plugin removes all Symphony users with the exception of Admin, so that only AD users are available. This means that it is extremely difficult to migrate an existing cluster from the default Symphony securi...
We are currently running PROD in Sym5.1. Win 2012 support is essential to utilize newer capacity with higher memory sizes. Though Sym6.1.1 has Win2012 support we cannot afford a quick migration in PROD. Do inform us at the earliest of when this su...
Symphony 7.1 stops supporting .Net version earlier than 4.0. However per Microsoft documents .Net 3.5 will not be end of life in any time soon. Providing support of .Net 3.5 in symphony 7 and future version will help .Net applications on earlier ...
Tomcat version 6.0.43 bundled in Symphony 7.0 needs update to 6.0.44 to comply with bank compliance/audit. - Wells Fargo
Our Symphony 7.1 install incudes the Tomcat version 6.0.43 installed and running. Internal bank audit/controls requires us to upgrade any Tomcat versiosn to 6.0.44 or file an exception as to why we cannot get into compliance. Please let me know wh...
Symphony 6.1.1 with LSF 9.1.1 multihead setup support for SLES 11sp3
Big Financial server customer requires SLES 11 sp3 support for Symphony 6.1.1. The customer plans to start a Symphony/LSF multihead POC soon using 6.1.1 on SLES 11sp2 but will be soon upgrading their systems to SLES 11 sp3.
Do not place IBM confidential, company confidential, or personal information into any field.