Integration


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 (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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on May 7, 2026

RELATED IDEAS

Extended support for the schema registry

The new Kafka Producer node in ACE 13 is good, but it requires a specific ID from the Schema Registry, which varies by environment and makes it very difficult to deploy to higher environments.

Key points (from my PMR):

  • ACE 13 does not resolve schemas by subject name

  • ACE 13 does not apply Kafka topic naming strategies

  • ACE 13 requires a numeric schema ID to be provided

  • Subject names like <topic>-value cannot be used in place of a schema ID

My second problem is related to the Schema Registry policy, which can't take default values for TLS connections from the integration server/node. Kafka Policy can do this without a problem, so why can't it work the same way?


Third problem - i can set only one URL in Schema Registry policy which is very limiting if you don't have any load balancer before. I do think that multiple urls separated with comma is standard also for Schema Registry.

Idea priority Urgent
  • Admin
    Varun Jain
    Aug 21, 2026

    Thank you for raising this. Your request covers three related areas: a more user-friendly way to specify the schema ID, the ability to override TLS parameters for the schema registry (analogous to the variable-based override already available for the Kafka broker policy), and support for multiple load-balancer URLs for the schema registry in the same way as the bootstrap server property. All three are reasonable enhancements and we are accepting them collectively as a future consideration.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.