SystemWeaver Servers can be executed as Windows Services using the swServerMonitorService utility application. This is recommended since it offers greater flexibility and additional automatic restart functionality of the managed processes.
Running the SystemWeaver server application as a Windows Service offers the following advantages:
- The service and server application(s) can be started automatically when the server computer is started.
- The server application(s) can be configured to restart automatically (optional) in the event it has been terminated, e.g., due to a manual termination or server computer failure.
- The server does not depend on a login session, i.e., no user needs to be logged in to the server computer.
- The service offers slightly higher performance since no on-screen logging is performed.
- The service supports multiple instances of the same SystemWeaver server.
Below are two examples of SystemWeaver Monitor Service uasge.
One SystemWeaver Server and a Notification Server
Multiple SystemWeaver Servers, a Slave Server (on a separate Windows Server) and a Notification Server
Other optional servers can also be included in the settings, e.g., the Rest API.
Note: Only one swServerMonitorService can be run at a time on a server machine.
To get started with setting up the SystemWeaver Monitor Service, see Installing the SystemWeaver Monitor Service.