IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting 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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Dec 16 2020
  • Future consideration
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.

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.