To configure Wing Gateway, you also need to open WingFTP's web admin, if you want to add a new gateway server, just navigate to "Server -> Settings -> Gateway Manager", and click on the button "Add Gateway":
And just input a few necessary fields like "Host IP", "Port" and "Password", and then click "OK":
In the above screenshot, you can configure the following settings:
|•||Enable gateway: enable or disable this gateway|
|•||Host IP: the IP address of this gateway|
|•||Port: the port of this gateway, default communication port is 7466|
|•||Password: the communication password to that gateway|
|•||Description: the description note|
|•||Failover server: if enable this checkbox, then the current WingFTP machine will play as a failover server, it will standby until the master node fails or goes down.|
|•||Connection Test: click this button to verify whether gateway settings are correct|
After adding the Wing Gateway, you need to add the listener proxy for the gateway, just navigate to "Domain -> Settings -> Listeners":
Double click on the existed listener (or add listener if no listener exists), then select the gateway host and input a port which gateway will be listening:
As the above screenshot settings, now Wing Gateway (192.168.31.135) will listen and accept connection on its port 22, and forward all the connections (on port 22) to WingFTP:2200.
That's all things about Wing Gateway settings! Very easy, right?
So if you have several WingFTP server machines, and want to make a FTP server cluster, you just need to add the same settings on another WingFTP machine, then Wing Gateway will distribute incoming connections equally among multiple WingFTP server machines.
Additionally, for keeping the same user data in all the cluster nodes, you need to use database or LDAP authentication, and for keeping the same file data in all the cluster nodes, you need to use NAS server or shared folders. So here is an example of deployment diagram for WingFTP cluster with Wing Gateway: