Integration

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 ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

ADD A NEW IDEA

FILTER BY CATEGORY

All ideas

Showing 1648 of 1648

Deploying the individual message flows developed as part of the Application

Deploying an Individual Message flow which is part of an Application
about 9 years ago in App Connect 3 Future consideration

Cloned message flow application across execution group

message flows that leverage aggregate control/request/reply nodes in WMB 7.x and beyond cannot scale across EGs within the same broker unless changes are made to the aggregate reply node to differentiate reply node "name" per EG.
about 9 years ago in App Connect 3 Future consideration

XPath 2.0 support in JCN

I would like the MbXPath class to support XPath 2.0.
about 9 years ago in App Connect 5 Future consideration

MQTT Device Daemon for ARM V7 and later

It is necessary to support more current versions of the ARM platform (V6,V7) and Linux kernels (V3) - most embedded systems currently in development or test are based on Cortex or Nvidia chip sets
about 9 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration

WMQ Support for MSCS Majority Node Cluster

Please see below which is a previous response to a RFE – we are basically following up this original query and trying to determine if/when support will be available for WMQ using MSCS Majority Node cluster. When queried last time we were told it w...
about 9 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration

A requirement for larger messages to be supported in a future release of WMQ FTE.

The customer was unable to create large messages on z/OS queue using File to Queue .The state message is held on the SYSTEM.FTE.STATE. queue. This limits the maximum output message size that can be written to around 33MB as you observe. There ...
about 9 years ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

File Read Node Optimized for sequential reads

Would like to see the file read node improved so that sequential reads are optimized. Current the file read node restarts each time the data is read making this impractical and poorly performing for sequential reads of significantly sized files (...
about 9 years ago in App Connect 3 Future consideration

Allow TCP Output nodes to use Local Environment overrides to set a configurable service to use.

The current TCP Output nodes only allow 'hostname' and 'port' to be overriden in the Local Environment. It does not allow you to specify a Configurable Service (TCPIPClient / TCPIPServer). This restriction effectively means that you cannot dynamic...
about 9 years ago in App Connect 3 Future consideration

Cannot implementat SOAP input authenticate with more than one group in WMB profile or SOAP configuration.

Only one group can be defined for each security profile for the purposes of creating a authentication profile through WMB. In configuring a security for a SOAP input nude only one profile name may be used. Because of the mapping of principals to g...
about 9 years ago in App Connect 4 Future consideration

No reason returned when an attempt to commit a transaction in async put mode fails

When an WebSphere MQ classes for JMS application uses the WebSphere MQ asynchronous put functionality to send a message to a queue inside a transaction, and a failure occurs when putting the message (because the queue is full, for example), the at...
about 9 years ago in MQ, MQ Advanced & MQ Appliance 3 Future consideration