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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 30, 2021

BrokerProxy - getRegistryPropertyNames does not give back mqKeyRepository

We want to have a dashboard showing all properties set on the broker and We don't understand why this function does not give back all properties available, especially as the mq key repository is not different from keystore or truststore

Idea priority High
Who would benefit from this idea? All the customers who want to have a dashboard of all broker properties
  • Admin
    Ben Thompson
    Dec 13, 2021

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request. The ACE admin API (described by our Open API v3 document which is available on the URL route /apidocs from any started integration node or server) gives dynamic access to a wide variety of the most commonly used integration node properties. However, as noted, in ACEv11 and ACEv12, the code is very specific in this area and only picks out certain properties for return across the admin REST API and unfortunately mqKeyRepository is one of those not currently exposed. As you may have noticed, some properties, such as those associated with the "BrokerRegistry" component of the integration node, of which mqKeyRepository is one example, currently require an integration node restart to become effective. Properties of this sort can still be editted using the mqsichangeproperties command, which you will then see evidence of the change in the override node.conf.yaml file, but the node must be restarted for them to become effective. Similarly, a locally executed mqsireportproperties command can report on the BrokerRegistry directly... but when considering remote access, one thing we would need to consider is whether absolute paths to security aspects may not be suitable for exposure over remote connections. We are updating the status of the idea to Future Consideration and invite comments from the community about whether this property should be considered suitable for remote reporting.