Server control

Use the Server Control page to manage the protocol and TM component servers of your SecureTransport system. On the Server Control page for a SecureTransport Server you can specify port, SSL key alias, and FIPS transfer mode settings for the FTP, HTTP, AS2, SSH, PeSIT, and Transaction Manager (TM) servers and start and stop them. These are the component servers of the SecureTransport Server. You can also start and stop the Monitor server.

Server Control - View and maintain servers.

On the Server Control page for a SecureTransport Edge, there is no TM Server pane because the Transaction Manager does not run on the SecureTransport Edge, but you can configure the port for the SecureTransport Edge proxy server. For details, see Manage the Proxy server on SecureTransport Edge.


Note By default, SecureTransport Edge uses a cipher strength of AES 256 for communication between its protocol servers and the TM Server on the SecureTransport Servers. To change the cipher suites enabled, edit the TransactionManager.Listeners.Ssl.enabledCipherSuites server configuration parameter. For valid values, see the cipher suites listed for transfers using AS2, FTPS, HTTPS, and PeSIT over secured socket in the SecureTransport Cipher suites topic, part of the SecureTransport 5.4 Security guide.

When you disable any of the component servers using the Administration Tool, the scripts used to run the servers from the command line are renamed with the .disable extension. To disable a server clear the check box for that server. Once the servers are enabled, the files are restored to the original name. For example, if you disable the FTP server, the script start_ftpd is renamed to start_ftpd.disable. Once you select the enable check box and start the server using the Administration Tool, the script name returns to start_ftpd. All utility scripts are located in the <FILEDRIVEHOME>/bin directory.

The following topics provide additional information for managing and monitoring the servers:

Related Links