The following configuration properties determine which configuration mode and connection type the (S)FTP Client communication point is to use:

Configuration Mode

Configuration Mode determines whether the (S)FTP Client communication point is operating in static, or dynamic mode using XML configuration templates or message properties:

Property Option Description
Use Static Configuration† A static mode in which all parameters except the Base Filename and suffix are set statically at configuration time.
Dynamic Using XML Configuration Templates A dynamic mode in which XML configuration templates can be used to override the static configuration when a message is sent or received. This dynamic mode cannot be used in Input-only mode.
Use Message Property Configuration A dynamic mode in which message properties can be used to override the static configuration when a message is sent or received. This dynamic mode cannot be used in Input-only mode.

† Default option.  

In dynamic mode, all properties are available for modification.

Configuration Templates

Configuration Templates allows multiple sets of configuration settings to be set using an auxiliary configuration XML file. It must be provided and be valid if XML configuration templates are in use. Refer to Dynamic Mode and Dynamic Configuration Using XML Templates for details.

Protocol

Protocol determines the type of FTP connection that should be used:

Property Option Description

FTP†

 File Transfer Protocol (FTP) is a standard network protocol used to transfer files from one host to another host over a TCP-based network.

FTPS Implicit

Implicit FTPS is a deprecated standard for FTP that requires the use of an SSL or TLS connection.

FTPS Explicit

Explicit FTPS is an extension to the FTP standard that allows clients to request that the FTP session be encrypted.

SFTP

SSH File Transfer Protocol is an FTP-like protocol that operates over an SSH connection. Normally, an SFTP/SSH server listens on port 22 for a connection. SFTP connections are protected using DSA or RSA key pairs to encrypt the secure channel between the client and the server. In order to verify that the (S)FTP Client Communication Point is connected to the correct SFTP server (rather than some arbitrary SSH server), it is mandatory to configure it with the SFTP server's SSH public key. Rhapsody is then able to validate that the correct public key is presented by the SFTP server before it sends any authentication information or message data to the server. The SFTP server almost always authenticates the client using the following authentication modes:

  • Password authentication - the client provides a username and password to the server over the encrypted channel.
  • Public key authentication - the client provides a username and proof of ownership of an SSH private key.
  • Password and public key authentication - the client provides a username, password, and proof of ownership of an SSH private key.
  • Keyboard interactive authentication - not supported by the FTP/SFTP communication point.

The SSH keys used to validate the server and perform client authentication are retrieved from the Certificate and Key Manager in Rhapsody IDE.

† Default option.