This document provides an overview of Mulesoft's File Connector. It discusses how the File Connector can be used as an inbound or outbound endpoint to exchange files with a file system. It also covers installing and configuring the File Connector, including the inbound vs outbound endpoint types and the Reconnection and Transformer tabs in the properties editor. The document concludes with a demo of using the File Connector to move files from one directory to another.

1. Mulesoft
File Connector
https://docs.mulesoft.com/mule-user-guide/v/3.8/file-connector
Kumar Gaurav
k10gaurav@gmail.com

2. Agenda
• Introduction
• Installation and configuration
• Inbound vs outbound endpoint
• Reconnection Tab
• Transformer Tab
• Demo
• Conclusion

3. About
The File connector allows your Mule application to exchange files with
a file system.
You can implement the File connector as an inbound endpoint (such
as, a message source), or as an outbound endpoint.
This endpoint implements a one-way exchange pattern only.

4. Installation and configuration
Installation:
You can install a connector in Anypoint Studio using the instructions in
Installing a Connector from Anypoint Exchange.
Configuration:
File endpoint configuration consists of two stages:
1. Place the File endpoint within the Mule flow you are developing:
o If you place the File endpoint at the beginning of the flow, it acts as an inbound endpoint
(such as, message source), triggering the flow whenever it receives an incoming file.
o If you place the File building block in the middle or at the end of the flow, it serves as an
outbound endpoint, passing files to the connected file system.
2. Configure the File endpoint by providing values for the fields on the various tabs on
the properties editor.

5. Inbound vs outbound endpoint
Inbound endpoint
Configuration XML Default Representation
<file:inbound-endpoint path="" responseTimeout="10000" doc:name="File"/>

6. Inbound vs outbound endpoint
Outbound endpoint
Configuration XML Default Representation
<file:outbound-endpoint path="" responseTimeout="10000" doc:name="File"/>

7. Reconnection
By default, there is no reconnection strategy implemented for you, but you may
choose to configure reconnection on a set frequency (Standard
Reconnection) or via Custom Reconnection strategy.

8. Transformers Tab

9. Demo
Step 1: Create a new flow fileconnectordemoFlow as directed below:

10. Continue…
Step 2: Configure file connector (FileMove) as directed

11. Continue…
Step 3: Add logger just after it to see the operation in log:
Message:
#['FILE_NAME- '+message.inboundProperties.originalFilename],#['FILE_SIZE- '+((message.inboundProperties.fileSize)/1024)+'KB']]

12. Continue…
Resulting XML config would be:

13. Continue…
Now, we let’s start testing by running the application
Corresponding logger message in console:
Also the files from source directory has been moved to target location. Please
verify the same.

14. Conclusion
So this way we have seen how file connector works as a powerful component
in files movement within local file system.

15. Thank you!