SecureTransport 5.3.6 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content Manage your servers 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. 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 Advertised ciphers and cipher suites. 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: Manage server operations - Describes monitoring server status indicators, starting and stopping servers, and reloading the server configuration. Manage the FTP server - Describes managing the FTP server. Manage the HTTP server - Describes managing the HTTP server. Manage the AS2 server - Describes managing the AS2 server. Manage the SSH server - Describes managing the SSH server. Manage the PeSIT server - Describes managing the PeSIT server. Manage the Transaction Manager server - Describes managing the Transaction Manager server. Manage the Proxy server on SecureTransport Edge - Describes managing the Proxy server on the SecureTransport Edge. Manage the Monitor server - Describes managing the Monitor server. Use the operating system to monitor SecureTransport processes - Describes using the operating system tools to monitor SecureTransport processes. Related Links
Manage your servers 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. 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 Advertised ciphers and cipher suites. 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: Manage server operations - Describes monitoring server status indicators, starting and stopping servers, and reloading the server configuration. Manage the FTP server - Describes managing the FTP server. Manage the HTTP server - Describes managing the HTTP server. Manage the AS2 server - Describes managing the AS2 server. Manage the SSH server - Describes managing the SSH server. Manage the PeSIT server - Describes managing the PeSIT server. Manage the Transaction Manager server - Describes managing the Transaction Manager server. Manage the Proxy server on SecureTransport Edge - Describes managing the Proxy server on the SecureTransport Edge. Manage the Monitor server - Describes managing the Monitor server. Use the operating system to monitor SecureTransport processes - Describes using the operating system tools to monitor SecureTransport processes.