Configuring a FTP Emitter


Messages are sent to particular destinations at the completion of a workflow. The state of the document determines which destination is used. The order in which the destinations are used cannot be predicted.

Note: Configuring a FTP emitter is not required if the outlet (emitter) protocol is the same as the inlet (listener) protocol.

To route an output document or error message to a protocol other than that of the outlet (listener) used, you must configure an emitter. For example, if an application can send input over MQSeries, but you want to route the output to a FTP destination.

Reference: FTP Emitter Parameters

The following table lists and describes parameters for the FTP emitter.



Destination (required)

The file@host. If an asterisk (*) is entered, a time stamp is substituted for the file name.

User Name (required)

The user ID on the FTP host.

Password (required)

The user password on the FTP host.

Account Name

Some FTP servers require an ACCT command as part of their login credential exchange. If configured, this information is sent by the ACCT command when the login is attempted.


In ASCII mode, conversions are done (EBCDIC to ASCII and vice versa). In BINARY mode, the data remains unchanged.

Socket Timeout

The time, in seconds, in which a read() call on the socket blocks. If the timeout expires, a is raised.

Rename To

The name to give the uploaded file after the upload is complete. Use an asterisk (*) in the name to be replaced by time stamp and # by a sequential counter, for example:



If a destination file exists, the information is appended to that file. Otherwise, a new file is stored.

Quote Command

The entered command is sent as typed, BEFORE any data transfer begins. Following login to the FTP server, if this is configured it is a command to be sent to the server. Often this is used to accomplish a secondary login.

File Protect

Emits a temporary name and then renames it to the desired name.

Starting SITE command

The SITE command to issue before the transfer of data.

Successful SITE command

The SITE command to issue after the successful transfer of data.

Error SITE command

The SITE command to issue if the transfer of data fails.


Secure Control Connection

Use a secure control connection, for example, transfer user ID and password securely. Data transfer will not be secured. You may need to configure the keystore under the HTTPS section of the system properties if client authentication is required.

Note: If the keystore is configured in system properties, make sure it has the CA certificate or the client certificate of the server to which you are connecting. If the keystore is not configured in system properties, the default truststore located under <JRE_HOME>/lib/security/cacerts is used.

SSL Security

Select one of the following FTP server connection types from the drop-down list:

  • unknown. Defaults to explicit security then fails over to implicit security.
  • explicit. In order to establish the SSL link, explicit security requires that the FTP client issue a specific command to the FTP server after establishing a connection. The default FTP server port is used.
  • implicit. Implicit security automatically begins with an SSL connection as soon as the FTP client connects to a FTP server. In implicit security, the FTP server defines a specific port for the client (typically 990) to be used for secure connections.

Keystore Security Provider

Enter the iWay Keystore Security Provider name. If this component is secure and Keystore Security Provider is left blank, the default Keystore Security Provider is used.

Secure Data Connection

This determines whether to use a secure data connection (transferring data securely). This is used in conjunction with Secure Control Connection.

Use 128-Bit Encryption

This enforces the use of 128-bit encryption.

Security Protocol

The security protocol. Available options are:

  • SSL. Supports some version of SSL. May support other versions.
  • SSLv2. Supports SSL version 2 or higher.
  • SSLv3. Supports SSL version 3. May support other versions.
  • TLS. Supports some version of TLS. May support other versions.
  • TLSv1. Supports TLS version 1. May support other versions.