Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Future consideration
Created by Guest
Created on Jan 13, 2023

Add 'prefix' to Kafka provider properties

When sharing the same Kafka cluster between multiple environments, it is necessary to provide different (unique) topic names for each environment to ensure they are not consuming another environment's data. This is somewhat problematic for the use of migration manager as the environment-specific configuration is then present on external systems and cron task instances.

Ideally a 'prefix' property on the Kafka message provider would be transparently appended to the configured topic names so the environment-specific configuration is in a single location, and the functional configuration of topic names does not need to be modified in each environment.

For example, if we share a Kafka cluster between Dev and Test environments for the 'SYSTEM1' system, we may configure a 'dev_system1' and a 'test_system1' topic which is then specified on the external system and cron task instances.

A preferable implementation would be for the Kafka provider on Dev to have a prefix of 'dev_' defined, and similarly the provider on Test to have a 'test_' prefix defined, and the external system and cron task instance to only reference 'system1' as the topic name.

Idea priority Medium
Needed By Not sure -- Just thought it was cool