The various SystemWeaver applications can be used in many different configurations according to the needs of the organization. This article illustrates some of the configuration possibilities.
The 'SWClient' in the examples illustrates any kind of SystemWeaver client such as a swExplorer, a swAdmin2, and swArchitect or any custom SystemWeaver client.
SystemWeaver TestServer Configuration
The TestServer configuration illustrates the simplest SystemWeaver configuration. The swTestServer runs the SystemWeaver server executables via a user-friendly GUI interface. The advantage of this configuration is that it is very easy to install on any PC using the GUI of the swTestServer in case any troubleshooting is needed. It should be noted that this configuration runs directly under a Windows session. If the session is killed, the server will stop running as well.
Typically any SystemWeaver installation will be tested first in this configuration, and later when the configuration has been tested successfully, the configuration will migrate into a monitor service configuration.
SystemWeaver Monitor Service Configuration
The swServerMonitorService monitors its server applications and can restart them when necessary. More detailed information can be found in Introduction to the SystemWeaver Monitor Service.
SystemWeaver Slave Server Configuration
When a SystemWeaver Client is located geopgraphically far away from an swServer (with inherent network latency), the use of an swSlaveServer (see SystemWeaver Slave Server) can greatly reduce loading time of large models to the client, since the swClient only interacts with the swSlaveServer. The swSlaveServer should preferably be located at a server computer close to the swClients that will access it.
SystemWeaver Notification Server Configuration
Full SystemWeaver Configuration
Below is an example of a full SystemWeaver configuration including multiple swServers, a slave server and a notification Server.