|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (8)
View Page History...
|| Attribute || Description || Default value || Required ||
| filename \\ | The name of the file where the JBI message (the XML content) will be written in. \\
| filename \\ | The name of the file where the JBI message (the XML content) will be written in. \\
...
h1. Invoking service on incoming file
If you want to invoke a service in the JBI bus with files, put the files in the configured directory (read-directory). (folder). At each configured polling period (polling-period), the component fetchs the incoming files.
For each received files and according to the transfer mode (transfer-mode or base-msg), the component creates a new message exchange and attachs the file, either as source or as source, attachment. or none.
If a file is put as a attachment, the name of the attachment is set to the name of the file, and in the source of the message exchange, the component put a XML structure like following :<attached-files> ccording to xop rules.
<file-name>myFileName</file-name>
<attached-files>
The resulted message exchange(s) are sent to the target endpoint.
During the transfer, if the backup directory (backup-directory) is set, the transfered file is moved into it and never deleted by the component. Otherwise the file is moved to the system temporary directory.
During the transfer, if the backup directory (backup-directory) is set, the transfered file is moved into it and never deleted by the component. Otherwise the file is moved to the system temporary directory.
When deploying a service unit like in the previous following code snippet, all the files put in the directory $PETALS_HOME/filetransfer/in would be set as the payload of an invocation to the FileService service.
h2. Configurations
...