Skip to Main Content
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.


Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 12, 2013

Per PMR WMB 8.0 ".Broker file" currently does not support multi-instance

Per, PMR 41175,442,000, in version WMB 8.0.0.2, the .broker files used to attach and administer brokers from WMB Explorer, and WMB Toolkit. IBM Support asked me to open RFE. See their email below.

----- UPDATE -----
As mentioned earlier we do not have any provision to include dual Broker
connection information in <.broker> file. Please note that it is
designed to take only one Broker connection information and
changes to make it handle multiple Brokers would need to follow a
separate process called RFE. We would like you to be informed that the
support system can comment only on something already available in
the product. As the current scenario deals with a functionality
to be extended it needs to be handled through RFE process to design and
decide on the structure/syntax. Any such new feature request puts you
in direct communication with Broker development.

Request you to submit the RFE from URL https://wwwprdw.ibm.com/developerworks/rfe/
so that it can be considered for the coming releases of the product.
---- /UPDATE -----
Please let us know if you have further questions or comments regarding this PMR.
We look forward to hearing from you soon.

Kind regards,
WMB L2 Support

Idea priority Medium
RFE ID 41536
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Sep 13, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. Whilst we view this as quite a minority use case, and one which is easily worked around, we acknowledge that enhancing the product in this way would make it more user-friendly for those who are utilising highly available pairs. Noting the solid (9) number of votes, yet also that there has not been recent evidence of popularity, it is unlikely that this request will be prioritised in the short term, but we will continue to monitor it. Status of the RFE is updated to Uncommitted Candidate.

  • Guest
    Reply
    |
    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
    Reply
    |
    Dec 5, 2013

    It might be more than two hosts running the MI QM and broker.

    Referencing a CCDT file might be a better way to implement this RFE.