Polling period in milliseconds Directory where read files are moved. ${env} environment variables are supported. Format like C:\ or /home For operations getting files, if set to 'true', files are not moved to the backup directory (see 'backup-directory'). Default value: false Transfer the file into PEtALS as an XML payload or as an attachment Working directory where files are written or retrieved. ${env} environment variables are supported. Format like C:\ or /home CONSUME MODE: pattern used to filter files to read. PROVIDE MODE: name of the file written by PEtALS, appended with date-time (if not set, the file name is the operation name or 'content.xml'). The skeleton of XML-message to send to the consumed service. It may contain $content or $attachment, or none of them. This is the way the component should link the file with the returned message. $content will be replaced by the file content. $attachment will set the file in attachment. It will be replaced by a xop:include element which references the attachment (MTOM-like). For each "consume" service-unit, the component creates a poller. This parameter defines the maximum number of files that are processed simultaneously. If no more processor thread are available, file to process are queued. Define eviction time in millisecond for processor thread created by the poller Define the number of incoming files processed concurrently in the sliding window, or '0' for no limitation Define the max waiting time that an incoming file waits to enter in the sliding window. If it can't, its processing will be postponed after the next polling period. This parameter has no sens if external-processor-block-size is set to '0'. Define the waiting time to read a locked file. If no value is defined at SU level, the value defined at component level is used. Define the period to check the locking wait time. If no value is defined at SU level, the value defined at component level is used.