IMS endpoint Post message produces json. How to do it for an xml so that it can consume and produce

Hi All,

We have a requirement from a customer who is upgrading from on-prem to MT cloud version of Infor M3.

They will post an xml to ION and also receive an xml through ION in response. Please note they have a mec mapping involved. In on-prem env they used to do https post to mec.

In this case now we are trying to use IMS Messaging services but it produces json output. How we can change that to produce xml output and accept xml input as well.

Best Regards

Shashank Malali

Find more posts tagged with

ION Connect

Accepted answers

unknown

Ok, IMS V3's multiPartmessage by definition sends you the response as an 'application/JSON' and it contains two files:

A manifest file with header information as an 'application/JSON'
The actual payload as an 'application/Octetstream' (which can be of any data format supported in ION such as XML or JSON or DSV..)

So your expectation to receive an XML payload is not a problem as you can get it from the second file directly. All what you need is that the receiving application you are implementing should be capable of receiving a JSON message. The same goes for, when you are sending an XML message as well. As you are building this client application newly anyway, my suggestion would be to build the capability to handle a JSON message. Sample code for how to build this IMS application is available for download from ION Desk -> Configuration -> Downloads -> IMS Client and Server examples.

Need for XML transformation in your document flow is not a problem. If M3 is already producing an XML response, you can directly use an ION(XSLT) mapper to build your output. If M3 is producing a JSON, you can use the ION Scripting (Python) to convert the JSON to the XML you need. And then send it to the custom IMS via ION API connection point which will deliver that XML to your endpoint wrapped in an JSON envelope.

Hope this helps.

All comments

unknown

Can you explain your document flow?

M3 CE is in one end of your document flow. How it connects to ION CE is wired automatically and the format of message (JSON or XML) that it sends to ION is immaterial, as what you are interested is just the payload.

Which application is in the other end of the flow? Is that a custom application? And what type of ION connection point is used for this application? If thats of type IMS then, what version (V2 or V3) ? And what flavor of API it has implemented to receive a message? ('POST Message' or 'POST multipartMessage' ?)

unknown

Hi Vignesh,

Thanks for the reply. version V3 we are trying to use. POST multipartMessage. Ion connection point used is IMS via ion api connection point with client id as the authorization

The other end of the flow is an custom application databox.

They will be sending an xml through "Post" and m3/ ion need to send response xml through "Post".

But in between this there is a mec mapping involved which has input xsd and the output response xsd.

Best Regards

Shashank Malali

unknown

Ok, IMS V3's multiPartmessage by definition sends you the response as an 'application/JSON' and it contains two files:

A manifest file with header information as an 'application/JSON'
The actual payload as an 'application/Octetstream' (which can be of any data format supported in ION such as XML or JSON or DSV..)

Hope this helps.

unknown

Hi Vignesh,

Thanks. All that you stated in above post we have implemented it in another customer but there was no problem as they were doing Post and sending Json. That customer was also having mec mapping so we used the python script there. approach was the same IMS endpoint.

But this customer may be we have to change the approach then.

Thanks for the input though.

Is there any roadmap for this ims endpoint to handle xml? It would be great.

gsingh

Hi, Just picking up this same requirement now we have clarified a few points and tested. The application is not in our control and is external ordering system that currently (on premise) sends orders via xml which mec transforms, runs some custom mapping etc and then sends a synchronous response back. This needs to be done in a few seconds back on the same sending request. I think the IMS endpoint as described is intended to be a custom designed IMS Server application that can accept the response ? Is that correct. If so how can we best achieve that in MT / ION receive an xml request , transform and map with m3 api's etc and then return a custom xml response to the sending application synchronously ? Any help welcome.

Copyright © 2025 Infor. All rights reserved.