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 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
  • 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.