Record map messages are objects, where as EnsLib.EDI.XML.Operation.FileOperation expects messages of type EnsLib.EDI.XML.Document (vdoc). There are 2 options for you:

1. Transform the record map batch message to XML. e.g call the XMLExportToStream which will convert the record map batch to XML into a stream, which can then be loaded to EnsLib.EDI.XML.Document (using ImportFrom stream methods). This vdoc message then be forward to your XML file operation.

2. Create a custom operation which can create XML from the recordmap batch and write it to a file.

Thank you.

Hi Tom

"None" might end up processing a file which is not completed yet. It really depends on the size of the file and how the source system/application creates the file too.  The FTP Adapter will start checking if the file is ready to process as soon as it sees it in the source folder. Size & Rename would be a safest setting for ConfirmComplete.

As the documentation says QueueCountAlert is only to monitor queue for the configured number of threshold limit. It is not designed for monitoring the queue that either only keeps growing or stopped processing messages (though the queue count may also be an indication of this).

QueueWaitAlert can be used to alert if the messages are not processed or slower than usual. But this doesn't monitor for growing queues primarily. This checks for the first message in the queue on how long it is in the queue and alerts if the queue waiting time is more than the configured threshold on QueueWaitAlert. 

Managed Alerts can be also used which is a work flow based alert management.

Alternative is to create a custom service (refer OnProcessInput method in Ens.MonitorService.cls) to implement the required Monitoring to the production.