10.10. Configuring the File System Provider

The following file system provider configuration options are available within a file system message filter (fs-message-filter) which itself is contained in an fs-bus. For a good example, see the helloworld_file_action quick start.

Note

For the directory options below, each directory specified must exist and the application server's user must have both read and write permissions on the directory in order to move and rename files through them.
Table 10.6. File System Message Filter Configuration
Property Description Required
directory The directory that will be monitored for incoming files. Yes
input-suffix Suffix used to filter for incoming files. Must be one character or greater, with a ".", such as ".esbIn". Yes
work-suffix The suffix used when a file is being processed by the ESB. The default is ".esbInProcess". No
post-suffix The suffix used when a file has been successfully processed by the ESB. The default is ".esbDone". No
post-delete If true, the file will be deleted after it is processed. In this case, post-directory and post-suffix have no effect. Defaults to true. No
post-directory The directory to which the file will be moved after it is processed by the ESB. Defaults to the value of directory above. Yes
post-rename If true, the file will be renamed after it is processed. Note that the post-rename and post-delete options are mutually exclusive. No
error-delete If true, the file will be deleted if an error occurs during processing. In this case, error-directory and error-suffix have no effect. This defaults to "true." No
error-directory The FTP directory to which the file will be moved after when an error occurs during processing. This defaults to the value of directory above. Yes
error-suffix The suffix which will be added to the file name after an error occurs during processing. Defaults to .esbError. No
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.