Managed File Transfer Gateway Guide

10.4.0
- 10.5.3
- 10.5.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Server Configuration

To configure the

Managed File Transfer

Gateway server, open the

gateway.xml

file located in the

[install_directory]/gateway/

directory using a text or XML editor.

Listed below are the attributes that can be updated:

Attribute Name	Description
controllerAddress	The local IP address on which Managed File Transfer Gateway should listen for Control Connections from . Be sure this IP address is reachable from the system where is installed.
controllerPort	The port number on which Managed File Transfer Gateway should listen for Control Connections from Managed File Transfer . The default port number is 9100. Be sure this port is open for outbound connections on the firewall protecting the private network.
dataAddress	The local IP address on which Managed File Transfer Gateway should listen for Data Connections from Managed File Transfer . When an external client connects to the Managed File Transfer Gateway, opens a data connection which attaches to the desired service. The IP address specified here should be accessible from the system where is installed.
dataNATAddress	The IP Address that should connect to when establishing a data connection with Managed File Transfer Gateway. Managed File Transfer Gateway will send this address to when a new client connects. This should be used only if connections from to Managed File Transfer Gateway are routed through a NAT firewall.
dataPort	The port number on which Managed File Transfer Gateway should listen for Data Connections from Managed File Transfer . The default port number is 9101. Be sure to open this port for outbound connections on the firewall protecting the private network.
dataNATPort	The port number Managed File Transfer Gateway will direct to connect to when establishing a data connection. This should be used only if connections from to Managed File Transfer Gateway are routed through a NAT firewall.
forwardProxyLocalAddress	The local IP address Managed File Transfer Gateway will use when active data connections are requested. This address is also used to establish outbound connections to remote servers when Managed File Transfer Gateway is used as a forward proxy. The value should be the local IP you wish to have used when establishing an outbound connection from the Managed File Transfer Gateway server.
proxyAddress	The local IP address on which the Outbound Proxy component of Managed File Transfer Gateway should listen for incoming requests. The Outbound Proxy works similar to a SOCKS Proxy, which accepts CONNECT and BIND requests from clients. A CONNECT request is used to connect out to another system on the Internet, whereas the BIND request is used to temporarily listen on a port for accepting incoming connections from a system on the Internet. The Outbound Proxy is used by the FTP and FTPS services in to facilitate routing of passive and active data connections through the Managed File Transfer Gateway. When an external FTP client requests a data connection in passive mode, the FTP service sends a BIND request to the Outbound Proxy. Managed File Transfer Gateway then listens on a temporary port for the incoming connection. After accepting the connection, any data is routed to the intended destination. When an external FTP client requests an active data connection, the FTP service sends a CONNECT request to the Outbound Proxy specifying the IP address and port it should connect to. Once the connection is established, any data will be routed to the intended destination. The Outbound Proxy can also be used by when using the FTP, FTPS, SFTP and SCP protocols.
proxyNATAddress	The IP Address that should connect back to when establishing an FTP Active or Passive data connection through Managed File Transfer Gateway. Managed File Transfer Gateway will send this address to during the initial handshake, and will connect to this address when an FTP/S client requests an Active or Passive data connection (see proxyAddress). This should be used only if you are supporting FTP/S Active or Passive data connections in , and if all connections from to Managed File Transfer Gateway are routed through a NAT firewall. This is not required when using Managed File Transfer Gateway as a forward proxy from .
proxyPort	The port number on which the Outbound Proxy component of Managed File Transfer Gateway should listen for incoming connections. The default port number is 9102. Be sure to open this port for outbound connections on the firewall protecting the private network.
proxyNATPort	The port number which Managed File Transfer Gateway will direct to connect to when establishing an FTP Active or Passive data connection through Managed File Transfer Gateway. Managed File Transfer Gateway will send this port to during the initial handshake, and will connect to this port when an FTP/S client requests an Active or Passive data connection (see proxyPort). This should be used only if you are supporting FTP/S Active or Passive data connections in , and if all connections from to Managed File Transfer Gateway are routed through a NAT firewall. This is not required when using Managed File Transfer Gateway as a forward proxy from .
passiveProxyAddress	The local IP address on which the Managed File Transfer Gateway should listen for incoming passive FTP data connections from external clients.
passiveProxyPortRangeFrom	The beginning port in the range of ports available for FTP passive data connections.
passiveProxyPortRangeTo	The ending port in the range of ports available for FTP passive data connections.
proxyEnabled	The outbound proxy component of Managed File Transfer Gateway can be enabled or disabled.
shutdownPort	The port number on which Managed File Transfer Gateway should listen for shutdown requests. For security reasons, Managed File Transfer Gateway binds the shutdown listener on the LOOPBACK address, thus ensuring shutdown requests are accepted only from the local host. The default port number is 9105.
minThreads	The minimum number of spare threads that Managed File Transfer Gateway should always have available. The default value is 10.
maxThreads	The maximum number of threads that Managed File Transfer Gateway is allowed to use. The default value is 2000.
threadKeepAlive	The number of seconds an unused thread would stay alive before it is discarded. The default value is 60 seconds.

Managed File Transfer

Gateway must be restarted for any changes to take effect. If the controllerAddress or controllerPort have changed, all instances of that are setup to use this gateway must also be updated, and the connection to

Managed File Transfer

Gateway must be restarted.

Configuring Managed File Transfer Gateway

Load Balancer

Default gateway.xml Configuration

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal