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 Sep 14, 2023

Apply security patches to MQ while the software is running and/or libraries are in-use

We have an internal policy which requires security vulnerabilities to be patched within 7-90 days (depending on the severity of the vulnerability). If we were able to rollout patches to MQ without the need to cycle Queue Managers or applications, this would allow us to stay on top of patching and minimize outages to applications and clients in turn. 

Idea priority High
  • Admin
    Mark Taylor
    Sep 27, 2023

    While an interesting suggestion, the amount of shared state between processes that might be using shared libraries would make this very difficult to implement reliably. As a result we are declining this Idea.

    Using containers that are built in a pipeline can simplify applying fixes as the new levels can be made ready to run before stopping the currently-executing environments.