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 1369

Allow message expiry to be set on event monitor messages

When adding a new monitoring event to a Broker node it would be useful to have the option of setting an expiry value (and possibly other MQMD values too) for the published event message.
about 10 years ago in App Connect 3 Future consideration

Dynamically update the binding location and connection factory in ESQL to support N numbers of JMS QM

I am looking to dynamically update the binding location and connection factory in ESQL so we can support N numbers of JMS QM. The problem with multiple JMS nodes within a flow is we are bound to the number of JMS nodes defined in the flow. For exa...
about 10 years ago in App Connect 3 Future consideration

Add Monitoring to HL7DFDLInput and HL7DFDLOutput nodes

The healthcare pack provides an HL7DFDLInput and HL7DFDLOutput nodes without a monitoring tab -- forcing crude work arounds, Ideally, they would be equipped with the same Transaction Start, Transaction Stop and Transaction Rollback that MQ nodes h...
over 10 years ago in App Connect 3 Future consideration

Add retry mechanism for EMAIL node

We continue to see intermittent network connectivity issue between the broker and SMTP Relay servers at our site. In order to mitigate the issue we have implemented the broker code to retry when there is a connectivity issue. But it would be nice ...
over 10 years ago in App Connect 3 Future consideration

Enable filtering of unmapped elements in Graphical Data Mapping node

Enable filtering of unmapped elements in the Grapical Data Mapping editor.
over 10 years ago in App Connect 3 Future consideration

The ability to quiesce connections to the TCPIP server node

The ability to quiesce connections to the TCPIP server node. Specifically, a command or procedure to instruct the TCP/IP connection manger to reject the establishment of new client connections, while still allowing already established connections ...
over 10 years ago in App Connect 2 Future consideration

Add XML Policy support to IIB's mapper

In the base GDM with XSLT as a target, "XML Policy" is available. Please make this "XML Policy" available in IIB's GDM.
over 10 years ago in App Connect 3 Future consideration

FileRead NODE and FileOutput NODE (Performance Enhancement)

Please enhance the File Read node to permit: - Sequential File reads on a record-oriented file - Improvement in performance of reading sequential records - Built-in node function to permit configurable buffering and read-ahead, to avoid the need t...
over 10 years ago in App Connect 2 Future consideration

Show all DFDL errors in ExcpList / logs

When a DFDL parsing fails only the fatal error is in the ExcpList or logs. Due to the nature of DFDL the root cause can be earlier in the message but will be hidden from the logs
almost 11 years ago in App Connect 3 Future consideration

Support stored procs in DatabaseInput node's autogenerator

Enhance the DatabaseInput node's autogenerator to support stored procedures.
almost 11 years ago in App Connect 3 Future consideration