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.
AES-256 encryption for .bin file creation
we understand that when a .bin file is created via lcu.jar it is encrypted with AES-128. We would like to see this encryption increased to AES-256 to satisfy our Security requirements.
Fix a bug which IBM support is not accepting as a bug
Problem: Any CD Windows v6 client or Requestor is impacted. When a lower case process name job is submitted, via the v6 client or requestor, the process name is automatically converted to uppercase and the job is submitted. While the same process ...
File agent high availability run GUI cdfa -C from a single Default_Config.ser copy in shared workspace
Instead of maintaining multiple local copies of Default_Config.ser, could a parm be added to cdfa -C to direct GUI to use a single copy in the shared directory. Similar to the cdfa -w parameter.
Status to be returned when performing an automatic silent install
When performing an automated silent install/upgrade from the Windows command prompt, instead of the command dropping straight back to the command prompt, certain messages would be returned and at the end of the install/upgrade a return code/status...
osa.rest.url Parameter needs to be able to handle multiple url's
Currently the osa.rest.url can only have one url. The Control Center Director may have multiple event processors. If the event processor (EP's) url that is referenced in the osa.rest.url parameter is down, then those events will not get to the oth...
Passwordless connection to built-in local PostgreSQL
This enhancement should allow to use alternate access options to local PostgreSQL other than locally encrypted password to PostgreSQL user. Proposed solutions include: certificate-based authentication (preferred, if technically feasable) password ...
Multi region access point support for s3 bucket
We would like to have multi region access point support for s3 bucket in connect direct transmission so that file transmission to AWS env can be done using multi region access point, this will help in case of DR scenario and the team sending the f...
Connect:Direct Client Identification by the Connect:Direct Server
Connect:Direct, although a peer to peer MFT tool, uses a client - server model as it's underlying architecture. With a client submitting a job to the C:D server, we cannot identify the client server with the current state of affairs if the C:D ser...
to add High Water Mark for max API session to be reported into the statistics
Add time zone to Connect Direct logs
Add time zone information to Connect Direct logs. Log file should present the datetime/timestamp in unambiguous fashion.
Do not place IBM confidential, company confidential, or personal information into any field.