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 1434

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...
almost 12 years ago in App Connect 3 Future consideration

Allow SOAP Nodes to follow HTTP Redirect

HTTP Request nodes have the option to follow redirects. Please implement this same functionality for SOAP Request nodes.
almost 12 years ago in App Connect 4 Future consideration

Message Reallocation Enhancement

When messages are not able to be delivered through cluster channels to a destination which is unreachable MQ will attempt message reallocation to redirect the messages. We understand from PMR 16826 082 000 that 3 gets and 1 put will occur for each...
almost 12 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration

Increased granularity for MQ Event Message Delivery

I am looking for IBM to enhance the granularity of delivery options for MQ generated Event messages. While newer Event Message types such as Configuration Events get their own queue (SYSTEM.ADMIN.CONFIG.EVENT), legacy events share common queues. A...
almost 12 years ago in MQ, MQ Advanced & MQ Appliance 5 Future consideration

Optimized database connection management

Currently WMB ODBC connections are limited in the sense that all database transactions by default are contained within the scope of the message flow transaction boundary. ESQL Compute nodes have a 'Transaction' property which can be set to Automat...
almost 12 years ago in App Connect 3 Future consideration

Create AMQERR01.LOG message or generate event at circular error log switch on WMQ distributed

Create a message in AMQERR01.LOG or generate an event when the circular error log 'flips' to the next file (via rename): AMQERR01->AMQERR02 , AMQERR02->AMQERR03, AMQERR03->AMQERR01
almost 12 years ago in MQ, MQ Advanced & MQ Appliance 7 Future consideration

Trace Default Root

The Trace Node is the best way to debug multiple flows, but if you have lots of Trace Nodes, deploying to a new server means a lot of tedious effort to set the file path. Make it configurable so the Trace Root can be set once for an entire app.
almost 12 years ago in App Connect 2 Future consideration

Add Feature in ESQL comupte node to make the changes in the code during debug & test them instantly as in Java Compute Node

There is a very good feature in Java Compute node that you can make changes in the code in the debug time and test then at the same time.But such feature is missing in ESQL compute node. I would suggest to enable same feature in ESQL compute node ...
almost 12 years ago in App Connect 2 Future consideration

Add Odata suppoort to message broker. (OData node for example)

We need the broker to provide full Odata implemetation, which could be done by the addition of an OData node. Right now we only have the capability to offer OData protocol through RESTfull interaction using HTTP nodes. To have full OData service w...
almost 12 years ago in App Connect 3 Future 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 12 years ago in App Connect 21 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.