This article describes how to test run a SystemWeaver installation to ensure that it starts successfully and that client applications can connect to it.
- An installed and configured SystemWeaver server
- A SystemWeaver Test Server (swTestServer) located in the same directory as the SystemWeaver server executables (swDBServer and Systemite.SystemWeaver.TcpSubServer.exe)
- An installation of the SystemWeaver Client (swExplorer) on another machine
Starting a Server using the Test Server GUI
The swTestServer executable enables you to run a server using a Windows GUI. We recommend that you use the swTestServer initially when setting up a new installation. The GUI makes it easier to test and observe an installation.
Double-click on the swTestServer executable file to open it. If it is located in the same directory as a swServer.ini configuration file, any settings in that file will be loaded for you. You can modify any of the available settings as needed. They are described in more detail in the Formatting the swServer.ini section of Installing a New SystemWeaver Server.
When you are ready to start the server, click Start. The server first performs initialization and checks the integrity of the database. 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.
If the server does not start properly, see Troubleshooting Server Installation. If you are unable to resolve the problem, contact email@example.com
Starting a Server Without the GUI
If you prefer not to use the swTestServer 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. 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 server starts successfully, the next step is to decide upon a configuration alternative. We recommend the server be run as a service using the SystemWeaver Monitor Service. In addition, there are other server applications that the organization may want to incorporate, such as a SystemWeaver Slave Server and/or a SystemWeaver Notification Server.
For the installation to be usable, users have to be added, a meta model must be created or imported and then views will need to be configured. These topics and more are covered in separate articles in the Support Portal Knowledge Base.