Oliver Wilms · Dec 7, 2020

Record Maps - is message required to be in a file?


I like to know if we need to have the message in a file to process a Record Map?

I am working with Interoperability Production that processes files /messages using Record Maps. My team was asked to redesign the solution for deployment in AWS. We use containers. We had problems with having multiple containers processing files from the same directory. We are considering Amazon Simple Queue Service instead of having files on a shared file system.

Has anybody migrated a Record Map to a Schema Definition to validate a message as a Virtual Document as I have seen with X12 messages?

Some of our messages are received via HTTP request. We take the message from the request body and save the stream to a file to process the record map. We look for ways to simplify this process. Any suggestions are appreciated.



Product version: IRIS 2020.1
$ZV: IRIS for Windows (x86-64) 2020.1 (Build 215_0_20264U) Fri Sep 25 2020 10:12:48 EDT
0 149
Discussion (1)1
Log in or sign up to continue

Looking at the code, I see that EnsLib.RecordMap.Service.FileService extends EnsLib.RecordMap.Service.Standard. You can try to create a custom Business Service (for example, EnsLib.RecordMap.Service.StreamService) extending the same parent class and override the OnProcessInput method to process your stream.

One issue you might have is, the FileService is bound to EnsLib.File.InboundAdapter that does a lot of work in the service. There are other types of out-of-the-box adapters - like EnsLib.HTTP.InboundAdapter which you could use here but your code would be customized.

Please note that this might not be officially supported by ISC.