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 Sep 13, 2013


When using an FTE output node in a workflow we are creating more than the 1000 queued transfers that is the set default. In a stand-alone agent we can make changes to an file to overcome this. We would like to be able to do the same for the FTE nodes that are available in the broker. With acquisitions, we will be hitting this threshold more often.

Idea priority High
RFE ID 39188
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Mar 18, 2022

    The FTE file which is used by the IIB/ACE message flow nodes is generated internally but can in theory be editted by the user such that the runtime would then take account of those changes. This process has not been documented as an external of the product, nor thoroughly tested, although we have shared information about the file location as part of wider discussions with specific customers through the support process. It is unlikely that this enhancement request to formally document a new external and test non-default agent properties will be prioritized but in the interests of helping users make these changes themselves, we are sharing the file location here (for example on Linux servers) which is as follows:


  • Guest
    Sep 23, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. The reason we have never externalised the ability for users to make their own personal changes to the FTE Agent properties file is that there are some circumstances where the file can be recreated by the IIB/ACE deploy chain. That said, it would certainly be technically feasible to formally externalise the file (which on Windows for example you will find in the workpath beneath C:\ProgramData\IBM\MQSI\components\\servers\\config\WMQFTE). Since raised back in 2013, there has only been a single vote in support of this RFE, so unfortunately it is unlikely to be prioritized soon, however we acknowledge that this enhancement suggestion would improve the product. The status of the RFE is updated to Uncommitted Candidate.

  • 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