The staff client must be installed on each staff workstation and requires at minimum: Windows (XP, Vista, or 7), Mac OS X 10 or later, or Linux operating system
4GB RAM or greater
Dual Core CPU or greater
Broadband internet connection. The staff client uses the TCP protocol on ports 80 and 443 to communicate with the Evergreen server. See also http://docs.evergreen- ils.org/2.3/_staff_client_requirements.html
Windows: 2GB RAM (at least 512MB RAM must be available to staff client under normal system load)
Pentium 4 or newer processor
200MB of hard drive space
Macintosh: Intel x86 processor or greater 512 MB of RAM 200 MB hard drive space
Optimal Internet Service Packages
For an optimal experience, we recommend library service packages with their Internet Service Providers at the following levels, where available: 6/1 Mbit Down/up | Latency: 100ms.
Please note – other hardware may run Evergreen but may not be supported by your consortium. Always check with local IT staff for any local minimum requirements.
From the Start menu, select “run” and enter taskmgr.exe then press return.
From the “Performance” tab look for the Physical Memory (MB) section’s “Available” value. This should be 300 or greater for the Evergreen Staff Client to perform at its best.
There is a lot of variance here, depending on expected load/use, the size of your data, the performance you require, and the amount of redundancy/availability/failover you want. The entire Evergreen server can run in a 1GB virtual image. It can also be spread out across multiple servers, with different requirements for different components. It requires some flavor of Linux, though may possibly run on other POSIX systems.
Evergreen is typically deployed using commodity hardware in the following formation:
Brick: hosts PAC services (both staff and public). Each brick is ideally comprised of two servers, a front running apache, and a back running drone services (auth, circ, cat, search). At smaller scales, the front and back can be on the same server.
Firewall & Load-balancer: required in multiple brick environments tosplit HTTP/HTTPS traffic between bricks.
Reports: highly variable load
Backend (holds,fines,A/T,etc.): runs the drone services that would generally be considered background/scheduled work. Examples would be processing holds as books are checked in, handling fines, email notifications.
SIP2: Partially depends on the back end or a drone,but is a good candidate to separate out. SIP2 generally requires ~60-180MB per connection (lower while idle). Every self-check station will require it's own connection, as will many other things like PC reservations.
Logging(via syslog protocol): For security & problem detection/analysis,all of the other roles report to a central logging location.
DB: This is the PostgreSQL database. Heavy random read/write IO performance required.