There’s not really a difference in file_reader and file_sender setup between Apps10 and IFS Cloud.

But there’s a difference if IFS runs on premise or in the cloud. If it runs in the could you won’t be able to access the folders directly. I would suggest to use ftp(s)-reader and ftp(s)-sender instead.

Hi STKIFR,

Hope this post helps as well for shared folders.

Regards,

Sahan

Hello @Sahan Udana ?

Could you please addd me in the group , so i can have access.

Thank you 

Best Regards 

Steve KIRO

Hello @heibde,

The customer is on permise, so it’s not going to fit the set up ftp(s)-reader and ftp(s)-sender

Adding the content of that post

Q: 

File Connector – File connector runs inside of the connect container hence it is not possible for the user to place the files inside the folder in the container. IN and OUT folder shared location and path should be provided in the settings along with a username and a password for accessing this location. This is necessary as you are accessing a shared location. File connector will work only with the on-premise customers. This won’t work with the cloud customers.  

Based on above;

1. Should shared folders IN and OUT must be on the Linux server ?
2. If the folders can be also somewhere on an Windows Server, what must be done to access them from IFS Connect ?

There is a customer with a on premise installation who puts a windows path, with user and password, but File Reader cannot access it.

Answer:

1. it could be placed inside Linux server or inside the windows management server as well. For a Linux system SMB server should be installed.
2. First you will have to create a shared folder and need to provide this path when setting up the file reader and should make sure that the full qualified path to the server is given. Also the archive folder. If the file reader still do not pick files from the shared folder, it is possible to increase the log level to debug and check the  output logs for any hints.