The SystemWeaver Notification Server can be run as a Windows Service using the swServerMonitorService utility application. Since the swServerMonitorService supports multiple server instances, if you are already using the utility application to run the SystemWeaver server, you can simply add a <Server> entry for the swNotificationServer to the swServerMonitorService.settings file rather than setting up a separate Windows service for it. In the below example, there is one SystemWeaver server being run (swDBServer.exe) along with one RestAPI, and one swNotificationServer. Note that the Notification Server is set with a start delay of 10 seconds. This is recommended so that the main server executable restarts first.
The <exe>, <ini> and <props> entries should refer to the notification server installation folder on the server machine's local drive. Note that when the server applications are executed as part of a service they do not have a home directory, so using these entries is the only way to direct the files to the applications. For more information about formatting the swServerMonitorService.settings file, see Installing the SystemWeaver Monitor Service.
To confirm that the swNotificationServer.exe is up and running, look for the process in the Task Manager:
Likewise, you can view the swNotificationServer.log file to confirm the server is listening for events: