EnvisionWare eCommerce Services has three components, a server, a web module, and Windows Clients. Clients operate on any current Windows platform and provide kiosk-based fine payment and account revalue or act as an integrated component that is invoked during the checkout process for some self-check systems. The web server module operates on Apache (Windows or Linux) or IIS web servers and the eCommerce Server runs on a Windows XP Workstation or a server depending on model and library size.
Hardware Requirements for eCommerce Server SLE - Small Library Edition
Windows XP Pro or Windows Server 2003 Operating System
2.5 Ghz Celeron Processor (typical) #
(2) 80GB Hard disk drive (typical), Raid 1 recommended*
512 MB RAM
Ethernet Card
Connectivity path to the Internet and your local LAN
Hardware Requirements for eCommerce Server - Enterprise Edition
Windows Server 2003 Operating System
2.8 Ghz Dual core Processor (typical) #
(2) 80GB Hard disk drive (typical), Raid 1 (minimum typical configuration)*
or
(3) 120 GB Hard disk drive, Raid 5*
1 - 4 GB RAM depending on card transactions per minute
1 GB minimum for 20 transactions per minute
1 GB additional for every (3) Payment Server upgrade modules, max 12 modules
Equals 260 card transactions per minute/ 15,000 per hour, 120,000 per day
Ethernet Card
Connectivity path to the Internet and your local LAN
If you also serve the eCommerce Web components from the same server using the PHP engine and IIS, consider (2) Dual core 3GHz processors for the entire server.
If AAM Database is added to the same server, consider (3) 300 GB Raid 5 Disks instead plus the upgraded (2) processors noted above and less (2) of the maximum additional Payment Servers - total 11 when adding the AAM and web server to the same unit
Separate Web Server
Operate on platform described above with appropriate adjustments or run on separate web server with 1 GB disk space.
The Web Module for eCommerce Services runs on Apache (Windows or Linux) or IIS and may run on other platforms.
* The eCommerce Server holds transaction history so hard disk redundancy should be considered a standard requirement. (Consistent with CISP requirements, we do NOT retain card numbers. As with all EnvisionWare products, we build systems that protect borrower privacy.) While the server may not be mission critical to operation of the library, the data on the server must be resilient and backed up regularly.
# Hardware requirements are stated as typical because the scalability of the software is limited only by hardware. eCommerce Services does not require a dedicated server so the location, dedication, and sharing of other applications depends largely on the size of the institution and the frequency with which patrons will transact self-service fine payments. Hardware requirements are stated as a guide to represent optimal performance under heavy load. They are designed with a 3-5 year hardware life cycle in mind. Historical data suggests that requirements peak when the service is first announced and then taper off to a moderate level. The above are stated to support the potential peaks. Depending on hardware and your library size, you may be able to support the MySQL AAM database, the Web module, and the core eCommerce server on the same device. The processing requirements for MySQL are very low because the architecture is for a data store only, not for execution of scripts or triggers. Your EnvisionWare Regional Manager or a partner salesperson will guide you in configuring hardware to support your enterprise deployment of EnvisionWare.
