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 Not under consideration
Created by Guest
Created on Jul 28, 2021

MQ MFT Agent Queue Manager Affinity

Currently, an MQ MFT client/agent is forced to register with one and only one queue manager. This prevents offering a continuously available file transfer service to customers as planned or unplanned downtime of a queue manager would incur an outage.

Idea priority High
  • Admin
    Mark Taylor
    Reply
    |
    Sep 7, 2021

    As MFT stores state information on a queue, availability patterns for transfers (both configuration and in-flight state) rely on the associated queue manager - which can of course be made highly available with a number of approaches including multi-instance or RDQM. A redesign of that queue-based model is not something we would expect to implement. Therefore this Idea is being declined.