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.


Status Future consideration
Workspace App Connect
Created by Guest
Created on May 11, 2022

Possibility to choose a MQ Policy for Timeout nodes & Co

Currently, it is only possible to use the default remote Queue Manager. https://www.ibm.com/docs/en/app-connect/12.0?topic=nodes-timeoutcontrol-node


I would like to be able to choose my MQ Policy at the design time or during the deploy, as MQ Nodes

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    May 11, 2022

    RFE Review. Thank you for taking the time to submit this idea for enhancement. As highlighted, it is possible to direct the Timeout nodes to use a remote queue manager through changing the default remote queue manager setting in the server.conf.yaml file. A new setting in the Timeout policy itself, or via a pointer from a Timeout policy to an MQEndpoint policy, would enable this configuration to be become more dynamic (changeable through policy redeploy rather than through server restart). Status of the suggestion is updated to Future Consideration.