Name of the MFT Connection.

Provide a description for the MFT Connection.

The host name or IP address of the server.

The port number to use for connecting to the server. If left blank, the default port number is 21.

The user name to use for connecting to the server.

The password to use for connecting to the server.

Indicates whether or not the MFT Connection will use

Passive

or

Active

mode. Specify

Yes

to use

Passive

mode. Specify

No

to use

Active

mode. If you do not select either value, the default

Active

is applied.

The starting port number to use for the data connection. This should be used when Active mode is specified and there is a limited range of open ports on your firewall allowed for data connections.

The ending port number to use for the data connection. This should be used when Active mode is specified and there is a limited range of open ports on your firewall allowed for data connections.

The number of seconds to wait when attempting to connect to the server. A timeout will occur if the connection cannot be established in the specified amount of time. If left blank, the default timeout is 120 seconds.

The number of times to retry the FTPS connection if it cannot be established. This setting is used for both the initial connection and any reconnect attempts due to lost connections. If left blank, then no retries will be attempted.

The number of seconds to wait between each connection retry attempt.

The initial directory to start in after connecting to the server. If left blank, then the initial directory will be the home directory assigned to the user on the server.

If left blank, Managed File Transfer uses the ISO standard ISO-8859-1. If supported by the server, other encodings like UTF-8 can be specified to support more international characters.

Limit the inbound and outbound bandwidth used for file transfers.

If enabled, Managed File Transfer uses the default certificate that is defined in the Managed File Transfer default key store.

Select a Managed File Transfer client certificate using the client certificate alias. A particular key within the Managed File Transfer default key store can be used for client authentication by indicating the key alias. The specified key will be used when required by the FTPS server.

The list parser to use for the server connection. If the field is blank, Managed File Transfer will try to use the MLSD parser. If the server does not support the MLSD parser, the UNIX parser is used. If you experience problems listing directories, select a different list parser.

Use this field if the server returns a date that is different from the selected list parser's default. If your location requires a different date format (for example, d MMM yyyy), specify the date format in this field. Not all list parsers support the date format setting. List parsers that do not support the Date Format setting will ignore any User specified values.

Specify the date format to use when parsing the recent last modified date for each file. The recent date format is primarily used on UNIX-based systems and appears on entries less than a year old. If your location requires a different recent date format (for example, d MMM HH:mm), specify that pattern in this field. Not all list parsers support the recent date format setting. List parsers that do not support the recent date format setting will ignore any User specified values.

Managed File Transfer supports SOCKS (version 4 and 5), HTTP tunneling through an HTTP proxy and Managed File Transfer Gateway. HTTP tunneling requires that the HTTP proxy supports the CONNECT HTTP method. Not all HTTP proxy servers might support the CONNECT method and some might only allow HTTPS traffic. When using an HTTP proxy that requires authentication, Basic and Digest authentication schemes are supported. Check with the network administrator for the correct proxy type.

The host name or IP address of the proxy server.

The host name or IP address of an alternate proxy server. The alternate proxy server is used when the primary proxy server is unavailable.

The port number to use for connecting to the proxy server. If left blank, the default port for an HTTP connection is 80 and SOCKS is 1080.

The user name to use for connecting to the proxy server.

The password to use for connecting to the proxy server.

Indicates if the connection type is Implicit SSL or Explicit SSL. The preferred connection type is the more modern Explicit SSL standard, however some trading partners might still require Implicit SSL. If this field is left blank, then the default connection type of Explicit SSL will be used.

Indicates whether SSL or TLS should be used for Explicit SSL connections. TLS is the latest security protocol standard, however many trading partners still use the SSL protocol for Explicit SSL connections. If this field is left blank, then the default security protocol of SSL will be used.

Indicates whether or not to use a clear command channel (CCC) for the FTPS connection. Specify

No

to keep the command channel encrypted. Specify

Yes

to not encrypt the control command channel (however, the actual data transfers will remain encrypted). If neither value is selected, then the default value of

No

will be used.

The data channel protection level indicates if the data channel is encrypted. Select

Private

to keep the data channel encrypted. If the FTPS server does not support an encrypted data channel, select

Clear

to leave the data channel unencrypted. The default setting is Private.

After the command channel is closed, most servers automatically close the SSL/TLS connection, however some servers do not understand the "close_notify" command. Select

No

to keep Informatica Managed File Transfer from sending the "close_notify" command. The default value is

Yes

.

Specify the protocol to use when creating the SSLContext. The value you need to specify here depends on the security providers you have installed in the JRE (Java Runtime Environment). In most cases, the default value (TLS) should just work fine. However, on some IBM JRE implementations the default value would not work if the server you are connecting to does not support TLS 1.0.