The following SystemWeaver executables are the most commonly used applications/application servers. The server applications are all available in a 64-bit version. Whether or not configuration file(s) are required and whether logging is available is indicated for each in the below tables.
|Used by Administrators to manage SystemWeaver user accounts, roles, licenses and security settings.||Used by Architects to administer the installation's SystemWeaver meta models.||The standard SystemWeaver client. The client can be configured to support a number of different development tasks and teams.||Used by IT Administrators to perform upgrades of the SystemWeaver database schema when needed. Also provides various other useful database tools, such as creating a file repository database.|
|Split Server Architecture (consists of two executables)|
|A SystemWeaver Application Server manages all SystemWeaver data and offers connections from any SystemWeaver application through the SystemWeaver API (The swDBServer/swServer runs as a background process in Windows, with interfaces to server configuration files, the database, a log file, and a status window. A SystemWeaver Server assures the integrity and security of the stored data, regardless of the operations performed by connected Clients.)|
For the split server concept, the SystemWeaver server consists of two executables - swDBServer.exe and Systemite.SystemWeaver.TcpSubServer.exe - the swDBServer contains the connection to the database, cached data and all API logic and the Systemite.SystemWeaver.TcpSubServer manages communication through TCP with all the clients and their connections.
|Offers the same services as the swDBServer/swServer, and in addition, has a GUI that offers manual selection of configuration options, possibility to see all logged in users, and a log window corresponding to the optional log file.|
Optional Server Applications
|A SystemWeaver client that sends email notifications upon updates to CMS Project issues.||An application that supports multiple instances of SystemWeaver servers as a service on the same server computer.||Acts as a mirror or replication of a main SystemWeaver server (the server described above), with data residing in a local database. The Slave Server will be replaced in an upcoming release by the Mirror Server.||Our 2nd generation Slave Server. The server application is identical to the main server application. See Split Server Architecture above.|
For a complete list of all SystemWeaver applications, refer to Overview of SystemWeaver Applications in the SystemWeaver Server Administration Manual.