Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Dec 16, 2020

Ability to convert JSON payload to XML sent to asynchronous defined in OMS

OMS currently supports conversion of JSON payloads to XML if passed to REST endpoints defined from OMS. However, if there are asynchronous services defined in OMS using JMS/ MQ, it mandates that the inputs passed is always XML for consumption by OMS APIs/ services defined in SDF. There will be customization required in OMS if this conversion needs to be done or mandate the sending system to pass XML to OMS.

The conversion logic from JSON to XML which the framework handles for REST endpoints needs to be supported for Asynchronous services too as this will reduce customization effort across implementations and integrations.

What is your industry? Computer Services
How will this idea be used?

OMS currently supports conversion of JSON payloads to XML if passed to REST endpoints defined from OMS. However, if there are asynchronous services defined in OMS using JMS/ MQ, it mandates that the inputs passed is always XML for consumption by OMS APIs/ services defined in SDF. There will be customization required in OMS if this conversion needs to be done or mandate the sending system to pass XML to OMS.

The conversion logic from JSON to XML which the framework handles for REST endpoints needs to be supported for Asynchronous services too as this will reduce customization effort across implementations and integrations.