This is the correct setup... you would likely want to schedule ListFile to run on Primary Node only, this is an option on the scheduling tab of the processors. That would take care of the problem when the directory is not a shared location, but even when it is shared, you still probably want Primary Node only because you don't want two instances of ListFile retrieving the same files. ... View more

1) You can not apply EL to the content of a flow file, this is by design, The approach you mentioned with ExtractText is correct. 2) You might be able to do this with a custom processor, or possibly somehow using the distributed cache services, but in general a processor is operating on one flow file at a time. ... View more

The ExtractText processor is used to pull up text from the content of a flow file into an attribute. You should be able to add a property like "message.body" with a value of "(.*)" to ExtractText to get it to extract everything. Keep in mind this only makes sense for small messages. Attributes are held in memory and if you did this with a huge flow file you could blow up the memory of your Java process. ... View more