From e522afb662de3efd0320060491ce29aaec9c5fb3 Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Fri, 27 Aug 2010 17:36:15 -0400 Subject: [PATCH] fix some broken s; expand the section 'Starting Evergreen'; --- 1.6/admin/ServersideInstallation.xml | 169 ++++++++++++++++++++------- 1 file changed, 128 insertions(+), 41 deletions(-) diff --git a/1.6/admin/ServersideInstallation.xml b/1.6/admin/ServersideInstallation.xml index b0408bf3be..ba37172a73 100644 --- a/1.6/admin/ServersideInstallation.xml +++ b/1.6/admin/ServersideInstallation.xml @@ -17,52 +17,59 @@ The system requirements for running Evergreen really depend on what you want to do with it. For just evaluating the software, or for a very small library (for example, 1 circulation station, a few thousand items, and infrequent online catalog use), any modern desktop or laptop made within the last few years capable of running Linux, FreeBSD, etc. should suffice. We recommend at least 512mb of RAM. - From Dan Scott on [http://list.georgialibraries.org/pipermail/open-ils-general/2007-July/000316.html|OPEN-ILS-GENERAL]: - > On 8/11/07, lan ye <lye at mail.slcl.org> wrote: - > > We've been researching the Evergreen Open Source Library system, and would - > like to have a list of hardware requirements for the installation of a small - > test server. To keep things within a small budget, I would like to just use - > an ordinary PC. Could you send some information to us? + From Dan Scott on [http://list.georgialibraries.org/pipermail/ + open-ils-general/2007-July/000316.html|OPEN-ILS-GENERAL]: + On 8/11/07, lan ye <lye at mail.slcl.org> wrote: + > We've been researching the Evergreen Open Source Library system, + > and would like to have a list of hardware requirements for the + > installation of a small test server. To keep things within a + > small budget, I would like to just use an ordinary PC. Could you + > send some information to us? For system requirements, it depends on how extensive you want your tests to be. Evergreen and all of the pieces it depends on - (PostgreSQL, Apache, Ejabberd) run happily in a VMWare image allocated - 512MB of RAM on my laptop with just the Project Gutenberg e-books - loaded, and that's enough to evaluate the OPAC interface / try out the - staff client / make some local changes and generally experiment. But - I'm not going to load one million bib records into that system and - expect it to perform. So, probably any hardware you have lying around - would be adequate for a small test server. + (PostgreSQL, Apache, Ejabberd) run happily in a VMWare image + allocated 512MB of RAM on my laptop with just the Project + Gutenberg e-books loaded, and that's enough to evaluate the OPAC + interface / try out the staff client / make some local changes and + generally experiment. But I'm not going to load one million bib + records into that system and expect it to perform. So, probably + any hardware you have lying around would be adequate for a small + test server. - > > It looks like Evergreen has been successfully installed on two Linux - > systems: Gentoo and Ubuntu. Which one is the best for us to test using - > what's already in place at other libraries? Are there any differences / - > Advantages in functionality between Gentoo and Ubuntu? + > It looks like Evergreen has been successfully installed on two + > Linux systems: Gentoo and Ubuntu. Which one is the best for us + > to test using what's already in place at other libraries? Are + > there any differences / Advantages in functionality between + > Gentoo and Ubuntu? - As John said, GPLS is running on Debian, and that's the only Evergreen - system that is in production at the moment. However, the documentation - for installing on Debian is a bit scattered right now. The developers - themselves used Gentoo originally, and that's what I'm using at the - moment & have documented in the wiki; the install process on Ubuntu is - very thoroughly documented and Ubuntu is reasonably close to Debian. - See http://open-ils.org/dokuwiki/doku.php?id=server_installation for + As John said, GPLS is running on Debian, and that's the only + Evergreen system that is in production at the moment. However, the + documentation for installing on Debian is a bit scattered right + now. The developers themselves used Gentoo originally, and that's + what I'm using at the moment & have documented in the wiki; + the install process on Ubuntu is very thoroughly documented and + Ubuntu is reasonably close to Debian. See + http://open-ils.org/dokuwiki/doku.php?id=server_installation for the list of install instructions for various distributions. - As for advantages / disadvantages of particular distributions, that's - a religious war that I don't want to step into... We'll try to help - you out no matter what distribution you choose; just please choose a - current release :) + As for advantages / disadvantages of particular distributions, + that's a religious war that I don't want to step into... We'll try + to help you out no matter what distribution you choose; just + please choose a current release :) -- Dan Scott Laurentian University - And from James Fournie in that same [http://list.georgialibraries.org/pipermail/open-ils-general/2007-July/000317.html|thread]: - We are running a test Ubuntu server on a ~1ghz Celeron PC with 512mb RAM. - It seems to be ok handling the Gutenberg samples, and our collection of - about 8000 records. We did have serious problems using anything less than - 512mb RAM. Also, I tried Evergreen on a K6 II 350, but it wasn't pretty. + And from James Fournie in that same [http://list.georgialibraries.org/ + pipermail/open-ils-general/2007-July/000317.html|thread]: + We are running a test Ubuntu server on a ~1ghz Celeron PC with + 512mb RAM. It seems to be ok handling the Gutenberg samples, and + our collection of about 8000 records. We did have serious problems + using anything less than 512mb RAM. Also, I tried Evergreen on a + K6 II 350, but it wasn't pretty. James Fournie Digitization Librarian @@ -141,7 +148,7 @@ To become the root user, issue the command: sudo su - root. To switch from the root user to a different user, issue a command like: su - USERNAME. For example, to switch from the root user to the opensrf user, issue this command: su - opensrf. Once you have become a non-root user, to become the root user again, simply issue the exit command.
Install the latest version of OpenSRF - For further information on installing the Open Service Request Framework (OpenSRF), see the section Installing OpenSRF. + For further information on installing the Open Service Request Framework (OpenSRF), see the section Installing OpenSRF. Follow the steps outlined in that section, then run the specified test(s) to ensure that OpenSRF is properly installed before continuing with any further Evergreen installation steps. The Evergreen application depends on properly installation of OpenSRF. If OpenSRF does not work correctly, Evergreen will not work properly either.
@@ -185,7 +192,7 @@
(OPTIONAL) Install the PostgreSQL Server Since the PostgreSQL server is usually a standalone server in multi-server production systems, the prerequisite installer Makefile in the previous step does not automatically install PostgreSQL. If your PostgreSQL server is on a different system, just skip this step. - For further information on installing PostgreSQL, see the section Installing PostgreSQL. + For further information on installing PostgreSQL, see the section Installing PostgreSQL. If your PostgreSQL server will be on the same system as your Evergreen software, then as the root user install the required PostgreSQL server packages:
Commands to install the PostgreSQL server @@ -491,7 +498,8 @@ Sample of configuration file /openils/conf/srfsh.xml.example <?xml version="1.0"?> - <!-- This file follows the standard bootstrap config file layout found in opensrf_core.xml --> + <!-- This file follows the standard bootstrap config file layout --> + <!-- found in opensrf_core.xml --> <srfsh> <router_name>router</router_name> <domain>private.localhost</domain> @@ -507,7 +515,7 @@
Modify the OpenSRF Environment - As the opensrf user, change the permissions of files to executable in the directory /openils/var/cgi-bin, then add a Perl environmental variable to the shell configuration file ~/.bashrc for the user opensrf. + As the opensrf user, change the file permissions the directory /openils/var/cgi-bin to executable, then modify the shell configuration file ~/.bashrc of that user by adding a Perl environmental variable. Note: in a multi-server environment, you must add the modifications to ~/.bashrc at the top of the file before the line [ -z "$PS1" ] && return. This will allow headless (scripted) logins to load the correct environment.
Modify the OpenSRF environment @@ -524,11 +532,90 @@
(OPTIONAL) Configuration for Other Languages - Load translations such as Armenian (hy-AM), Canadian French (fr-CA), and others into the database to complete the translations available in the OPAC and staff client. See [[server_installation:adding_localizations|these instructions]] for details. + Load translations such as Armenian (hy-AM), Canadian French (fr-CA), and others into the database to complete the translations available in the OPAC and staff client. See the section Adding Language Localization for details.
- Starting the Server + Starting Evergreen + + + As the root user, start the memcached and ejabberd services (if they aren't already running): +
+ Start some services + + $ sudo su - root + $ /etc/init.d/ejabberd start + $ /etc/init.d/memcached start + +
+ + + As the opensrf user, start Evergreen. + Use the flag -l to force Evergreen to use localhost (your current system) as the hostname. +
+ Start Evergreen + + $ sudo su - opensrf + + # ensure you have the needed path + $ export PATH=$PATH:/openils/bin + + # start the server; + # use "-l" to force hostname to be "localhost" + $ osrf_ctl.sh -l -a start_all + +
+ + + Note: You can also start Evergreen without the -l flag, but it must know the fully qualified domain name for the system on which it will execute. That hostname would have been specified in the configuration file opensrf.xml, which you configured in a previous step. + [[ explanation needed for configuring opensrf.xml ]] + Execute the following command to determine the fully qualified domain name of your system: +
+ (OPTIONAL) Determine the fully qualified domain name + + $ perl -e 'use Net::Domain qw(hostfqdn); print hostfqdn()."\n"' + +
+ + + When you attempt to start Evergreen, if you receive an error message similar to osrf_ctl.sh: command not found, then your environment variable PATH does not include the directory /openils/bin. As the opensrf user, edit the configuration file /home/opensrf/.bashrc and add the following line: export PATH=$PATH:/openils/bin + + When you attempt to start Evergreen, if you receive an error message similar to Can't locate OpenSRF/System.pm in @INC ... BEGIN failed--compilation aborted, then your environment variable PERL5LIB does not include the directory /openils/lib/perl5. As the opensrf user, edit the configuration file /home/opensrf/.bashrc and add the following line: export PERL5LIB=$PERL5LIB:/openils/lib/perl5 + + + + + As the opensrf user, generate the Web files needed by the staff client and catalogue, and also update the organization unit proximity. + You need to do this the first time you start Evergreen, and after that each time you change the library hierarchy in ''config.cgi'': +
+ Generate web files + + $ sudo su - opensrf + $ cd /openils/bin + $ ./autogen.sh -c /openils/conf/opensrf_core.xml -u + Updating Evergreen organization tree and IDL using '/openils/conf/opensrf_core.xml' + + Updating fieldmapper + Exception: OpenSRF::EX::Session 2010-04-16T06:31:38 OpenSRF::Utils::SettingsClient /usr/local/share/perl/5.10.0/OpenSRF/Utils/SettingsClient.pm:103 Session Error: router@private.localhost/opensrf.settings IS NOT CONNECTED TO THE NETWORK!!! + + + [[ TEST THIS! ]] +
+ + + As the root user, restart the Apache Web server: + +
+ Generate web files + + $ sudo su - root + $ /etc/init.d/apache2 restart + +
+ If the Apache Web server was running when you started the OpenSRF services, you might not be able to successfully log in to the OPAC or staff client until the Apache Web server is restarted. + + +
Testing Connections to the Server @@ -588,8 +675,8 @@ Building the Staff Client [[ Building the Staff Client ]]
-
- Language Localization +
+ Adding Language Localization [[ Adding Localized Languages to the Database ]]
-- 2.43.2