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 Sep 2, 2021

Enabling the MQ Appliance Floating IP to assume (resolve) a secondary address after the execution of 'makedrsecondary' command.

In the event of Disaster Recovery, application are unable to put messages to the queue manager at the recovery site using the floating IP. The HA floating IP is only shared by the main data center's HA pair, and upon recovery the static IP of the recovery appliance will need to be used to connect to the queue manager.


To avoid having to modify applications running in the recovery site, enable the HA floating IP to assumed (resolve) to the static IP of the recovery site immediately after executing the 'makedrsecondary' command.

Idea priority Urgent
  • Admin
    Mark Taylor
    Reply
    |
    Oct 5, 2021

    A floating IP address can only be shared between appliances that share the same subnet. A primary site and a recovery site would not usually share a subnet to help ensure the two sites remain independent. Therefore this feature is not practical to implement.


    If an application needs to connect to either site then a network load balancer or a DNS entry can be used to route applications to either the floating IP address at the main site or the IP address of the appliance at the recovery site. Alternatively, the application can use a CCDT or a connection name list to try connecting to each location in turn.