Server control

Operations > Server Control

The Server Control page is the entry point for SecureTransport administrators on successful login. Here you view and manage all protocol servers, the TM server and the Monitor server of your system.

Server control is available on both SecureTransport Server and SecureTransport Edge.

Server Control: Protocol servers

The protocol servers (also called daemons) you can manage on the Server Control page are: FTP, HTTP, AS2, SSH and PeSIT.

Each daemon is represented by a dedicated panel. The daemon's settings and status, as well as the available management actions are located in the panel header. From here, you can edit the daemon settings and perform actions like start and stop the daemon or adding a new server.

For each server, the panel displays current Status, basic configuration options, including listener port and key alias. You can also perform certain actions, like start and stop a server, or changing server configuration, distributed in dedicated controls, as follows:

  • the "gear" iconallows you to edit the configuration parameters of the corresponding server
  • the "play" icon( when server stopped) interchanges with the "stop" icon ( when server running); these controls apply the corresponding action to the selected server only

The following topics provide more details on adding and editing server daemons with the respective protocol:

Disabling protocol servers

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.

Server Control: Folder Monitor

Folder Monitor is available only on SecureTransport Server and is dependent on the value of the FolderMonitor.enable Server configuration option. Its dedicated pane allows you to see its Status and to Start the FM (when not running) or Stop the FM (when running).

Server Control: Scheduler

Scheduler is available only on SecureTransport Server and is dependent on the value of the Scheduler.enable Server configuration option. Its dedicated pane allows you to see its Status and to Start theScheduler (when not running) or Stop the Scheduler (when running).

Note
The Scheduler.enable and FolderMonitor.enable server configuration options do not start or stop the respective cluster services; they only enable or disable the service. When Transaction Manager is running and Folder Monitor/Scheduler is disabled from the Server Configuration (the respective configuration parameter is set to false), the service runs in the background but does not do any job (schedule events or pull files). Folder Monitor/Scheduler is running and functional only when the Transaction Manager is started, and Folder Monitor/Scheduler is started and enabled from the Server Configuration.

Server Control: Transaction Manager server

The Transaction Manager (TM) server connects to the ports specified in the network zones. Its dedicated pane allows you to see its Status and to Start the TM (when not running) or Stop the TM (when running).

For more information, see Communication across Transaction Manager, protocol, and proxy servers.

Note There is no TM panel in the Server Control page on SecureTransport Edge.

Server Control: Monitor server

The Monitor Server uses the monitord monitoring service to perform periodical checks and identify if the SecureTransport servers are functional or not. Its dedicated pane allows you to see its Status and to Start the TM (when not running) or Stop the TM (when running).

For more information, see Monitor Server.

Server status indicators

The table below lists the various status options available from the Server Control page and when SecureTransport displays that status.

Status Description Used during:
Running
(displayed in green)
The server is running normally. Normal operation
Running
(displayed in blue)
An HTTP or FTP server suspension is pending, with the server suspension information displayed below. Scheduled suspensions
Not Running
(displayed in red)
The server is stopped. Disabled or stopped servers
Suspend
(displayed in red)
The HTTP or FTP server is scheduled to suspend in the near future. The HTTP or FTP server is running, but does not allow transfers. Users can still connect and get messages. Temporary suspensions, such as for maintenance

Server Control on SecureTransport Edge

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.

On the SecureTransport Edge, specify the port for the SecureTransport proxy server. The proxy port is used by SecureTransport Server to handle outgoing connections passed through a SecureTransport Edge. The default is port number 1080.

  1. On the Server Control page, under Proxy Server, enter a value in the Proxy Port field.
  2. Click Start.
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.

Related Links