Skip to content

File Inbound Endpoint

Introduction

The file inbound protocol is an alternative to the VFS transport. It uses the VFS transport to process files in a specified source directory. After processing the files, it moves them to a specified location or deletes them. Note that if files remain in the source directory after processing, they will be processed again. Therefore, if you need to maintain these files or keep track of the files that are processed, specify the option to move them instead of deleting them after processing.

Parameters

See the list of VFS parameters that can be used with both inbound endpoints and proxy services.

Processing Sub Directories

VFS Inbound endpoints are capable of handling files inside sub directories of the specified URL. Please note the following configurations that required to achieve the requirement.

  • Configure the input file URL to read sub files within sub directories. Please note /* at the end, which is mandatory to achieve the requirement.

    <parameter name="transport.vfs.FileURI">///home/user/test/in/*</parameter>

  • Configure the output directory with the same pattern if you wish to preserve the directory structure.

    <parameter name="transport.vfs.MoveAfterProcess">///home/user/test/out/*</parameter>
<parameter name="transport.vfs.MoveAfterFailure">///home/user/test/fail/*</parameter>

  • Use the following transport property within the sequence whenever you need to access the relative path of the files within sub directories.

    <property expression="$trp:RELATIVE_PATH" name="relative_path"/>