FTP refers to ‘File Transfer Protocol’ which is an internet-based data transfer mechanism much like HTTP (Hyper-Text Transfer Protocol) which is what you would be used to seeing at the start of web addresses that you type into your browser.
SFTP is ‘Secure FTP’ and is designed to encrypt file data sent across the internet similar to HTTPS (HTTP Secure) whilst using the same base protocol of FTP.
Both methods of FTP are essentially the same from the user’s point of view as both will likely require the use of a username and password for MachShip to point to.
As FTP is an older technology and offers several challenges which MachShip have chosen not to support, MachShip does not have an FTP server to which your customers could send their files – instead, you can ‘point’ MachShip at a customer's FTP server so that it can ‘poll’ (ask) that FTP server for any files which it might need to intercept.
An example workflow:
- Consignment created in customer's system.
- Customer's system creates the required file and uploads it to their own FTP server.
- MachShip periodically polls the customer's FTP server and uploads the file into MachShip.
- Consignment is created in MachShip.
- If there are any issues with the file, these issues will need to be resolved manually outside of this workflow.
Technical Level: IT Administrator
- Customers system
- Setup structured files to be generated from the customer's system
- Maintain an FTP Server
- Send files to the FTP Server
- MachShip system
- MachShip team
- Setup within MachShip to poll the customer's FTP server
- Setup within MachShip to send files back to their FTP server
Additional Setup for customer-specific file
- MachShip team
- Develop the mapping to read and import the customer's specific file format
- Creating Consignments