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 Oct 23, 2014

Dynamically update the binding location and connection factory in ESQL to support N numbers of JMS QM

I am looking to dynamically update the binding location and connection factory in ESQL so we can support N numbers of JMS QM.

The problem with multiple JMS nodes within a flow is we are bound to the number of JMS nodes defined in the flow. For example if we created a flow with 5 JMS nodes and at later time our system requires
additional JMS QMs, as a result we need to update the flow with additional JMS nodes and rebuild the bar and deploy it. However, if we can dynamically update the binding location and connection
factory in ESQL therefore we can continue using existing runtime object.

Idea priority Medium
RFE ID 61009
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Aug 2, 2021

    Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. As noted, it is currently not possible to use settings in the LocalEnvironment to override the connection factory name which is hardcoded on the message flow node properties. Whilst it is possible to abstract the connection factory to a JMSProvider policy, unfortunately these policies are not currently redeployable without a server restart ... It sounds like the main motivation here is to support multiple connections all at once in any case. This still sounds a valid future requirement and whilst we have not yet managed to prioritize a business case for this feature, we will maintain its status as Future Consideration for now.

  • 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
    Jun 3, 2015

    Thanks for raising. Status of this RFE is updated to Uncommitted Candidate.