Running the server as NT service

When the Scribe server is started as an ordinary application, it will continue to run as long as the user that started it- remains logged into his/her Windows session. Logging out of the session terminates the server, and all Scribe clients that might have been logged into the server at that time.

The NT service preference allows installing the Scribe server as Windows service, that can start automatically at the system boot time, and does not require a user login to run. The service installation (and de-installation) is handled by a toggle button in the Preference panel, as shown below:

The service is installed with the automatic start option.

Advanced options

The details of the service setup are controlled by the configuration template file wrapper.conf.template, located in the Scribe server installation (home) directory. This file is documented internally, and should be consulted with whenever the default settings need to be changed. Among other factors, the configuration file establishes the order of dependencies for the service; i.e. if there are some other applications on the Scribe host that the server depends on for proper functioning (e.g. a database), then the configuration file can ensure that the server does not start until other critical services are operational.

As the file name wrapper.conf.template suggests, it is a template that is used by Scribe Administrator to generate the actual configuration file, wrapper.conf, that provides the configuration settings to the NT service manager. If the template file is edited, the user should either delete the wrapper.conf file, or change the selection of the setup database adaptor to force the re-generation of the configuration file.