Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Aug 8, 2022

Allow MQGet/MQPut nodes to be looped in for a given set of QueueManagers/queues at runtime

Any one who wants to consume/put messages from and too by iterating thru different queue managers/queues config set at runtime.

Idea priority Medium
  • Admin
    Ben Thompson
    Sep 14, 2022

    Idea / RFE Review. Thank you for taking the time to raise this suggestion, and also for the interaction which has taken place through the service case which was raised on the same topic. Unfortunately on this occasion we do not intend to take this suggestion further forward. The main reason for this is a concern over the way in which you are viewing the dynamic addition of new queue managers in your network. If the intended use case here could accurately be described as "a new Queue Manager has been brought into operation and now I want ACE to read from it", then we would expect either a new flow to be deployed with an MQInput node configured appropriately to take messages from the new queue manager, or an existing flow could be extended with a policy that links to the new queue manager / or new branch of flow logic that deals with the new message feed. This kind of design reflects the fact that MQ is not really designed to have applications connect to it based on a file being updated with connection details ... some research on MQ trigger monitors may be helpful here as an alternative design. This commentary is based around the queue manager aspect of the use case .. where queues on an existing queue manager are concerned, you can use existing flow facilities for iterating over different queues using the MQGet node in combination with settings in the LocalEnvironment to specify the queue name dynamically. A final point worthy of note is that if you are adamant that you need queue manager dynamic connections (not using MQ options such as trigger monitor or uniform clustering, which would also be worth some research) then this could be achieved with bespoke java logic in a JavaCompute node, but as previously mentioned we would not encourage this workaround as we really feel a more basic appraisal of the interactions with MQ would be better.