OFTP (embedded) fields

An embedded OFTP V1 or V2 server is available after a community adds a delivery exchange that uses an embedded ODETTE File Transfer Protocol server. You can change the server’s settings and advanced options.

To change settings:

  1. Select System management > Manage embedded servers.
  2. Alternatively, you can click Trading configuration on the toolbar, click on the Communities page, and then click the link near the bottom of the page named Change an embedded transport server.
  3. From the list of embedded servers, click the name of an OFTP server to open the modification page.
  4. Click Save changes when you are done.

The following are the maintenance fields for an embedded OFTP transport server. The fields for OFTP V1 and V2 are the same.

Settings tab (without TLS)

  • Server name – The name for the embedded OFTP server. This can be any name you want.
  • Host – The fully qualified domain name of the computer on which the embedded server runs. Activator detects this setting; you cannot change it.
  • Port – The TCP port on which the server listens for connection requests. This field does not apply to OFTP V1 X.25.

Settings tab (with TLS)

  • Server name – The name for the embedded OFTP server. This can be any name you want.
  • Host – The fully qualified domain name of the computer on which the embedded server runs. Activator detects this setting; you cannot change it.
  • Port – The TCP port on which the server listens for connection requests. This field does not apply to OFTP V1 X.25.
  • This server requires client authentication – Select this to use the partner’s certificate to authenticate the partner when the partner connects to the server.
  • Add a TLS server certificate or TLS server certificate – For optional TLS, the server requires a TLS certificate. If the server has a certificate, the name of the certificate is displayed. If the server does not have a certificate, you are prompted to provide one.

Advanced tab

  • Minimum threads – The least number of threads Activator must dedicate to the server.
  • Maximum threads – The most threads Activator can dedicate to the server.
  • Read timeout (seconds) – How many seconds of inactivity to allow before Activator terminates the connection.

Related topics

Related Links