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 Submitted
Categories Event Streams
Created by Guest
Created on May 22, 2024

V2 MQ Source Connector Support for XML to JSON converter from Apach Kafka

We have multiple use cases where a legacy system produces a XML mmessage fformat that is not fit for consumption downstream.  

Idea priority Urgent
  • Guest
    May 23, 2024

    We have multiple use cases that would need to ingest an XML message from a legacy MQ queue on prem which is needs to be converted to a more Kafka-friendly message format like JSON before it can be transformed into a downstream data warehouse or consumer application.

    The message producer for majority of these use cases is on z/OS (there is significant tech debt adding a JSON converter), and we have other legacy processes using XML that could benefit from this functionality.  This would be appealing to other IBM customers modernizing around Kafka.

  • Guest
    May 23, 2024

    JSON Converter:

    Example Message in XML:

    <?xml version="1.0" encoding="ebcdic-cp-us"?><RecvDeliverSec><FirmNbr>99</FirmNbr><SubNbr>1</SubNbr><BranchId>9AAK</BranchId><RepId>AMGW</RepId><AcctNbr>99086900</AcctNbr><AcctType>1</AcctType><TranDesc>JRL</TranDesc><Qty>+100.00000</Qty><TradeDate>2024-05-17</TradeDate><SecNbr>8978942</SecNbr><Init>659</Init><ExecTradeId>+240517135423305815</ExecTradeId><AcctPseudoType>1</AcctPseudoType><SecDesc>FRANKLIN TEMPLETON</SecDesc><CUSIPNbr>35473P553</CUSIPNbr><SecAlpha>FRKLN LIBERTY US COR ETF</SecAlpha><TypeCode>C</TypeCode><NewTypeCode>M</NewTypeCode><Symbol>FLCB</Symbol><AcctAlpha>RICHIE  ZAPPER</AcctAlpha><ManagePlanId>SUMA</ManagePlanId><PrtfVendorCode>SW</PrtfVendorCode><FirmProductCode>SUMA</FirmProductCode></RecvDeliverSec>


    Example Message in JSON:


                    "RecvDeliverSec": {

                                    "FirmNbr": "99",

                                    "SubNbr": "1",

                                    "BranchId": "9AAK",

                                    "RepId": "AMGW",

                                    "AcctNbr": "99086900",

                                    "AcctType": "1",

                                    "TranDesc": "JRL",

                                    "Qty": "+100.00000",

                                    "TradeDate": "2024-05-17",

                                    "SecNbr": "8978942",

                                    "Init": "659",

                                    "ExecTradeId": "+240517135423305815",

                                    "AcctPseudoType": "1",

                                    "SecDesc": "FRANKLIN TEMPLETON",

                                    "CUSIPNbr": "35473P553",

                                    "SecAlpha": "FRKLN LIBERTY US COR ETF",

                                    "TypeCode": "C",

                                    "NewTypeCode": "M",

                                    "Symbol": "FLCB",

                                    "AcctAlpha": "RICHIE  ZAPPER",

                                    "ManagePlanId": "SUMA",

                                    "PrtfVendorCode": "SW",

                                    "FirmProductCode": "SUMA"



  • Guest
    May 22, 2024

    Please review the link: