Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Submitted
Created by Guest
Created on Oct 21, 2026

Increase the maximum Integrated File Agent Default_Config.json size beyond 2 MB to support large-scale rule configurations

We would like to request an enhancement to IBM Sterling Connect for Windows to increase the maximum supported size of the Integrated File Agent configuration file (Default_Config.json) beyond the current 2 MB limit.

Current Situation:

Our environment currently operates two Connect installations on the same Windows server:

  • Connect 6.3.0.6: Default_Config.json approximately 858 KB.

  • Connect 6.4.0.3: Default_Config.json approximately 933 KB.

These installations were maintained separately due to historical limitations in the size of the File Agent configuration file.

IBM Support confirmed that the maximum supported configuration file size was increased to 2 MB starting with Connect for Windows 6.4.0.0.

Although this improvement is beneficial, our number of File Agent rules continues to grow, and the current limit may become insufficient in the future.

Requested Enhancement:

We request IBM to consider:

  1. Increasing the maximum supported configuration file size to at least 10 MB, preferably with a configurable limit.

  2. Supporting a significantly larger number of File Agent rules within a single configuration.

  3. Improving configuration loading, validation, and rule management performance for large configuration files.

  4. Providing clear warnings when the configuration approaches its supported size limit.

  5. Considering a scalable configuration storage mechanism that avoids fixed file-size limitations.

Expected Benefits:

This enhancement would allow organizations with large-scale file transfer environments to consolidate File Agent rules into fewer Connect installations, simplify maintenance, reduce operational complexity, and support future business growth.

We would appreciate IBM Product Management evaluating this enhancement for inclusion in the Connect product roadmap.

What is your industry? Banking
How will this idea be used?

As an administrator of IBM Sterling Connect in a large-scale banking environment, I need to manage an increasing number of Integrated File Agent rules within a single Connect installation.

Currently, multiple Connect installations are maintained to distribute File Agent configurations and avoid configuration file size limitations.

With this enhancement, administrators would be able to consolidate existing rules into a single installation, continue creating new rules as business requirements grow, and manage file transfer automation without being constrained by the current 2 MB configuration file limit.

This would simplify administration, upgrades, monitoring, and maintenance while improving the scalability of our managed file transfer infrastructure.