Add Admin requurements and configurations chapter.
authorRobert Soulliere <rsoulliere@libdog.mohawkcollege.ca>
Mon, 16 Aug 2010 19:47:24 +0000 (15:47 -0400)
committerRobert Soulliere <rsoulliere@libdog.mohawkcollege.ca>
Mon, 16 Aug 2010 19:47:24 +0000 (15:47 -0400)
1.6/admin/admin-intro.xml
1.6/admin/requirements-configuration.xml [new file with mode: 0644]
1.6/admin/serveradministration.xml
1.6/root.xml

index cd030fb..f9820b0 100644 (file)
@@ -1,4 +1,4 @@
-<partintro xmlns:xl="http://www.w3.org/1999/xlink">
+<partintro xmlns:xl="http://www.w3.org/1999/xlink" xml:id="admin_intro">
        <para>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).</para>
        <para>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).</para>
diff --git a/1.6/admin/requirements-configuration.xml b/1.6/admin/requirements-configuration.xml
new file mode 100644 (file)
index 0000000..d10a83c
--- /dev/null
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="utf-8"?>\r
+<chapter xml:id="requirements" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
+    xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
+    <info>\r
+        <title>System Requirements and Recommended Configurations</title>\r
+    </info>\r
+\r
+    <para>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 \r
+       specific needs of your organization or consortium.</para>\r
+    \r
+       <section xml:id="requirements_server">\r
+               <info>\r
+                   <title>Server Minimum Requirements</title>\r
+               </info> \r
+              \r
+               <simplesect>\r
+                        <para>The following are the base requirements setting Evergreen up on a test server:</para>\r
+                       <itemizedlist>\r
+                               <listitem><para>An available desktop, server or virtual image</para></listitem>\r
+                               <listitem><para>512MB RAM</para></listitem>                     \r
+                               <listitem><para>Linux Operating System</para></listitem>\r
+                       </itemizedlist>\r
+                       <tip><para>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 \r
+                       to Linux, it is strongly recommended that you install Evergreen on the latest stable server edition of Debian (<ulink url="http://www.debian.org/">http://www.debian.org/</ulink>)\r
+                       or Ubuntu 10.04 Server(<ulink url="http://www.ubuntu.com/">http://www.ubuntu.com/</ulink>) since the installation instructions have been tested on these distributions. Debian and                              Ubuntu are free distributions of Linux.</para></tip>  \r
+               </simplesect> \r
+               <simplesect>\r
+                       <info>\r
+                               <title>Server Network Configurations</title>\r
+                       </info>\r
+                       <para>As apparent in the previous section, the base hardware requirements for running a functional Evergreen server are extremely minimal. It is also possible\r
+                       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 \r
+                       one Evergreen system with hundreds of libraries with millions of records and millions of users making the scalability of Evergreen almost infinite.</para>\r
+                       <para>Here are some example scenarios for a server network configuration:</para>\r
+                       <itemizedlist>\r
+                               <listitem><para>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 \r
+                               (1 machine).</para></listitem>\r
+                               <listitem><para>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 \r
+                               system by spreading services over multiple servers. It could also run  \r
+                               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, \r
+                               the operating system or the database software.</para></listitem>                        \r
+                               <listitem><para>A large library consortium with several public library systems and/or academic libraries with millions of users and items could run an Evergreen \r
+                               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 \r
+                               several library systems simultaneously.</para></listitem>\r
+                       </itemizedlist>\r
+                       <para>The key to Evergreen scalability is in the openSRF configuration files <filename>/openils/conf/opensrf.xml</filename> and \r
+                       <filename>/openils/conf/opensrf_core.xml</filename>. \r
+                       By editing these files an administrator could quickly cluster evergreen services over multiple servers, change the server running a specific service \r
+                       or change the server of the postgreSQL database.</para> \r
+\r
+                       <note><para>The default configuration of Evergreen in the installation instructions assumes a single <emphasis>localhost</emphasis> server setup. For more complex \r
+                       multi-server configurations, some server administration and database administration experience or knowledge may be required.</para></note>              \r
+               </simplesect>    \r
+       </section>\r
+       <section xml:id="requirements_staffclient">\r
+               <info>\r
+                   <title>Staff Client Requirements</title>\r
+               </info>\r
+       \r
+               <para> Staff terminals connect to the central database using the Evergreen staff client, available for download from <link xlink:href="http://www.open-ils.org/downloads.php">The Evergreen \r
+               download page</link>. The staff client must be installed on each staff workstation and requires at minimum: </para>\r
+               <itemizedlist>\r
+                       <listitem><para>Windows (XP, Vista, or 7), Mac OS X, or Linux operating system</para></listitem>\r
+                       <listitem><para>a reliable high speed internet connection</para></listitem>\r
+                       <listitem><para>512Mb of RAM</para></listitem>\r
+               </itemizedlist>\r
+               <simplesect>\r
+                       <info>\r
+                               <title>Barcode Scanners</title>   \r
+                       </info>\r
+                               <para>Evergreen will work with virtually any barcode scanner – if it worked with your legacy system it should work on Evergreen.</para>\r
+               </simplesect>\r
+               <simplesect>\r
+                       <info>\r
+                               <title>Printers</title>\r
+                       </info>\r
+                       <para>Evergreen can use any printer configured for your terminal to print receipts, check-out slips, holds\r
+                       lists, etc. The single exception is spine label printing, which is still under development. Evergreen\r
+                       currently formats spine labels for output to a label roll printer. If you do not have a roll printer\r
+                        manual formatting may be required.  For more on configuring receipt printers, see <link linkend="lsa-printer">Printer Settings</link>.</para>    \r
+               </simplesect>    \r
+       </section>\r
+</chapter>\r
index a2abbb0..6a44d49 100644 (file)
@@ -1968,8 +1968,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati
                                <step><para>Check the check box(es) next to the circulation modifiers(s) you wish to \r
                                delete.</para></step>\r
                                <step><para>Click <guibutton>Delete Selected</guibutton> near the top of the page.\r
                                <step><para>Check the check box(es) next to the circulation modifiers(s) you wish to \r
                                delete.</para></step>\r
                                <step><para>Click <guibutton>Delete Selected</guibutton> near the top of the page.\r
-                               <warning><para>The selected circulation modifiers will be deleted without a \r
-                               verification alert.</para></warning>\r
+                               <caution><para>The selected circulation modifiers will be deleted without a \r
+                               verification alert.</para></caution>\r
                                </para></step>\r
                        </procedure>\r
                        <procedure>\r
                                </para></step>\r
                        </procedure>\r
                        <procedure>\r
index 85b7439..2824604 100755 (executable)
@@ -57,6 +57,7 @@
                        <title>Administration</title>\r
                </info>\r
                <xi:include href="admin/admin-intro.xml"/>\r
                        <title>Administration</title>\r
                </info>\r
                <xi:include href="admin/admin-intro.xml"/>\r
+               <xi:include href="admin/requirements-configuration.xml"/>\r
                <xi:include href="admin/serveradministration.xml"/>\r
                <xi:include href="admin/AdminMisc.xml"/>\r
                <xi:include href="admin/admin-lsa.xml"/>\r
                <xi:include href="admin/serveradministration.xml"/>\r
                <xi:include href="admin/AdminMisc.xml"/>\r
                <xi:include href="admin/admin-lsa.xml"/>\r