By default, openFT is started automatically at system startup (under Windows systems as service).
The asynchronous openFT server executes asynchronous outbound requests, processes inbound requests, and (only on Windows systems) enables the use of admission profiles. If the asynchronous openFT server is not started, these functions cannot be used.
Starting and stopping the asynchronous openFT server manually
You can start and stop the asynchronous openFT server manually via the ftstart and ftstop commands or via the openFT Explorer with the Administration/Start Asynchronous Server or Administration/Stop Asynchronous Server functions.
Modifying the settings for automatic startup
Unix systems
Automatic startup is preset in the startup file. If openFT is not to be started automatically, the relevant command line must be commented out from the startup file. See section “Disabling the automatic startup of openFT”).
Note: On Solaris systems, automatic startup is performed via SMF.
Windows systems
You can use the openFT Explorer (Administration/Operating Parameters..., Start Asynchronous Server Automatically option) to specify whether the asynchronous openFT server should also be started automatically when the openFT service is started. Note that by default, the option for automatically starting the asynchronous openFT server is only activated for the std instance.