From ba3e60d2215508bca5f58be1c56a4ca517f32ddd Mon Sep 17 00:00:00 2001 From: rsoulliere Date: Mon, 2 Jan 2012 09:09:59 -0500 Subject: [PATCH] Add requirements-configuration file to master. --- admin/requirements-configuration.xml | 99 ++++++++++++++++++++++++++++++++++++ 1 file changed, 99 insertions(+) create mode 100644 admin/requirements-configuration.xml diff --git a/admin/requirements-configuration.xml b/admin/requirements-configuration.xml new file mode 100644 index 0000000..e399249 --- /dev/null +++ b/admin/requirements-configuration.xml @@ -0,0 +1,99 @@ + + + + System Requirements and Hardware Configurations + + Evergreen is extremely scalable and can serve the need of a large range of libraries. The specific requirements and configuration of your + system should be determined based on your specific needs of your organization or consortium. +
+ + Server Minimum Requirements + + The following are the base requirements setting Evergreen up on a test server: + + An available desktop, server or virtual imagevirtual image + 1GB RAM, or more if your server also runs a graphical desktop + Linux Operating SystemLinux + Ports 80 and 443 should be opened in your firewall for TCP connections to allow OPAC and staff + client connections to the Evergreen server. + + + + DebianLinuxDebian and + UbuntuLinuxUbuntu are the most widely used + Linux distributions for installing Evergreen and most development takes place on Debian based systems. If you are new + to Linux, it is strongly recommended that you install Evergreen on the latest stable server edition of Debian + (http://www.debian.org/) + or Ubuntu 10.04 Server(http://www.ubuntu.com/) since the installation instructions have been + tested on these distributions. Debian and Ubuntu are free distributions of + Linux. + +
+
+ + Server Hardware Configurations and Clustering + hardwareclustering + + The hardware requirements for running a functional Evergreen server are minimal. It is also possible to scale up your evergreen configuration to be + spread your Evergreen resources and services over several or even many servers in a clustered approach for the purpose + of system redundancy, load balancing and downtime reduction. This allows very large + consortia to share one Evergreen system with hundreds of libraries with millions of records and millions of users, making the scalability of + Evergreen almost infinite. + Here are some example scenarios for networked server configurations: + + A small library library with 1 location, under 25,000 items and a few thousand users could easily run Evergreen on a single server + (1 machine). + A college or university with 1 million items and 20,000 users could run an Evergreen system using several servers balancing the + load on their + system by spreading services over multiple servers. It should host their PostgreSQLdatabases + PostgreSQL + database on a separate server. They could also cluster the Evergreen services + strategically to minimize or eliminate any necessary downtown when upgrading Evergreen or other server software. Moreover, system redundancy will reduce the chance of + unplanned catastrophic downtime caused by system failure since Evergreen will be running over several machines. + A large library consortium with several public library systems and/or academic libraries with millions of users and items could run an + Evergreen + system over many servers with clusters for Evergreen services as well as a cluster for the Postgresql Database. + + The key to Evergreen scalability is in the OpenSRF configuration files + /openils/conf/opensrf.xmlconfiguration filesopensrf.xml and + /openils/conf/opensrf_core.xmlconfiguration filesopensrf_core.xml. + By configuring these files, an administrator could cluster evergreen services over multiple hosts, change the host running a specific service + or change the host of the PostgreSQL database. + + The default configuration of Evergreen in the installation instructions assumes a single localhost + server setup. For more complex + multi-server clustered configurations, some server administration and database administration experience or knowledge will be required. +
+
+ + Staff Client Requirements + + + Staff terminals connect to the central database using the Evergreen staff client, available for download from + The Evergreen download page. The staff client must be installed on each staff workstation and requires at + minimum: + + Windows (XP, Vista, or 7), Mac OS X, + or Linux operating system + a reliable high speed Internet connection + 512Mb of RAM + The staff client uses the TCP protocal on ports 80 and 443 to + communicate with the Evergreen server. + + + Barcode Scanners + Evergreen will work with virtually any barcode scannerbarcode scanner – + if it worked with your legacy system it should work on Evergreen. + + + + Printers + + Evergreen can use any printer configuredprinters for your terminal to print receipts, check-out slips, holds + lists, etc. The single exception is spine label printing, which is still under development. Evergreen + currently formats spine labels for output to a label roll printer. If you do not have a roll printer + manual formatting may be required. For more on configuring receipt printers, see Printer Settings. + +
+ -- 2.11.0