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
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,
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 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 a 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.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to email@example.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Add function to MQ to listen to ENF71 signal from TAMZ product(Broadcom)
We are using TAMZ product to elevate our ID's to gain higher access during a production issue or during the normal QMGR build process. The process of elevation is as below1.Elevate our normal TSO ID to the EPV group ID which has access to DEFINE/A...
enhancement to logs in AMU to add details of OAuth related product and subscription
During an API Connect v5 to v10 migration using the AMU tool, the archive-push info.log details OAuth products and subscriptions that were not created/pushed on v10 because they were containing OAuth only APIs and subscribing to products containin...
DataPower SFTP Poller - Adhoc Schedule instead of Polling Interval
As of now, SFTP Pollers are having the Polling Interval alone, We need to have Specific date and time and Calendar for Polling Schedule. There are some SFTP Pollers required to be configured to transfer a file once a day, so we don't want datapowe...
IBM MQ is preventing WebSphere Application Server (WAS) to be started in reusables ASIDs
In our business operation, we need to take down the WAS servers to make the user application unavailable at night. These stops (and later restarts) of the WAS servers are consuming the ASIDs in the systems they run and demanding frequent IPLs. We ...
We have MFT for MQ running on-prem system and planning to migrate to CP4I. Since MFT is currently not being supported in CP4I environment, we are not able to proceed with the migration. It will be helpful, if the MFT is supported in CP4I environment
Update the MQ PowerShell library SupportPac MO74 for MQ V9
The PowerShell libraries make it very easy for administrators to script and execute automated actions, like:Removing all queues from a QM, except the SYSTEM* queuesBatch configure queue depths, channel properties, etcOther operations on a range of...
Monitoring of the APIDeveloper portal compliance against security baseline configuration
APIDeveloper portal has multiple security configuration items which needs to be correctly set and maintained. On top once there is new portal many configuration items can be changed by portal administrator which can cause potential security risk i...
Currently there is no solution proposed for the security monitoring of the API Developer portal and API Manager portal. IBM customers are looking for the designs explaining how to build the security monitoring (which log sources, how to get them, ...
Missing documentation for security events in the IBM DataPower log and APIConnect.
Current DataPower log documentation is not including good categorization, sequence nor details explaining which log categories and event codes are including potential security issues. Documentation mainly includes plain event code and name without...
Do not place IBM confidential, company confidential, or personal information into any field.