By Managed File Transfer (short MFT) we understand the file transfer from point A to point B.
Here the communication or exchange can consist of any combination of HDD and FTP.
So all permutations of the two variants:

• Dateisystem Empfangskanal to Dateisystem Sendekanal or
• Dateisystem Empfangskanal to Ftp/Ftps Sendekanal or
• Ftp/Ftps Empfangskanal to Dateisystem Sendekanal or
• Ftp/Ftps Empfangskanal to Ftp/Ftps Sendekanal.

Note: In addition, eBiss specific methods can be used here, so that a partner recognition based on the paths¹⁾ and a partner specific²⁾ forwarding is possible without having to look into the files³⁾.

1. For each source path - target path combination⁴⁾ there is a new tradingpartner with corresponding communication addresses of the type file system, consisting of the directory names.
   1. The target path is the default address for the send channel (“MFT.Send”) and
   2. the source_path for partner detection at the receive channel⁵⁾
2. To collect these partners in a group, you create a corresponding template partner, for which the outgoing communication channel is stored.
3. For the files there is a mailbox⁶⁾ specially created for this purpose, in which all files end up:
   1. the messages that cannot be forwarded are directly discarded in a part of a job⁷⁾,
   2. all others are marked as “send” by the send channel (“MFT.Send”).
4. The receive channel⁸⁾, which also carries out partner detection based on the source directories, moves the contents of the folders to a subdirectory⁹⁾
5. A file system transmission channel with a corresponding destination path and the setting “Use transmitter address”.
6. A job(“MFT.In”)) opens the receive channel(“MFT.Receive”) and
   1. discards all files that match the filter specified¹⁰⁾.
   2. All files that do not match the first filter will be filtered again in the second step in reverse¹¹⁾
   3. OPTIONALLY a CustomJob Object can be triggered¹²⁾

All the names for channel / jobs etc. are fictitious

C:\TEMP\MFT_TEST
├───Partner A
│ └───Archiv
├───Partner B
│ └───Archiv
├───Partner C
│ └───Archiv
├───Partner X
│ └───Archiv
└───Partner Y
  └───Archiv

z:\hostsystem_edi_inbound
├───host1
├───host2
├───host3
├───host4
└───host5

1. Navigate to the desired source path (it is best to create a temporary folder)
2. There create some folders with test files (do not create “archive” folders)
   
   
3. Then start the job that picks up the files and filters them - here “MFT.In”
   
4. Check the directory - If everything worked fine, there should be no files in the folders. They should now be in a newly created subfolder “Archive”