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
Created by Guest
Created on May 10, 2015
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-16 MQIPT single route for Multi-Instance qmgrs.

Multiple QMs in connection name for MQ IPT Merged

Currently, MQ IPT will only allow one QM connection endpoint in the connection name definition used to configure a route to a queue manager. In Multi-Instance QM environments, the ability is needed to attempt connection against a number of QMs in sequence until the currently active QM is found.

The MQ IPT manual recommends several approaches to address this need, but we believe this scenario would be simplified by having the IPT handle this internally.

Idea priority High
RFE ID 70934
RFE URL
RFE Duplicate of 37081
RFE Product IBM MQ
  • Guest
    Reply
    |
    Jul 26, 2016

    Close as dup of RFE 37081

  • Guest
    Reply
    |
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Reply
    |
    Sep 20, 2015

    Not quite sure why this is required. The client needs 2 addresses configured anyway in order to drive the correct failover/recovery behaviour. So configuring 1 port in MQIPT for each of the 2 (or more) possible queue manager addresses seems to make sense.

    For QM to QM channels, the same solution is possible, although implementing the alternative addresses in MQIPT would make configuration simpler.

  • Guest
    Reply
    |
    Jul 4, 2015

    Another vote. Also, dupe of #37081?