Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


ADD A NEW IDEA

My ideas

Showing 1337

When a Source FTE agent crashes Destination Threads for In Progress transfers hang on the Destination FTE agent

The ability for Destination FTE agents to cope with outages to Source FTE agents that have crashed, and not have In Progress transfers from the crashed Source Agent holding on to the Destination transfers threads on Destination FTE agent.
almost 12 years ago in MQ, MQ Advanced & MQ Appliance 6 Future consideration

Update Broker System Trace to include value of ODBCINI and the real error behind issues reading odbc.ini

In troubleshooting a problem connecting to MS SQL Server we performed a system trace. The trace provided the following error information: DatabaseException BIP2347E: Database error: SQL State ''IM002''; Native Error Code ''0''; Error Text 'System ...
almost 12 years ago in App Connect 3 Future consideration

XQuery support requested within WebSphere Message broker

We currently have a lot of integration code written using XQuery. We would like to implement WMB as our Integration Engine. How can we retain all our investment in XQuery ? Ideally - provide an "XQuery node" within WMB. Alternatively, provide some...
almost 12 years ago in App Connect 4 Future consideration

Allow additional data, scripts, etc. to be included in Library/Application projects but not included in the BAR file.

The current build of a BAR file (WMB 8) includes all files contained in Application and Library projects into the BAR file. We would like the ability to specify, whether or not to include non-broker artifacts held in a Library or Application in th...
almost 12 years ago in App Connect 4 Future consideration

Support multifactor authentication in SFTP

The fileoutput node is unable to connect to remote SFTP systems that use both a key AND password. The mqsisetdbparms will only allow one to be set.
almost 12 years ago in App Connect 2 Future consideration

EmailOutput node: To Cc Bcc should be configurable properties

We use EmailOutput node to deliver alerts from message flows. The mail IDs are different in development, test and production regions. Because the To, Cc and Bcc address fields of this node aren't configurable, we have to rely on work-arounds.
almost 12 years ago in App Connect 1 Future consideration

Enhanced toString for MbElement

The MbElement toString function does not print out the list of children or siblings. During debugging sessions, custom code needs to be written to review the node tree.
almost 12 years ago in App Connect 4 Future consideration

Deploying the individual message flows developed as part of the Application

Deploying an Individual Message flow which is part of an Application
almost 12 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.
almost 12 years ago in App Connect 3 Future consideration

Extend the WMB Node API to allow the creation of Monitoring Events

Creating new message flows during the instantiation of a pattern is a very nice feature. However, right now it is not possible to add monitoring events to a node using the WMB Node API.There are already dummy methods defined (addMonitorEvent, getM...
about 12 years ago in App Connect 3 Future consideration