|
|
|
System Requirements
|
Software Requirements
|
|
If installing on Windows Vista
|
If installing on Windows Vista, WebWatchBot for SQL Server must be installed. We recommend
installing SQL Server 2005 with SP1 (SP1 is a requirement for SQL Server 2005 on Windows
Vista) or SQL Server 2008.
MSDE (Microsoft SQL Server Desktop Edition) is not compatible with Windows Vista; therefore,
WebWatchBot with MSDE cannot be installed on Windows Vista.
|
|
If installing on Windows Server 2003 SP1
|
There is a setting change that needs to be made in Windows after installation to
properly run WebWatchBot. Please refer to this KB article:
Installing WebWatchBot on Windows Server 2003 SP1
|
|
MDAC (Microsoft Data Access Components)
|
Version 2.6 or higher, 2.8 is recommended.
MDAC Download from Microsoft.com
(Opens a new window)
You may have already have a version installed...Windows OS/Software and Default MDAC version:
- Windows Vista - Up to date, requirement met.
- Windows Server 2003 - 2.8 - Up to date, requirement met
- Windows XP - 2.7 - Up to date, requirement met
- Microsoft SQL Server 2000 Service Pack 3a - 2.71 SP1 Refresh - Up to date, requirement met
- SQL Server 2000 SP2 - 2.6 SP2 - Up to date, requirement met
- SQL Server 2000 SP1 - 2.6.1 - Up to date, requirement met
- Windows 2000 Service Pack 3 - 2.5 SP3 - Need to download and install latest MDAC.
Windows NT 4.0 users may need to download an install the latest Microsoft Jet
Engine Update. Refer to: http://support.microsoft.com/default.aspx?kbid=239114
|
|
Internet Explorer
|
Version 5.5 or higher required.
|
|
Additional Configuration Requirements/Recommendations
|
WebWatchBot's Database
|
WebWatchBot 5.0 uses Microsoft SQL Server to store the data that it collects for
maximum efficiency and scalability.
WebWatchBot will use either:
- An existing installation of SQL Server 2000(Good), 2005(Better), or 2008(Best).
NOTE: Required if using Windows Vista.
Download SQL Server 2005 Express (FREE) from Microsoft. Recommended: better performance and
higher scalability.
Download
SQL Server 2008 Express (FREE) from Microsoft. Recommended: best performance and
best scalability.
- The free desktop
version of SQL Server (MSDE: Microsoft Sql Server
Desktop Engine)
automatically installed for you with no added cost or special licensing.
NOTE: Not compatible with Windows Vista. (If using Windows Vista, you must
use SQL Server 2005 or 2008 - see above)
|
|
Run as a Windows Application
|
-
The logged in user must have FULL CONTROL permission in the directories and
sub-directories:
System Temporary Directory
\Documents and Settings\All Users\Application Data
- The logged in user must have READ, WRITE, EXECUTE permission in the directories and
sub-directories:
\Program Files\WebWatchBot [2/3/4/5]\
- The logged in user must have permission to read, write, and
create keys the system registry.
|
|
Run as a Windows Service
|
- WebWatchBot installs its Windows Service component,
named WWBServer.
NOTE FOR WEBWATCHBOT V3.0.2 AND OLDER: WWBServer must log in under the "Local System Account" Account. This
should not be changed. Additionally, the SYSTEM ("Local System Account"), must be set
to interact with the desktop.
NOTE FOR WEBWATCHBOT V3.0.3 AND NEWER: If you change the logged in user account, ensure to
reflect this change below, substituting SYSTEM with the specified user account.
-
The SYSTEM ("Local System Account") account must have FULL CONTROL permission in the directories and
sub-directories:
System Temporary Directory
\Documents and Settings\All Users\Application Data
- The SYSTEM ("Local System Account") account must have READ, WRITE, EXECUTE permission in the directories and
sub-directories:
\Program Files\WebWatchBot [2/3/4/5]\
- The SYSTEM ("Local System Account") account must have permission to read, write, and
create keys the system registry.
|
Recommended Configurations
|
Minimum System Specification Recommendation
|
Try the
System Configurator
for recommendations
|
Stage 1
1-50 Watch Items
|
WebWatchBot Version: Professional or Enterprise
OS: Windows 2000/XP Pro/2003/Vista/7/2008
CPU: 500 MHz Pentium® II/AMD
Memory: 1 GB
Hard Drive Space: 20-250MB initially, additional 40MB per month
Database Software: Microsoft® SQL Server®. Min ver: MSDE. Rec ver: 2008
WebWatchBot run as a Windows Application or Windows Service
|
Stage 2
50-100 Watch Items, with less than 50 watch items/minute running
|
WebWatchBot Version: Enterprise
OS: Windows 2000/XP Pro/2003/Vista/7/2008
CPU: 4 GHz Intel/AMD based CPU or faster
Memory: 2 GB or more
Hard Drive Space: 40-500MB initially, additional 150MB per month
Database Software: Microsoft® SQL Server®. Min ver: 2000. Rec ver: 2008
WebWatchBot run as a Windows Service
|
Stage 3
100-500 Watch Items, with less than 100 watch items/minute running (The frequency with which Watch Items
are run, directly impacts overall performance)
|
WebWatchBot Version: Enterprise
OS: Windows 2003/2008
CPU: Minimum: 4 GHz Intel/AMD based CPU. Recommended: Xeon or Dual Core or faster
Memory: Minimum: 2 GB. Recommended: 4 GB
Hard Drive Space: 100MB-2.5GB initially, additional 400MB per month
Database Software: Microsoft® SQL Server®. Min ver: 2005. Rec ver: 2008
WebWatchBot run as Windows Service
Other recommendations:
- Consider multiple machines running WebWatchBot
- SQL Server 2000/2005 located on a different server
- No other applications running on server
|
Stage 4
500-1000 Watch Items, with less than 100 watch items/minute running (The frequency with which Watch Items
are run, directly impacts overall performance)
|
WebWatchBot Version: Enterprise
OS: Windows 2008
CPU: Minimum: Intel or AMD Quad Core Processor
Memory: Minimum: 4 GB
Hard Drive Space: 100MB-2.5GB initially, additional 400MB per month
Database Software: Microsoft® SQL Server®. Min ver: 2005. Rec ver: 2008
WebWatchBot run as Windows Service
Other recommendations:
- Consider multiple machines running WebWatchBot
- SQL Server 2000/2005 located on a different server
- No other applications running on server
|
** Please note: Your results may vary based upon factors such as concurrently
executing programs, processes, and services. Additionally, each
Watch Type, e.g., ping, port, http, etc., affects performance
differently based on the resources needed to execute.
|
|
|