MFT - Push Files
Utilize this type of Job in order to automatically push files to a remote MetaDefender Managed File Transfer instance.
Unlike the system-level MFT to MFT mirroring functionality, the MFT - Push Files Job only transfers files from configured sources for users who have specifically defined these jobs.
Configuration
Target MFT Username
The username to authenticate with on the remote MetaDefender Managed File Transfer instance.
Target MFT Password
The password to authenticate with on the remote MetaDefender Managed File Transfer instance.
In case of editing or duplicating a previously saved job, the password needs to be re-entered.
Select Target MFT
The MetaDefender Managed File Transfer integration which files will be pushed to.
See: MFT Integration
Source Folders
Provide paths to recursively collect files from and push them to the selected MetaDefender Managed File Transfer instance through HTTP(S). Any number of paths can be configured, if no path is added, the root ('/') will be the source path.
The folder structure under the configured source path(s) will be preserved at the destination.
Push Files as a Member of the Selected Group
Enter the Active Directory group you want to use for uploading files. Different groups may have different security settings. This field is only required when uploading files to an Active Directory user on the target MFT.
For further information about the security aspects, read Custom MetaDefender Core Workflow rule for Groups and Active Directory Supervisors Setup.
Destination at Target MFT
The destination path on the remote MetaDefender Managed File Transfer instance to push the files to. If the path does not exist it will be created automatically.
Transfer Method
Decide what to do with the original files on the local instance.
- Copy Files: Files successfully pushed will remain intact on the local instance.
- Move Files: Files successfully pushed will be removed from the local instance.
In case multiple source paths point to the same file, the file will only be deleted on the local instance if it was successfully pushed from all listed source paths.
For example, if move is enabled and there is a file /data/logs/log.txt and source paths /data and /data/logs are configured with destination /pull it will only be removed from the local instance if pushing was successful for both /pull/logs/log.txt and /pull/log.txt.
File Overwrite Rules
Decide what to do if a file with the same path already exists in the remote MetaDefender Managed File Transfer instance.
- Don't Overwrite: Do not push the file to the remote instance.
- Overwrite Existing: Push the file to the remote instance and remove the originally existing one.
Overwrite doesn't do any pre-check on the local or the remote file, it is just simply overwriting the remote file with the local one even if they contain the same data. This means if a file does not change on the local instance the same file will be pushed over and over again.
Example
I want to push files to my remote MetaDefender Managed File Transfer instance from my local instance. I only want to push files that are under the path /work/share and /tools, I want this to be done every Tuesday at 10AM and on Fridays at 4PM. My username is teodor and my password is pass%123! on the remote instance.
My remote instance can be reached on the FQDN mft.remote.io. I want my files to remain on my local instance, just copy them for my user under the path /pushed/mft on the remote instance. If a file already existed remotely then keep that, don't overwrite it.
