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
Created by Guest
Created on Dec 12, 2022

Enhance MQ LDAP failover handling: if multiple servers in CONNAME and one Server is down, whole Queue Manager should failover to Server#22

We use LDAP for user authentication (AUTHINFO TYPE(IDPWLDAP)).

We have configured three LDAP Servers to cover failover (CONNAME(ldap1,ldap2,ldap3)).

We learned, that MQ failover from ldap1 to ldap2 works per authentication request.

So each single authentication request will first go to ldap1, wait for the timeout, and only failover to ldap2 after the timeout.


Please enhance MQ LDAP failover handling. If multiple servers are given in CONNAME, and if one Server is down, the whole Queue Manager should failover to Server#2.

Solution idea #1 (optimal for our setup): Round Robin and Watchdog

There should be ALWAYS a "Round Robin" between all the LDAP Servers ldap1, ldap2, ldap3.

There should be a watchdog in the background, to regularly (every second) check all LDAP servers. If one goes down, this should be taken out from the Round Robin.

As soon as the server is back, it should be taken into the Round Robin again.

Corresponding messages should be written to the logfile if a server is taken out of the Round Robin, and once it is added to the Round Robin again.

Solution idea #2 (simple, but should be "good enough"): MQ Failover

This solution might be easier to implement.

Use ldap1 for all auth. requests.

IF ldap1 goes down

The whole QM should use ldap2 for all auth. requests until restart of the QM or manual event (e.g. refresh security).

Corresponding message should be written to the logfile.

Idea priority High
  • Guest
    Jul 9, 2024
    We recognise that this is a valid requirement. However it doesn't fit with our prioritised delivery plans for the next couple of years. As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.