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.
EGO command 'egosh' should support both -json and -o "column1 column2 ..." like other commands
The current egosh command output is formatted in a way that does not make for easy parsing by customers. It would be nice if it follows the LSF convention of providing both a -json output format, and an columnar output format using -o "column1:xx ...
Since we are having problems while PLC is not being able to write all the tasks executed in Symphony to Oracle database, we would like to have a plc connector to send all the information to a Kafka queue (or similar). Our goal is to be able to use...
[Workload Monitoring and Management] SOAM - Package - Remove obsolete/inconsistent SI packages from compute node (Epic32879)
Even if customer removed consumer, SI package corresponding to the consumer would be still remained on compute node. Symphony should be able to remove obsolete SI package from all compute nodes.There is an idea to remove obsolete packages.- Set fl...
[Installation and Upgrade] Install - New Installation type: Management Console and Management Client
Currently, there are the following three installation types only.- Management Node- Compute Node- Client- Symphony DE But it's better to have new installation type "Management Console" or "Management Client".It contains ego/soam commands, but it d...
Service Package Version Reset and/or Forsibly Deploy
If Symphony shared directory was restored by some reasons (ex. Disaster Recovery, Hardware Renewal, Hardware broken, etc.), RS couldn't deply newer SI package until the version number was incremented to the version number deployed on compute node....
[Support Matrix] Matrix - Oracle Standard Edition support for Symphony 6.1.1
We changed the Oracle support policy from v6.1.1 and it make customer hard now.Symphony v6.1.1 support only Oracle Enterprise edition.It is barrier for customer to upgrade Symphony now. Old version Symphony (v184.108.40.206, v5.x) supported Oracle and it...
[CE] Platform Symphony Management GUI - Solaris Sparc - BBK
We use a Symphony Version 5.0 in a pure Solaris 10 Sparc 64 bit Infrastructure including the Platform Management Console GUI. All used servers are based on Solaris Sparc architectureThe Symphony Grid infrastructure is implemented in two regions --...
[Cluster Management] Add OS dependency for service packages
For platform independent applications (eg. Java based) it would be great to have OS option on service package dependency setup.Without that option Java based application service packages have to be either repackaged (replace deployment.xml having ...
Do not place IBM confidential, company confidential, or personal information into any field.