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 Delivered
Workspace App Connect
Created by Guest
Created on Apr 8, 2019

Add envvars as properties in conf.yaml files

In IIB 10 some fixes had to be activated using envvars, for instance for the mapping

As more properties were added recently to the ACE 11 conf.yaml files, this seems also a good location to replace those envvars.


Idea priority Medium
RFE ID 131840
RFE Product IBM App Connect (formerly Cast Iron)
  • Admin
    Ben Thompson
    Sep 19, 2022

    RFE Review. Setting environment variables and having them take effect at server start time can be a complex activity to get right. Environment variables can in general be set in the server.conf.yaml file (note the stanza named "EnvironmentVariables" in the sample server.conf.yaml file) but this won't have any effect for environment variables which are read in at C++ static initialization time. A few of the historic MQSI* variables are like this (for example MQSI_MRM_CONSUME_TRAILING_BYTE), but the majority of variables are checked from java such as the mapper variables, and so placing them in the server.conf.yaml file will cause them to be set before JVM startup and therefore they will take effect. Ideally in the long term we would like to see the transfer of all MQSI* style variables into standard entries in the server.conf.yaml file, or documentation of them as supported env vars ... this is an activity we'll continue to address over time, but given the base capability is there for the vars in question we are closing this suggestion as delivered.

  • Guest
    Nov 5, 2020

    RFE Review. Thank you for taking the time to raise this RFE and apologies it has been in submitted status for so long. We agree that this fits with the concept of the declarative style server.conf.yaml and the idea would enhance the product; and we have even prototyped a similar capability. Status of the RFE is updated to Uncommitted Candidate.