M3 MT cloud ION: Inbound Bank statement MT940 gems flat file not coming the same from JMS queue like

Legacy Contributor

Hi,

Currently the Bank statement MT940 inbound flat file comes from a folder (File connection point) so it picks the File template schema. With Document ID and Raw data.

Where Raw data is the base64 data which is converted as per the file template defined. In file template in ION format type is "Binary"

Now customer wants to move away from folder and use the JMS queue.

When they send the file on jms queue it is transforming the entire flat file data in one xml tag. Even if they send bas64 file instead of flat file it doesn't give the same result as it gives when a file comes from a folder (file connection point)

Have anybody worked on this kind of request or any idea how can i make the file coming from jms identical to the file coming from the folder (File connection point). I need both the tags Document ID and RawData or else the next xslt transforms are failing and blank bank statement file is going from ion to m3.

Best Regards

Shashank Malali

Maxime Richard

Hello,

Do you mean that the base64 encoded data is the content of the file and not the file itself ?

How did you set up your message queue connection point ? Any screenshot ?

Can't they build a complete BOD that looks like the binary one you were using before (DocumentID + RawData tags = base64 encoded file) and push it in the queue ?