E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (9)
View Page History
...
{section} h1. Invoking service on incoming file (Consumes mode)
If you want to invoke a service in the JBI bus with files, put the files in the configured directory (folder). At each configured polling period (polling-period), the component fetchs the incoming files.
If you want to invoke a service provider in Petals ESB with files, put the files in the configured directory ({{folder}). At each configured polling period ({{polling-period}}), the component fetches the incoming files.
For each received files and according to the transfer mode (transfer-mode ({{transfer-mode}} or {{base-msg}}), the component creates a new message exchange and attachs attaches the file, either as source or attachment.
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 according to MTOM optimization rules.
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 ccording to xop rules.
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 deleted by the component. Otherwise the file is moved to the system temporary directory.
When deploying a service unit like in the 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 _ftContentNoBaseMsgService_ service.
{note}
A InOut service provider can be exposed to be consumed through files. The content of its reply will be ignored. By default the message exchange pattern used to send messages to the service provider is '{{InOnly}}'. Just set the right value into the parameter {{mep}} in the section {{consumes}} of the SU JBI descriptor.
{note}
A InOut service provider can be exposed to be consumed through files. The content of its reply will be ignored. By default the message exchange pattern used to send messages to the service provider is '{{InOnly}}'. Just set the right value into the parameter {{mep}} in the section {{consumes}} of the SU JBI descriptor.
{note}
When deploying a service unit like in the 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 _ftContentNoBaseMsgService_ service.
h2. Configurations
...