The SystemWeaver Server Monitor Service Status Tool is useful if you have multiple SystemWeaver server applications running on the same server machine, e.g., in a test/QA environment. Using it, you can stop and start individual server applications in the Server Monitor Service without disrupting the other server applications that are running in the service. The tool can be run directly as an executable in a Windows session as needed, or as a server application in the service. It is only accessible from the server machine where the SystemWeaver Monitor Service and SystemWeaver Monitor Service Web App Host are running. This article describes how to view the tool, and use it to start and stop servers in the service.
- The SystemWeaver Monitor Service 2 is installed and running.
- The SystemWeaver Monitor Service Web App Host is installed and running.
- SystemWeaver version R40 or later.
Viewing the Status Tool
To view the Status Tool, open a browser on the machine where the SystemWeaver Monitor Service and SystemWeaver Monitor Service Web App Host are running.
Navigate to http://localhost:5000/status to see the Web App GUI. The port should match the value for key="WebHostPort" in swServerMonitorWebAppHost.exe.config.
If the Status tool is left open and inactive, you will need to refresh the page (press F5) to use it.
Stopping and Starting a Server
To stop a specific server in the service, find the entry in the tool and click Stop.
When you are ready to restart the server, click Start in the tool.
Things to Consider
If the database is very large, it may take some time to complete the stop and start processes.
You can monitor the progress via the Task Manager.
Stop: It is completely stopped once the server application is no longer listed as running process and the tool indicates that it is stopped. Do not perform any tasks/restart, until you are certain that the server is stopped.
Start: It has completed the startup process once the Memory usage has stopped growing as seen via the Task Manager.