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

App Connect

Showing 798

Publication using Broker UserID

Please provide the option to choose that messages are published under brokerID. This was the behaviour before upgrade to WMB 7.0.0.5 (see APAR IC81853: http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IC81853) Currently we run with MQS...
about 11 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...
about 11 years ago in App Connect 3 Not under consideration

AGENT.PROPERTIES FILE FOR BROKER FTE NODES

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 agent.properties file to overcome this. We would like to be able to do the sa...
over 11 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
over 11 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...
over 11 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.
over 11 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.
over 11 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.
over 11 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 ...
over 11 years ago in App Connect 3 Not under consideration

Allow a configurable Message Context property for a Publication Node

Allow a configurable Message Context property for a Publication Node in a similar fashion to that allowed for an MQ Output Node.
over 11 years ago in App Connect 2 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.