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.


Add a new idea Subscribe
Status Under review
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Aug 27, 2025

RELATED IDEAS

Cloud-native management of MQ-objects using MQ-operator on openshift

While it is possible to maintain mq objects via mqsc scripts as described in https://www.ibm.com/docs/en/ibm-mq/9.2.x?topic=manager-example-supplying-mqsc-ini-files - the mechanism is a bit weak and fiddly, because:

1) operator will only cycle the sts and run scripts if there are additions/removals of configmaps - not if the content changes
2) it is hard to remove objects this way - you need to put in delete statements or do it manually on the side outside of the operator contol
3) it depends on cycling the queue-manager pods - even if you run nativeha this will give a [small] interruption of service

a stronger and more cloud-native way of doing this would be to have a secondary resource which would control the management of channels and queues - just managing queues would be a good start - you then define queues (and their properties, like persistence etc) in a k8s api, and operator reflects this state. Upsides:

1) declarative and cloud-native, gives feedback of status in the resource
2) can be done online over MQSI or rest-api calls
3) easier to deal with deletes

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.