VIGILANCE XPRESS SYSTEM REQUIREMENTS
VIGILANCE XPress™ Deployment Prerequisites
Hardware -- Production
The server hardware requirements for a VIGILANCE XPress™ deployment are dependent on the data sizing and CPU requirements for the production platform.
For production deployments that can quickly scale to dozens of users, with potentially multiple data marts and cubes, you will require, at a minimum, a production Intel® server with 2 dual-core 64-bit Xeon™ processors operating at 2.5 GHz (minimum) and a storage array, NAS or SAN.
Other hardware requirements:
- Memory: a minimum of 4 GB; 8 GB is recommended
- Storage: a minimum of 250 GB of disk consisting of 7200 RPM IDE or Serial-attached SCSI (SAS); although 500 GB of disk is recommended; we also strongly recommend a RAID1+0 array for redundancy and hot-swap capability
- CD / DVD: a DVD ROM drive is required
- Network: 1,000 MB / sec (aka Gigabit) Ethernet is highly recommended; 100 MB / sec is acceptable
- Warranty: We recommend a 3-year Next Business Day on-site warranty for the production server
Hardware -- Testing & Evaluation
For testing or evaluating VIGILANCE XPress™, a non-virtualized desktop or mid-tier laptop computer no more than 3 years old will likely have the acceptable processing power, memory, storage and network resources.
Software
You will need the following software components:
- Operating System: Microsoft Windows Server 2003 SP1 [32-bit] Standard Edition or later, with Internet Information Services (IIS) 6.0 HTTP Web Server
- Database: SQL Server 2005 SP2, Standard Edition or later, including SQL Server Reporting Services (SSRS) and SQL Server Analysis Services (SSAS)
Note: A user account with administrator privileges (including being a member of the "OLAP Administrators" group) should be created and used to run and administer all SQL Services (e.g. SQL Server, SQL Server Agent, MSSQLServerOLAP Service) and for some of those services to use as a log-on user name
- Other Infrastructure: Microsoft .NET Framework 2.0
- Windows Domain:
-- A Windows Active Directory configuration is required
-- The server and all clients must be members of a Network Domain that can be "seen" by the server
-- SQL Server 2005 and the Domain Server must not be on the same platform
Note: If no Active Directory or Network Domain is present, the user must belong to the "local administrators" group
|
