This article describes how to test run a SystemWeaver mirror server configuration to ensure that it starts successfully and that client applications can connect to it.
- An installed and configured SystemWeaver main server is running with journaling enabled
- A SystemWeaver Test Server (swTestServer) executable located in the same directory as the SystemWeaver mirror server installation (executables swDBServer.exe and Systemite.SystemWeaver.TcpSubServer.exe)
- A journal file has been created for the database
- A cache file has been created for the mirror server
- The mirror server's configuration file is located in the same directory as the SystemWeaver mirror server installation
- An installation of the SystemWeaver Client (swExplorer) on another machine
- The account running the mirror server mush have minimum Write access to the cache file
- The account running the mirror server mush have minimum Write access to the directory where cache file is located
- Confirm that no other process is running against the cache file
Starting a Mirror Server using the Test Server GUI
The swTestServer executable enables you to run a mirror server using a Windows GUI. We recommend that you use the swTestServer initially when setting up a new mirror server installation. The GUI makes it easier to test and observe an installation.
In the mirror server installation, double-click on the swTestServer executable file to open it. If it is located in the same directory as the mirror server's swServer.ini configuration file, the settings in that file will be loaded for you. You can modify any of the available settings as needed, or enter all settings manually if you do not have a configuration file in place. Note however that if you want to test with SSL encryption* enabled, you must have a configuration file in place with the required settings defined.
Before starting the mirror server, be sure that the main server is up and running. If you recently started the main server, you can verify that start-up is completed by either logging in to the server with a client, or viewing the running process in the Task Manager to confirm that the Memory is no longer increasing.
When you are ready to start the test mirror server, click Start. The server first performs initialization and then checks the mirror's cache to make sure it is in sync with the main server. It is ready to accept connections from SystemWeaver clients when the log window at the bottom of the GUI indicates that the TCP server is started:
Note: Should you receive any alerts from Windows Defender or your anti-virus software, simply allow access and/or create exceptions for the SystemWeaver executables. (If needed, see How to Report SystemWeaver Falsely Detected as Malware.)
Note: The swTestServer is only used to test the server application itself and is not used when executing the server as a Windows service.
When you have completed your testing, just click Stop to terminate the server.
Starting a Mirror Server Without the GUI
If you prefer not to use the swTestServer for testing or do not have one available, the server can also be executed in the foreground by double-clicking the swDBServer main server executable or from a Windows command line. This assumes that there is a swServer.ini file in the same directory containing a valid configuration for the mirror server. However, when testing new installations, the test server's GUI is recommended because of its useful log window.
When started in the foreground, the swDBServer will display the following status in a command window when it is up and running:
When you are ready to stop the server, X out of the window.
Testing a Connection
Once the server is running, you should test that a SystemWeaver client can connect from another machine. See Logging in to the Server for instructions. For new databases, you can use the "admin" username to log in. The "admin" account is installed with the predefined password “wagadoff”. The password should be changed before any user accounts are created.
If you are testing a new installation and the mirror server starts successfully, the next step is to decide upon a configuration alternative. We recommend the mirror server be run as a service using the SystemWeaver Monitor Service.
* The availability of the encryption option is restricted due to EU regulations. Please contact us for more information.