SAR Technology: 'Incident
Commander V5'
Software
- International
Edition
'Incident Commander' - Network Selection & Setup
Selecting
a Network Configuration
Two network configurations
are recommended for optimum program performance:
Environment 1:
Environment 2:
Windows XP Professional in a peer-to-peer configuration.
Summary
Environment 1, the Server
Configuration, is far
more stable, and generally faster than the peer-to-peer file sharing employed by
Windows XP Pro. The server platform’s ability to manage cache memory and
record locking seem to provide a more stable environment for deployment in a
networking situation. However Environment 2, the XP Pro platform, has a distinct
cost saving over the server platform.
Environment 1, utilizing a Windows
2000 Server, a SCSI hard drive, and 10 / 100 Ethernet, produced the fastest raw
network performance for clients running the network version of the Incident
Commander software. It should be noted that the hard drive specifications and
interface, is a definite factor in the high performance of the system. This
configuration was tested on a desktop server, as SCSI versions of hard drives on
laptops do not seem to be an available option.
This desktop configuration did
not exhibit any noticeable issues surrounding Incident Commander and it’s use on a
true server platform. This configuration was also tested with Windows 2003
Server installed on a laptop with some measurable performance increases,
especially with some of the new features inherent in this latest release of the
server operating system. The Windows 2003 Server server-based network
configuration provided the highest speed and by far the most stable network
environment.
Setting
up a Network System
Environment
2, utilizing Windows XP
Pro in a Peer-to-Peer Network Configuration, provided basic functionality for
a small number of clients. It is strongly recommended that the only XP Pro be
used as the host and not the Home version. The primary benefit of the Windows XP
Pro
configuration is reasonable network stability and moderate cost.
Step 1.
Install Incident Commander on the Host computer, then register the
program with the required number of Network Licenses.
Step 2. Run
the IC_ClientSetup program, on each
Client computer, to install all of the necessary system files onto each Client
computer to be networked to the Host.
Step 3. Follow
the step-by-step instructions described in Configuring
Incident Commander For Network Use PDF document, to configure
Windows XP to run Incident Commander
over the network.
Note: Microsoft's website provides
more detailed information on how to
configure a file
sharing network for Windows XP.
ConclusionsThe server software is designed to provide optimized network use and as a
result performs far better than the peer to peer configuration in the network
environment. There are, however, two issues to consider when choosing the server
option.
The cost for the Windows server software is substantial.
The server software, potentially on a laptop, requires
substantial computing power, and therefore the hardware specifications are of
importance. Typical areas to watch for are ram speed and quantity, hard drive
access speed and network bandwidth capabilities. It should be noted that current
laptops are not certified for the server version of the Windows software,
however no detectable anomalies were encountered when the software was installed
and tested on a laptop.
The use of the server software in
large network deployments would probably justify the additional cost.
For small network environments, Windows XP Pro in a peer-to-peer
configuration, will provide adequate basic file and print services for a few
clients. It should be noted the other applications installed on the client and
host machines should be carefully monitored and minimized, as they can affect
the stability.
Prepared by: Glen
Kulak
Go
to: Networking
the 'Incident Commander' Software
SAR Technology Inc.
4315 Keith Road, West Vancouver
B.C., Canada V7W 2L9
Phone:
(604) 590-7419 / (604) 921-2488 
Fax (604) 921-2484
Go Back to SAR Technology
Home Page