From b27bcc59aee883f3f5178d7a46dd9e6c679344e5 Mon Sep 17 00:00:00 2001 From: Robert Soulliere Date: Mon, 16 Aug 2010 15:47:24 -0400 Subject: [PATCH] Add Admin requurements and configurations chapter. --- 1.6/admin/admin-intro.xml | 2 +- 1.6/admin/requirements-configuration.xml | 83 ++++++++++++++++++++++++ 1.6/admin/serveradministration.xml | 4 +- 1.6/root.xml | 1 + 4 files changed, 87 insertions(+), 3 deletions(-) create mode 100644 1.6/admin/requirements-configuration.xml diff --git a/1.6/admin/admin-intro.xml b/1.6/admin/admin-intro.xml index cd030fb289..f9820b0f78 100644 --- a/1.6/admin/admin-intro.xml +++ b/1.6/admin/admin-intro.xml @@ -1,4 +1,4 @@ - + This part of the documentation is intended for Evergreen administrators and requires root access to your Evergreen server(s) and administrator access to the Evergreen staff client. It deals with maintaining servers, installation, upgrading, and configuring both system wide and local library settings. Some sections require understanding of linux system administration while others require an understanding of your system hierarchy of locations and users. Many procedures explained in the following chapters are accomplished with linux commands run from the terminal without a Graphical User Interface (GUI). diff --git a/1.6/admin/requirements-configuration.xml b/1.6/admin/requirements-configuration.xml new file mode 100644 index 0000000000..d10a83c357 --- /dev/null +++ b/1.6/admin/requirements-configuration.xml @@ -0,0 +1,83 @@ + + + + System Requirements and Recommended 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 image + 512MB RAM + Linux Operating System + + Debian and Ubuntu 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 Network Configurations + + As apparent in the previous section, the base hardware requirements for running a functional Evergreen server are extremely minimal. It is also possible + to scale up your evergreen configuration to be spread your Evergreen resources and services over many servers in a clustered approach. 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 a server network configuration: + + A small public library or school 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 could also run + PostgreSQL on a separate server. They could also cluster the Evergreen services in a way to minimize or eliminate any necessary downtown when upgrading Evergreen, + the operating system or the database software. + 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, balancing the load on the system while sharing resource costs. At the same time, it gives users searching capabilities to search + several library systems simultaneously. + + The key to Evergreen scalability is in the openSRF configuration files /openils/conf/opensrf.xml and + /openils/conf/opensrf_core.xml. + By editing these files an administrator could quickly cluster evergreen services over multiple servers, change the server running a specific service + or change the server of the postgreSQL database. + + The default configuration of Evergreen in the installation instructions assumes a single localhost server setup. For more complex + multi-server configurations, some server administration and database administration experience or knowledge may 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 + + + + Barcode Scanners + + Evergreen will work with virtually any barcode scanner – if it worked with your legacy system it should work on Evergreen. + + + + Printers + + Evergreen can use any printer configured 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. + +
+ diff --git a/1.6/admin/serveradministration.xml b/1.6/admin/serveradministration.xml index a2abbb0bc0..6a44d49968 100644 --- a/1.6/admin/serveradministration.xml +++ b/1.6/admin/serveradministration.xml @@ -1968,8 +1968,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Check the check box(es) next to the circulation modifiers(s) you wish to delete. Click Delete Selected near the top of the page. - The selected circulation modifiers will be deleted without a - verification alert. + The selected circulation modifiers will be deleted without a + verification alert. diff --git a/1.6/root.xml b/1.6/root.xml index 85b7439994..2824604b0d 100755 --- a/1.6/root.xml +++ b/1.6/root.xml @@ -57,6 +57,7 @@ Administration + -- 2.43.2