Skip to Main Content

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

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 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 for resolution. For more information about IBM's Ideas program visit



All ideas

Showing 1908 of 1908

.NET access to global cache

MS/.NET customers would like .NET access to the embedded global cache.
almost 9 years ago in App Connect 3 Not under consideration

Publication using Broker UserID

Please provide the option to choose that messages are published under brokerID. This was the behaviour before upgrade to WMB (see APAR IC81853: Currently we run with MQS...
almost 9 years ago in App Connect 3 Future consideration

Should give an error for an undefined variable used in the code while compilation time only

While writing code in ESQL if a developer uses a variable in the code which is not defined then it only gives a warning and even creates the bar file. Rather it should give a error during compilation of the code itself and should not allow the dev...
almost 9 years ago in App Connect 3 Not under consideration


When using an FTE output node in a workflow we are creating more than the 1000 queued transfers that is the set default. In a stand-alone agent we can make changes to an file to overcome this. We would like to be able to do the sa...
almost 9 years ago in App Connect 3 Not under consideration

Clustering the DBInput Node

The DBInput Node does not function in a multi clustered MQ/Broker environment. This limits failover and redudency and negates clustering
almost 9 years ago in App Connect 21 Future consideration

Event monitoring generate alswas transaction.rollback with Excp in case of an error.

In some cases, for instance with the MQInput node, there is no transaction.rollback event emitted when the flow fails. When there is a validation error detected in the MQInput node (validate content and value with parse timing complete) there is a...
almost 9 years ago in App Connect 2 Future consideration

Provide validation for duplicated label names on Label nodes in WMB Toolki

If we have duplicated label names in label nodes the bar file is built without error. The validation is only performed during deployment time what delays development process.
almost 9 years ago in App Connect 2 Future consideration

Execute Web UI Data Viewer filters at user login

Update the Web UI to provide the ability for a user to create Data Viewer filter statements which can be stored and automatically applied when that user signs in.
about 9 years ago in App Connect 86 Future consideration

View the message or ExceptionList in the Web UI Data Viewer

Update the Web User Interface (UI) so a message and/or ExceptionList may be viewed in the Web UI Data Viewer instead of having to download them and view with Notepad, rfhutil, etc.
about 9 years ago in App Connect 86 Future consideration

Cognos BA Node

This node will be an output node which will take input from previous node of the message flow and transform messages into .csv, .cod, .xls, .JPG etc formats needed by Cognos Inside and finally generate the report in Cognos report format as output ...
about 9 years ago in App Connect 3 Not under consideration