External Application sending Process BOD to ION. Help with information. Thanks

i have a requirement wherein the external application can send the exact Process BOD in xml format and it will be fed into an LN application connection point which will create the transaction and return Acknowledge file. Does it mean the incoming API call has to use this end point: "IONSERVICES/api/ion/messaging/service" ? And this only accepts JSON input? If yes, how can this be converted to Process BOD format? Python scripting or some other component? is there a way so ION can just consume incoming Process BOD and send to LN ? And the Connection point to be used here is "Message Queue type"? If yes, what is this "JMS Server type to Connect to" ? Is this something Infor provides upon request? Might be an elementary question... and in that case, please redirect me to such threads. Many thanks.

Find more posts tagged with

ION API Gateway

Accepted answers

All comments

jschra

Hi Senthil,

assuming LN, is as M3 connected to IMS then the 3rd party could call {{APIBaseURL}}/IONSERVICES/api/ion/messaging/service/v3/multipartMessage with a valid Oauth2 bearer token.

The payload is of type form-data, and one section is MessagePayload, which can be your BOD in XML

The other section is ParameterRequest. This needs to be a JSON formatted parameter message. But this can always be the same.

The 3rd party delivers the BOD to IMS via an own connection point an LN will pick it up from IMS.

When I set this up the first time I used this Infor documentation as reference. Here is also explained how to download the example from ION -> Configuration. -> Downloads. The Postman collection that is part of this download was very useful to test the flow.

Hope this helps.

BR/J

Kevin Heiman

ion/messaging/service/v3 is the ideal way to do this as noted by JuanSz.

Consider if you want to use the multipartMessage vs the message/multipart . The later only has the payload file and uses headers for the Parameter values. Some client application struggle with having two files, so we added this option.

As to the JMS that is a alternative way to connect not using APIs. sFTP(s) is another way, but it is likely your partner wants to use APIs. And you could write your own API using BaaS or API Flows, but we would recommend IMS as it is mature and heavily used.

POST/v3/message/multipart
MESSAGE_MULTIPART_V3 :: Publish message to ION via IMS

This method retains core "message" concept from the v2 version but now supports multipart form data. It offers the possibility of sending message payload in request body (of type multipart/form-data), mandatory and optional properties are now moved to headers and query parameters. This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

jschra

Thanks Kevin - the multipart is sometimes a bit a hassle indeed. I was not aware the additional message/multipart api in v3. Learned something this Friday! Thanks.

Senthil Ganesh Chandraraj

Thanks JuanSz for the details and link to right documentation. Managed to send a BOD into LN via IMS connection point

Senthil Ganesh Chandraraj

Thanks Kevin. using multipartmessage, was able to send a payload into LN via IMS connection point.

Copyright © 2025 Infor. All rights reserved.