Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Created by Guest
Created on Aug 25, 2020

Let the MDM Docker containers use environment settings from outside the image

The current Docker installable containers use static environment settings for for example database server, ldap server, kafka server, etc. This means we need to create an image for every environment increasing the possibility to have different code bases for the environments.

It would be better to externalize the environmental settings and pass then when the container starts. So the image can be made once and be used through the complete DTAP street. You then have the option to run multiple T environments (which now means yet an other image to be build).

Build 1 image and create multiple environment files. Creating an extra environment file most likely takes less time as creating a new image.

Needed by Date Oct 1, 2020
  • Guest
    Reply
    |
    Aug 28, 2020

    Hi Erik,

    We believe this type of customization can/should be performed by customers in their own environments (for example, by replacing values in configuration files with placeholders and then replacing placeholders in the startup scripts in the container, by reading values from ConfigMap and replacing configuration files with files from ConfigMap or other sources like volume.)

    Since this is related to install-able MDM container images which customers configure and the customization can vary from customers to customers, we have decided not to provide this out of the box.

    Hope this helps.

    Thank You

  • Guest
    Reply
    |
    Aug 27, 2020

    What we ment is not change the serversetting when the server is running, but at file level.

    For example for LDAP change the security.xml in the config\cells\<cell_name> directly before the server is started.

  • Guest
    Reply
    |
    Aug 26, 2020

    Hi Erik, please see below the initial feedback I received from our development team.

    • If setting these through WAS deployment script, it will take too long a time for a container to start up and it may not feasible. It will require deep WAS hack to deal with WAS configuration file directly to parameterize these deployment information. We probably don't know which configuration file contains information for database server, ldap server, kafka server, etc. This is not a typical WAS configuration process. Since this is a WAS standalone environment, dealing with configuration file directly should not be a big problem.

    • When scripts are used to change configuration, we will have to first start the server (x seconds), run the scripts and restart the server (2x seconds). So the startup time will increase, which is not good in a container orchestration platform.

    Let me know your thoughts. Thank you.

  • Guest
    Reply
    |
    Aug 25, 2020

    Hi Erik, thank you for submission. We will investigate and follow up here with status.