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 Jan 22, 2026

Externalizing initparm.cfg configuration Using ConfigMaps and Secrets

In IBM Connect:Direct containerized deployments running on OpenShift, the initparm.cfg file is generated exclusively during the installation phase and is not designed for dynamic updates. As a result, configuring or modifying integrations with cloud object storage services such as Amazon S3 and Azure Storage currently requires direct access to the running pod and manual file changes.

This proposal introduces the use of ConfigMaps and Secrets to manage updates to initparm.cfg and the associated credentials files, eliminating the need to access the pod directly or to modify the persistent volume using sidecar containers.

To minimize the risk of syntax errors or misconfiguration in the primary initparm.cfg, also suggests introducing a dedicated import file variable (for example, an IMPORTFILE or equivalent parameter). Instead of modifying the base initparm.cfg, which is generated at installation time and should remain immutable, Connect:Direct would load additional parameters from an external import file. (fileexit_import_file:/../fileimport.cfg