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
Workspace App Connect
Created by Guest
Created on Jan 28, 2015

IIB Plug-in

The IIB plug-in for MQ Explorer requires each Broker profile individually (this is a real pain) which creates an additional file (broker_name).broker. These files also cannot be imported to MQ v7.5 so we need the same conversion capability for the IIB plug-in. While we are on the subject ... why not just combine WMB import/export MQ Explorer settings capability into the MQ 7.5 Export/Import MQ Explorer Settings selection panel so you can save everything at once in one file in one place?

Idea priority High
RFE ID 65059
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Oct 4, 2021

    Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. The IIB / ACE product has evolved significantly since the time this suggestion was initially created. The Message Broker Explorer component no longer exists as part of the product and in its place we now have a web browser based ui dashboard which is capable of connecting to multiple integration nodes and independent integration servers. This dashboard has the ability to encrypt connection information and also an export capability when wanting to share connections between different users. On the off chance that you feel further specific enhancements are still required in this area please feel free to raise a request against the latest release of the product, focussing on this new UI.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Feb 13, 2015

    Thank you for raising this requirement. We acknowledge that behaviour could be improved in this area. The existing behaviour highlighted by the RFE is an MQ Explorer feature "Export MQ Explorer Settings", where as the Broker connection format is known by the IIB IBX plugins (as opposed to a feature of the MQ Explorer itself). The independence of the two products (MQ and IIB) and the fact that MQ Explorer is used by many clients who do not have IIB, is the reason for the different file format and apparent "duplication" of the feature, yet implemented in slightly different ways. Despite this justification of history, the essence of the requirement is obvious - for users with large numbers of brokers, an extension of the *.broker format to support the storage of multiple sets of connection details would undoubtedly be a good thing for the product. It is likely that this would need to be implemented in a new file type - the existing *.broker format is relevant for a single broker/node and is used and interpreted by some of the Broker command console commands, so we'd likely maintain this format in its current form for backwards compatability. So, once again, thank you very much for taking the time to raise the requirement which would provide enhanced usability. Status of this RFE is updated to Uncommitted candidate.