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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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,
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 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 notifications 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.
SSH User Identity Key > 2,048 bit
Partner ask to generate a auth key of 4,096-bit or larger, however Sterling menu doesn't allow for any key size except 1,024, 1,536 or 2,048. Also, there does not appear to be a documented and supported method to generate a key pair using a comman...
The source map name and compiled map name should be same as that of name of Map detail, only then the map deployment should be allowed
The source map name and compiled map name should be same as that of name of Map detail, only then the map deployment should be allowed.
Add possibility to use separate client TLS certificate for each Global Mailbox server when connecting to Cassandra and Zookeeper
Due to security compliance reasons please add possibility to use separate client TLS certificate for each Global Mailbox server when connecting to Cassandra and Zookeeper
Additional REST services
In our project, we have augmented the Sterling REST services with some other capabilities which we wrote as JAX-RS/Jersey REST services, hosted in a WAR in an HTTP Adapter. It would be good if you would consider in the roadmap providing the functi...
SFTP Error Reporting
With SI v6.0 and above the error reporting to SFTP has changed, with earlier versions we used to get clear failure messages like 'Known host keys mismatch', etc, whereas now we get more of a generic message like 'SSH_DISCONNECT_BY_APPLICATION:SFTP...
Native support for Azure Blob Storage acess
For supportability it would be great to see native support added for Azure Blob Storage along with the current plan to support S3
Upgrade Cassandra to 4.0 for Global Mailbox in order to support auditlogs
that would be useful for auditing purposes. PCI-DSS requirements require to audit systems access. All customers working in financial industry would benefit from this.
File replay on surviving data center using metadata from cassandra if the processing data center goes down
Currently , if the file is uploaded to the datacenter (DC) and that DC goes down, there is no way to replay that file until the DC comes up. This causes adverse impact on customer's business. Having this will help the production support to replay ...
Show more detail, on progress bar, when using IIM to upgrade B2Bi
Upgrading B2Bi v6.0 to v6.1 took almost two hours. For the majority of that time, IIM's progress bar sat at (about) 60%. It would be helpful to see what it's doing or even update the progress bar more frequently.
On the Code (List) Info form, put Text1 thru Text9 on their own lines and make the data fields much wider
Please put Text1 thru Text9 on their own lines and make the data entry field as wide, or wider, than the size of the Description data entry field.
Do not place IBM confidential, company confidential, or personal information into any field.