From: Steve Sheppard Date: Mon, 30 Aug 2010 16:53:49 +0000 (-0400) Subject: reorganize ordering of some chapters; X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=37097b66617835dc29816c4e4af7f55a49ccdde5;p=Evergreen-DocBook.git reorganize ordering of some chapters; general cleanup; add further [[ CONTENT ]] sections as needed; --- diff --git a/1.6/admin/ServersideInstallation.xml b/1.6/admin/ServersideInstallation.xml index 2517428..9f41bf6 100644 --- a/1.6/admin/ServersideInstallation.xml +++ b/1.6/admin/ServersideInstallation.xml @@ -3,102 +3,20 @@ Server-side Installation of Evergreen Software - This section describes installation of the Evergreen server-side software. Installation, configuration, testing and verification of the Evergreen server-side software is straightforward if you follow some simple directions. Installation of the Evergreen Staff Client software is handled in the section "Installing the Evergreen Staff Client" . + This section describes installation of the Evergreen server-side software and its associated components. Installation, configuration, testing and verification of the software is straightforward if you follow some simple directions.
Overview - A bare-minimum system Evergreen system requires only a single Server and a single Staff Client, both residing on a single server machine. In fact, that is a reasonable architecture for simple experiments or as a proof of concept in a conference-room pilot. But typical real-world systems will probably consist of at least one or two Evergreen servers plus multiple Staff Clients. - Another simple system may require only that you install one or more instances of the Staff Client software. For instance, if your consortium already provides the Evergreen server software or if you are using the hosted version provided by Equinox, you do not need to install the Evergreen server-side software at all. - Current versions of Evergreen software run as native applications on any of several well-known Linux distributions (e.g., Ubuntu and Debian). It does not currently run as a native application on the Windows operating system (e.g., WindowsXP, WindowsXP Professional, Windows7), but the software can still be installed and run on Windows via a so-called virtualized Unix-guest Operating System (using, for example, VirtualBox or VMware to emulate a Linux environment). More information on running Evergreen in virtualized environments can be found in the section "Installing Evergreen in Virtualized Unix Environments". -
-
- System Requirements - This section describes various requirements of the hardware and software environment that must be fulfilled to support a successful Evergreen installation. For a description of the installation process itself and for links to further instructions please review the section "The Installation Process" . - 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. - [[ ADD OTHER HARDWARE AND SOFTWARE REQUIREMENTS ]] - - - 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. - - > 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 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 :) - - -- - 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. - - James Fournie - Digitization Librarian - Union of B.C. Indian Chiefs - + Installing, configuring and testing the Evergreen server-side software is straightforward with the current stable software release. See the section "Installing Evergreen On Ubuntu or Debian" for instructions tailored to installing on some particular distributions of the Linux operating system. Earlier software distributions are described in the section "Installing Previous Versions of Evergreen" . + Current versions of the Evergreen server-side software run as native applications on any of several well-known Linux distributions (e.g., Ubuntu and Debian). It does not currently run as a native application on the Windows operating system (e.g., WindowsXP, WindowsXP Professional, Windows7), but the software can still be installed and run on Windows via a so-called virtualized Unix-guest Operating System (using, for example, VirtualBox, or VMware, or VirtualPC to emulate a Linux environment). It can also be installed and run on other Linux systems via virtualized environments (using, for example, VirtualBox or VMware). More information on virtualized environments can be found in the section "Installing Evergreen in Virtualized Unix Environments". + Installation of some sub-components of the Evergreen server-side software is mentioned only in abbreviated form in this section. More detailed information is available in the accompanying sections: + "OpenSRF" , + "PostgreSQL Database" , + "Apache" and + "memcached Servers" . -
-
- Example System Architectures - This sections describes examples of some working Evergreen system architectures, including both server-side software and Staff Client software. -
- PINES - In order to provide load balancing and high-availability at the OPAC and Staff Client level, PINES has implemented a Linux Virtual Server environment with five independent mini-clusters. This allows live updates of the entire system with no perceived downtime or interruption in service. - [[ ADD FURTHER INFORMATION ON PINES ]] -
-
- Sitka - [[ ADD FURTHER INFORMATION ON SITKA ]] -
-
- Other working systems - [[ ADD FURTHER INFORMATION ON OTHER WORKING SYSTEMS ]] -
-
-
- The Installation Process - Installing, configuring and testing the Evergreen server-side software is straightforward with the current stable software release. Earlier software distributions are also available. In the following sections you will find instructions tailored to specific distributions. + Installation of the Evergreen Staff Client software is handled in the section "Installing the Evergreen Staff Client" .
Current Stable Software Release The current stable release of Evergreen is version 1.6.0.7. Instructions for installing, configuring and testing that version on the Ubuntu or Debian Linux systems are found in the section "Installing Evergreen on Ubuntu or Debian" . @@ -108,459 +26,543 @@
Previous Software Releases - Earlier releases of Evergreen are also available. Instructions for installing, configuring and testing earlier versions are found in the section Installing Previous Versions of Evergreen . - The next most recent previous release of Evergreen is version 1.4.0.6. Instructions for installing, configuring and testing that version are found in the section Installing Evergreen 1.4.0.6 on Ubuntu or Debian . + Earlier releases of Evergreen are also available. Instructions for installing, configuring and testing earlier versions are found in the section "Installing Previous Versions of Evergreen" . + The next most recent previous release of Evergreen is version 1.4.0.6. Instructions for installing, configuring and testing that version are found in the section "Installing Evergreen 1.4.0.6 on Ubuntu or Debian" . - The accompanying previous release of OpenSRF is version 1.0.x. Instructions for installing, configuring and testing that version are found in the section Installing OpenSRF 1.0.x . + The accompanying previous release of OpenSRF is version 1.0.x. Instructions for installing, configuring and testing that version are found in the section "Installing OpenSRF 1.0.x" .
+
+ System Requirements + This section describes various requirements of the hardware and software environment that must be fulfilled to support a successful Evergreen installation. 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. + [[ ADD FURTHER CONTENT ON HARDWARE AND SOFTWARE REQUIREMENTS ]] + + + 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. + + > 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 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 :) + + -- + 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. + + James Fournie + Digitization Librarian + Union of B.C. Indian Chiefs + + +
+
+ Example System Architectures + This sections describes examples of some working Evergreen system architectures, including both server-side software and Staff Client software. + A bare-minimum system Evergreen system requires only a single Server and a single Staff Client, both residing on a single server machine. In fact, that is a reasonable architecture for simple experiments or as a proof of concept in a conference-room pilot. But typical real-world systems will probably consist of at least one or two Evergreen servers plus multiple Staff Clients. + Another simple system may require only that you install one or more instances of the Staff Client software. For instance, if your consortium already provides the Evergreen server software or if you are using the hosted version provided by Equinox, you do not need to install the Evergreen server-side software at all. +
+ PINES + In order to provide load balancing and high-availability at the OPAC and Staff Client level, PINES has implemented a Linux Virtual Server environment with five independent mini-clusters. This allows live updates of the entire system with no perceived downtime or interruption in service. + [[ ADD FURTHER INFORMATION ON PINES ]] +
+
+ Sitka + [[ ADD FURTHER INFORMATION ON SITKA ]] +
+
+ Other working systems + [[ ADD FURTHER INFORMATION ON OTHER WORKING SYSTEMS ]] +
+
Installing Evergreen On Ubuntu or Debian This section outlines the installation process for the latest stable version of Evergreen (1.6.0.7). + In this section you will download, unpack, install, configure and test the Evergreen system, including the Evergreen server and the PostgreSQL database system. You will make several configuration changes and adjustments to the software, including updates to configure the system for your own locale, and some updates needed to work around a few known issues. + As far as possible, perform the following steps in the order they are given since the success of many steps relies on the successful completion of earlier steps. You should make backup copies of files and environments when you are instructed to do so. In the event of installation problems those copies can allow you to back out of a step gracefully and resume the installation from a known state. + Of course, after you successfully complete and test the entire Evergreen installation you should take a final snapshot backup of your system(s). This can be the first in the series of regularly scheduled system backups that you should probably also begin. - The following steps have been tested on the x86 (32-bit) and x86-64 (64-bit) architectures. There may be differences between the Desktop and Server editions of Ubuntu. These instructions assume the Server edition. - In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. - To become the root user, issue the command: 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. + + The following steps have been tested on the x86 (32-bit) and x86-64 (64-bit) architectures. There may be differences between the Desktop and Server editions of Ubuntu. These instructions assume the Server edition. + In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. + To become the root user, issue the command: 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. + +
+ Installing OpenSRF + Evergreen software is integrated with and depends on the Open Service Request Framework (OpenSRF) software system. For further information on installing, configuring and testing OpenSRF, see the section "Installing OpenSRF" . + Follow the steps outlined in that section and run the specified tests to ensure that OpenSRF is properly installed and configured. Do not continue with any further Evergreen installation steps until you have verified that OpenSRF has been successfully installed. +
- Downloading and Building Evergreen - In this section you will download, unpack, install, configure and test the Evergreen system, including the Evergreen server and the PostgreSQL database system. You will make several configuration changes and adjustments to the software, including updates to configure the system for your own locale, and some updates needed to work around a few known issues. - As far as possible, perform the following steps in the order they are given, since the success of many steps relies on the successful completion of earlier steps. You should make backup copies of files and environments when you are instructed to do so. In the event of installation problems those copies can allow you to back out of a step gracefully and resume the installation from a known state. - Of course, after you successfully complete and test the entire Evergreen installation you should take a final snapshot backup of your system(s). This can be the first in the series of regularly scheduled system backups that you should probably also begin. -
- Installing OpenSRF - Evergreen software is integrated with and depends on the Open Service Request Framework (OpenSRF) software system. For further information on installing, configuring and testing OpenSRF, see the section "Installing OpenSRF" . - Follow the steps outlined in that section and run the specified tests to ensure that OpenSRF is properly installed and configured. Do not continue with any further Evergreen installation steps until you have verified that OpenSRF has been successfully installed. -
-
- Download and Unpack Latest Evergreen Version - As the opensrf user, download and extract the latest version of Evergreen. The latest version can be found here: - [[ VERIFY LOCATION OF LATEST VERSION OF EVERGREEN ]] -
- Commands to download/extract Evergreen - - $ su - opensrf - $ wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.6.0.7.tar.gz - $ tar zxf Evergreen-ILS-1.6.0.7.tar.gz - -
-
-
- Install Prerequisites to Build Evergreen - In this step you will install and configure a set of prerequisites used to build the Evergreen server-side software. In a following step you will actually build the software. - As the root user, enter the commands show below to build the prerequisites from the software distribution that you just downloaded and unpacked. Remember to replace [distribution] in the following example with the keyword that corresponds to the actual Linux distribution listed here: - - debian-lenny for Debian Lenny (5.0), the most recent version - debian-etch for Debian Etch (4.0) - - ubuntu-karmic for Ubuntu Lucid (10.04) [same as for Karmic] - ubuntu-karmic for Ubuntu Karmic (9.10) - ubuntu-intrepid for Ubuntu Intrepid (8.10) - ubuntu-hardy for Ubuntu Hardy (8.04) - ubuntu-gutsy for Ubuntu Gutsy (7.10) - - gentoo generic for Gentoo versions - centos generic for Centos versions - - [[ ADD INFO FOR OTHER LINUX DISTRIBUTIONS ]] - -
- Commands to install prerequisites for Evergreen - - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make -f Open-ILS/src/extras/Makefile.install [distribution] - -
-
-
- (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" . - 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 - - $ su - root + Download and Unpack Latest Evergreen Version + As the opensrf user, download and extract the latest version of Evergreen. The latest version can be found here: + [[ VERIFY LOCATION OF LATEST VERSION OF EVERGREEN ]] +
+ Commands to download/extract Evergreen + + $ su - opensrf + $ wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.6.0.7.tar.gz + $ tar zxf Evergreen-ILS-1.6.0.7.tar.gz + +
+
+
+ Install Prerequisites to Build Evergreen + In this step you will install and configure a set of prerequisites used to build the Evergreen server-side software. In a following step you will actually build the software using the make utility. + As the root user, enter the commands show below in Figure 1.3 to build the prerequisites from the software distribution that you just downloaded and unpacked. Remember to replace [distribution] in the example with the keyword corresponding to the actual Linux distribution listed here: +
Keywords used with "make" + debian-lenny for Debian Lenny (5.0), the most recent version + debian-etch for Debian Etch (4.0) - # Debian Lenny and Ubuntu Hardy (8.04) - $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_83 + ubuntu-karmic for Ubuntu Lucid (10.04) [same as for Karmic] + ubuntu-karmic for Ubuntu Karmic (9.10) + ubuntu-intrepid for Ubuntu Intrepid (8.10) + ubuntu-hardy for Ubuntu Hardy (8.04) + ubuntu-gutsy for Ubuntu Gutsy (7.10) - # Ubuntu Karmic (9.10) and Ubuntu Lucid (10.04) - $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_84 - -
- - - PostgreSQL 8.1 is deprecated and will become unsupported in a future release, though existing installations upgrading from Evergreen 1.4 or before will work fine. However, consider upgrading your Postgres soon! - - - [[ VERIFY: IS THIS STILL TRUE? ]] - [[ ADD INFO ON HOW TO DETERMINE WHICH VERSION OF POSTGRESQL YOU HAVE ]] -
-
- (OPTIONAL) Install Perl Modules on PostgreSQL Server - If PostgreSQL is running on the same system as your Evergreen software, then the Perl modules will automatically be available. Just skip this step. - Otherwise, if your PostgreSQL server is running on another system, then as the root user install the following Perl modules on that system: -
- Commands to install Perl modules - - # ensure the gcc compiler is installed - $ su - root - $ aptitude install gcc + gentoo generic for Gentoo versions + centos generic for Centos versions - # install the Perl modules - $ perl -MCPAN -e shell - cpan> install JSON::XS - cpan> install MARC::Record - cpan> install MARC::File::XML - -
- [[ ADD INFO ON HOW TO INSTALL THE PERL MODULES ]] - [[ ADD INFO ON HOW TO VERIFY THAT THE PERL MODULES ARE INSTALLED ]] -
-
- Add Additional Library Paths on Evergreen System - As the root user, you must update the system dynamic library path to ensure the system will recognize the newly installed libraries. Do this by creating a new file named /etc/ld.so.conf.d/eg.conf containing the two paths, then run the command ldconfig to automatically read the file and modify the dynamic library path: -
- Commands to modify system dynamic library path - - $ su - root - $ cat > /etc/ld.so.conf.d/eg.conf << ENDOFFILE - /usr/local/lib - /usr/local/lib/dbd - ENDOFFILE - $ ldconfig - -
-
-
- (OPTIONAL) Restart the PostgreSQL Service - If PostgreSQL is running on the same system as the rest of Evergreen, as the root user you must restart the PostgreSQL service to avoid a problem where the library plperl.so cannot be found. If your PostgreSQL server is running on another system, just skip this step. - [[ ADD INFO ON OTHER VERSIONS OF POSTGRESQL ]] -
- Commands to restart PostgreSQL service - - $ su - root - $ /etc/init.d/postgresql-8.3 restart - -
-
-
- Configure and Compile Evergreen Sources - As the opensrf user, configure and compile the software from the prerequisites that were set up in previous steps: -
- Commands to configure and compile Evergreen - - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ ./configure --prefix=/openils --sysconfdir=/openils/conf - $ make - -
-
-
- Link and Install Evergreen - As the root user, link and install the compiled code. In the commands below, remember to set the variable STAFF_CLIENT_BUILD_ID to match the version of the Staff Client you will use to connect to the Evergreen server. Finally, create a symbolic link named server in /openils/var/web/xul to the /server subdirectory of your Staff Client build: -
- Commands to link and install Evergreen - - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_6 install - $ cd /openils/var/web/xul - $ ln -sf rel_1_6_0_7/server server - -
-
-
- Copy the OpenSRF Configuration Files - As the root user, copy the example OpenSRF configuration files into place. This will replace the OpenSRF configuration files that you set up while installing and testing OpenSRF. You should also create backup copies of the old files for troubleshooting purposes. Finally, change the ownership on the installed files to the user opensrf: -
- Commands to copy OpenSRF configuration files - - $ su - root - $ cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml - $ cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml - $ cp /openils/conf/oils_web.xml.example /openils/conf/oils_web.xml - $ chown -R opensrf:opensrf /openils/ - -
-
-
- Create and configure PostgreSQL Database - As the postgres user on your PostgreSQL server, create the Evergreen database. - Remember to adjust the path for the contrib repository to match your PostgreSQL server layout. For example, if you built PostgreSQL from source following the cheat sheet, the contrib directory will be located here: /usr/local/share/contrib . If you installed the PostgreSQL 8.3 server packages on Ubuntu 8.04, the directory will be located here: /usr/share/postgresql/8.3/contrib/ . - - - - Create and configure the database - - As the postgres user on the PostgreSQL system create the PostgreSQL database, then set some internal paths: -
- Commands to create database and adjust the path - - # create the database - $ su - postgres - $ createdb -E UNICODE evergreen - $ createlang plperl evergreen - $ createlang plperlu evergreen - $ createlang plpgsql evergreen - - # adjust the paths - $ psql -f /usr/share/postgresql/8.3/contrib/tablefunc.sql evergreen - $ psql -f /usr/share/postgresql/8.3/contrib/tsearch2.sql evergreen - $ psql -f /usr/share/postgresql/8.3/contrib/pgxml.sql evergreen - -
- - - Create new Evergreen superuser - As the postgres user on the PostgreSQL system, create the new user evergreen : -
- Commands to create the 'evergreen' user - - # create superuser 'evergreen' and set the password - $ su - postgres - $ createuser -P -s evergreen - Enter password for new role: mynewpassword - Enter it again: mynewpassword - -
- - -
-
- Create Database Schema - As the root user, create the database schema and configure your system with the corresponding database authentication details for the database user 'evergreen' that you created in the previous step. - Enter the commands and replace [HOSTNAME], [PORT], [USER], [PASSWORD] and [DATABASENAME] with appropriate values. - On most systems [HOSTNAME] will be localhost, and [PORT] will be 5432. -
- Commands to create Evergreen database schema - - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ - --service all --create-schema --create-bootstrap --create-offline \ - --hostname [HOSTNAME] --port [PORT] \ - --user [USER] --password [PASSWORD] --database [DATABASENAME] - -
- + [[ ADD INFO FOR OTHER LINUX DISTRIBUTIONS ]] + +
+ Commands to install prerequisites for Evergreen + + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make -f Open-ILS/src/extras/Makefile.install [distribution] + +
+
+
+ (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" . + 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 + + $ su - root + + # Debian Lenny and Ubuntu Hardy (8.04) + $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_83 + + # Ubuntu Karmic (9.10) and Ubuntu Lucid (10.04) + $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_84 + +
+ + + PostgreSQL 8.1 is deprecated and will become unsupported in a future release, though existing installations upgrading from Evergreen 1.4 or before will work fine. However, consider upgrading your Postgres soon! + + + [[ VERIFY: IS THIS STILL TRUE? ]] + [[ ADD INFO ON HOW TO DETERMINE WHICH VERSION OF POSTGRESQL YOU HAVE ]] +
+
+ (OPTIONAL) Install Perl Modules on PostgreSQL Server + If PostgreSQL is running on the same system as your Evergreen software, then the Perl modules will automatically be available. Just skip this step. + Otherwise, if your PostgreSQL server is running on another system, then as the root user install the following Perl modules on that system: +
+ Commands to install Perl modules + + # ensure the gcc compiler is installed + $ su - root + $ aptitude install gcc + + # install the Perl modules + $ perl -MCPAN -e shell + cpan> install JSON::XS + cpan> install MARC::Record + cpan> install MARC::File::XML + +
+ [[ ADD INFO ON HOW TO INSTALL THE PERL MODULES ]] + [[ ADD INFO ON HOW TO VERIFY THAT THE PERL MODULES ARE INSTALLED ]] +
+
+ Add Additional Library Paths on Evergreen System + As the root user, you must update the system dynamic library path to ensure the system will recognize the newly installed libraries. Do this by creating a new file named /etc/ld.so.conf.d/eg.conf containing the two paths, then run the command ldconfig to automatically read the file and modify the dynamic library path: +
+ Commands to modify system dynamic library path + + $ su - root + $ cat > /etc/ld.so.conf.d/eg.conf << ENDOFFILE + /usr/local/lib + /usr/local/lib/dbd + ENDOFFILE + $ ldconfig + +
+
+
+ (OPTIONAL) Restart the PostgreSQL Service + If PostgreSQL is running on the same system as the rest of Evergreen, as the root user you must restart the PostgreSQL service to avoid a problem where the library plperl.so cannot be found. If your PostgreSQL server is running on another system, just skip this step. + [[ ADD INFO ON OTHER VERSIONS OF POSTGRESQL ]] +
+ Commands to restart PostgreSQL service + + $ su - root + $ /etc/init.d/postgresql-8.3 restart + +
+
+
+ Configure and Compile Evergreen Sources + As the opensrf user, configure and compile the software from the prerequisites that were set up in previous steps: +
+ Commands to configure and compile Evergreen + + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ ./configure --prefix=/openils --sysconfdir=/openils/conf + $ make + +
+
+
+ Link and Install Evergreen + As the root user, link and install the compiled code. In the commands below, remember to set the variable STAFF_CLIENT_BUILD_ID to match the version of the Staff Client you will use to connect to the Evergreen server. Finally, create a symbolic link named server in /openils/var/web/xul to the /server subdirectory of your Staff Client build: +
+ Commands to link and install Evergreen + + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_6 install + $ cd /openils/var/web/xul + $ ln -sf rel_1_6_0_7/server server + +
+
+
+ Copy the OpenSRF Configuration Files + As the root user, copy the example OpenSRF configuration files into place. This will replace the OpenSRF configuration files that you set up while installing and testing OpenSRF. You should also create backup copies of the old files for troubleshooting purposes. Finally, change the ownership on the installed files to the user opensrf: +
+ Commands to copy OpenSRF configuration files + + $ su - root + $ cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml + $ cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml + $ cp /openils/conf/oils_web.xml.example /openils/conf/oils_web.xml + $ chown -R opensrf:opensrf /openils/ + +
+
+
+ Create and configure PostgreSQL Database + As the postgres user on your PostgreSQL server, create the Evergreen database. + Remember to adjust the path for the contrib repository to match your PostgreSQL server layout. For example, if you built PostgreSQL from source following the cheat sheet, the contrib directory will be located here: /usr/local/share/contrib . If you installed the PostgreSQL 8.3 server packages on Ubuntu 8.04, the directory will be located here: /usr/share/postgresql/8.3/contrib/ . + + - If you are entering the above command on a single line, do not include the \ (backslash) characters. If you are using the bash shell, these should only be used at the end of a line at a bash prompt to indicate that the command is continued on the next line. + Create and configure the database - -
-
- Configure the Apache Server - As the root user, configure the Apache server and copy several new configuration files to the Apache server directories: -
- Commands to configure the Apache server - - # configure the Apache server - $ su - root - $ a2enmod ssl # enable mod_ssl - $ a2enmod rewrite # enable mod_rewrite - $ a2enmod expires # enable mod_expires - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + As the postgres user on the PostgreSQL system create the PostgreSQL database, then set some internal paths: +
+ Commands to create database and adjust the path + + # create the database + $ su - postgres + $ createdb -E UNICODE evergreen + $ createlang plperl evergreen + $ createlang plperlu evergreen + $ createlang plpgsql evergreen + + # adjust the paths + $ psql -f /usr/share/postgresql/8.3/contrib/tablefunc.sql evergreen + $ psql -f /usr/share/postgresql/8.3/contrib/tsearch2.sql evergreen + $ psql -f /usr/share/postgresql/8.3/contrib/pgxml.sql evergreen + +
+ + + Create new Evergreen superuser + As the postgres user on the PostgreSQL system, create the new user evergreen : +
+ Commands to create the 'evergreen' user + + # create superuser 'evergreen' and set the password + $ su - postgres + $ createuser -P -s evergreen + Enter password for new role: mynewpassword + Enter it again: mynewpassword + +
+ + +
+
+ Create Database Schema + As the root user, create the database schema and configure your system with the corresponding database authentication details for the database user 'evergreen' that you created in the previous step. + Enter the commands and replace [HOSTNAME], [PORT], [USER], [PASSWORD] and [DATABASENAME] with appropriate values. + On most systems [HOSTNAME] will be localhost, and [PORT] will be 5432. +
+ Commands to create Evergreen database schema + + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ + --service all --create-schema --create-bootstrap --create-offline \ + --hostname [HOSTNAME] --port [PORT] \ + --user [USER] --password [PASSWORD] --database [DATABASENAME] + +
+ + + If you are entering the above command on a single line, do not include the \ (backslash) characters. If you are using the bash shell, these should only be used at the end of a line at a bash prompt to indicate that the command is continued on the next line. + + +
+
+ Configure the Apache Server + As the root user, configure the Apache server and copy several new configuration files to the Apache server directories: +
+ Commands to configure the Apache server + + # configure the Apache server + $ su - root + $ a2enmod ssl # enable mod_ssl + $ a2enmod rewrite # enable mod_rewrite + $ a2enmod expires # enable mod_expires + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - # copy files - $ cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/ - $ cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/ - $ cp Open-ILS/examples/apache/startup.pl /etc/apache2/ - -
-
-
- Create a Security Certificate (SSL Key) - Use the command openssl to create a new SSL key for your Apache server. For a public production server you should configure or purchase a signed SSL certificate, but for now you can just use a self-signed certificate and accept the warnings in the Staff Client and browser during testing and development: -
- Commands to create an SSL key - - $ mkdir /etc/apache2/ssl - $ cd /etc/apache2/ssl - $ openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key - -
- + # copy files + $ cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/ + $ cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/ + $ cp Open-ILS/examples/apache/startup.pl /etc/apache2/ + + +
+
+ Create a Security Certificate (SSL Key) + Use the command openssl to create a new SSL key for your Apache server. For a public production server you should configure or purchase a signed SSL certificate, but for now you can just use a self-signed certificate and accept the warnings in the Staff Client and browser during testing and development: +
+ Commands to create an SSL key + + $ mkdir /etc/apache2/ssl + $ cd /etc/apache2/ssl + $ openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key + +
+ + + This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: + + + [[ ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE ]] +
+
+ Modify the Apache Configuration File + As the root user, edit the Apache configuration file /etc/apache2/sites-available/eg.conf and make the following changes: + + + Comment out the line Allow from 10.0.0.0/8, then uncomment the line Allow from all. - This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: + This change allows access to your configuration CGI scripts from any workstation on any network. This is only a temporary change to expedite testing and should be removed after you have finished and successfully tested the Evergreen installation. - - [[ ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE ]] -
-
- Modify the Apache Configuration File - As the root user, edit the Apache configuration file /etc/apache2/sites-available/eg.conf and make the following changes: - - - Comment out the line Allow from 10.0.0.0/8, then uncomment the line Allow from all. + - This change allows access to your configuration CGI scripts from any workstation on any network. It is a temporary change to expedite testing and should be removed after you have finished and successfully tested the Evergreen installation. + You must remove these changes after testing is completed. See the section "Post-Installation Chores" for further details on removing this change after the Evergreen installation is complete. - - - You must remove these changes after testing is completed. See the section "Post-Installation Chores" for further details on removing this change after the Evergreen installation is complete. - - - - - Comment out the line Listen 443 as it conflicts with the same declaration in the configuration file: /etc/apache2/ports.conf . Debian etch users should not do this. - [[ ADD INFO ON WHY DEBIAN ETCH USERS SHOULD NOT DO THIS ]] - - - The following updates are needed to allow the logs to function properly, but it may break other Apache applications on your server. We hope to make this unnecessary soon. - [[ ADD INFO ON WHETHER THIS IS STILL NECESSARY ]] - - - For the Linux distributions Ubuntu Hardy or Debian Etch, as the root user, edit the Apache configuration file /etc/apache2/apache2.conf and change the user: - www-data - to the user: - opensrf - - - For the Linux distributions Ubuntu Karmic or Ubuntu Lucid or Debian Lenny, as the root user, edit the Apache configuration file /etc/apache2/envvars and change the phrase: - export APACHE_RUN_USER=www-data - to the phrase: - export APACHE_RUN_USER=opensrf - - - - - As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line KeepAliveTimeout 1, or modify an existing line if it already exists. - - -
-
- (OPTIONAL) Performance Modifications for Apache - Some further configuration changes to Apache may be necessary for busy systems. These changes increase the number of Apache server processes that can be started to support additional browser connections, and are made to the prefork configuration section of the Apache configuration file. - - As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line MaxKeepAliveRequests 100, or modify an existing line if it already exists. - - As the root user, edit the Apache configuration file /etc/apache2/apache2.conf, locate and modify the section related to prefork configuration to suit the load on your system. -
- (OPTIONAL) Updates to Apache configuration - - <IfModule mpm_prefork_module> - StartServers 20 - MinSpareServers 5 - MaxSpareServers 15 - MaxClients 150 - MaxRequestsPerChild 10000 - </IfModule> - - MaxKeepAliveRequests 100 - -
- - -
-
- Enable the Evergreen Site - You must run additional Apache configuration commands to enable the Evergreen web site. As the root user, run these commands: -
- Apache Commands to Enable the Evergreen Web Site - - $ su - root + + + + Comment out the line Listen 443 as it conflicts with the same declaration in the configuration file: /etc/apache2/ports.conf . Debian etch users should not do this. + [[ ADD INFO ON WHY DEBIAN ETCH USERS SHOULD NOT DO THIS ]] + + + The following updates are needed to allow the logs to function properly, but it may break other Apache applications on your server. We hope to make this unnecessary soon. + [[ ADD INFO ON WHETHER THIS IS STILL NECESSARY ]] + + + For the Linux distributions Ubuntu Hardy or Debian Etch, as the root user, edit the Apache configuration file /etc/apache2/apache2.conf and change the user: + www-data + to the user: + opensrf + + + For the Linux distributions Ubuntu Karmic or Ubuntu Lucid or Debian Lenny, as the root user, edit the Apache configuration file /etc/apache2/envvars and change the phrase: + export APACHE_RUN_USER=www-data + to the phrase: + export APACHE_RUN_USER=opensrf + + + + + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line KeepAliveTimeout 1, or modify an existing line if it already exists. + + +
+
+ (OPTIONAL) Performance Modifications for Apache + Some further configuration changes to Apache may be necessary for busy systems. These changes increase the number of Apache server processes that can be started to support additional browser connections, and are made to the prefork configuration section of the Apache configuration file. + + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line MaxKeepAliveRequests 100, or modify an existing line if it already exists. + + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf, locate and modify the section related to prefork configuration to suit the load on your system. +
+ (OPTIONAL) Updates to Apache configuration + + <IfModule mpm_prefork_module> + StartServers 20 + MinSpareServers 5 + MaxSpareServers 15 + MaxClients 150 + MaxRequestsPerChild 10000 + </IfModule> + + MaxKeepAliveRequests 100 + +
+ + +
+
+ Enable the Evergreen Site + You must run additional Apache configuration commands to enable the Evergreen web site. As the root user, run these commands: +
+ Apache Commands to Enable the Evergreen Web Site + + $ su - root - # disables the default site (i.e., the "It Works" page). - $ a2dissite default + # disables the default site (i.e., the "It Works" page). + $ a2dissite default - # enables the Evergreen web site - $ a2ensite eg.conf - -
-
-
- Modify the OpenSRF Configuration File - As the opensrf user, edit the OpenSRF configuration file /openils/conf/opensrf_core.xml to update various usernames and passwords, and to specify the domains from which we will accept and to which we will make connections. - If you are installing Evergreen on a single server and using the private.localhost / public.localhost domains, these will already be set to the correct values. Otherwise, search and replace to match your customized values. - - - The following example uses common XPath syntax on the left-hand side to indicate the aproximage position needing changes within the XML file. - - - [[ ADD A BETTER DIAGRAM HERE ]] -
- Updates needed to the file "/openils/conf/opensrf_core.xml" - - /config/opensrf/username = opensrf + # enables the Evergreen web site + $ a2ensite eg.conf + +
+
+
+ Modify the OpenSRF Configuration File + As the opensrf user, edit the OpenSRF configuration file /openils/conf/opensrf_core.xml to update various usernames and passwords, and to specify the domains from which we will accept and to which we will make connections. + If you are installing Evergreen on a single server and using the private.localhost / public.localhost domains, these will already be set to the correct values. Otherwise, search and replace to match your customized values. + + + The following example uses common XPath syntax on the left-hand side to indicate the aproximage position needing changes within the XML file. + + + [[ ADD A BETTER DIAGRAM HERE ]] +
+ Updates needed to the file "/openils/conf/opensrf_core.xml" + + /config/opensrf/username = opensrf - /config/opensrf/passwd = password for "private.localhost" opensrf user + /config/opensrf/passwd = password for "private.localhost" opensrf user - /config/gateway/username = opensrf + /config/gateway/username = opensrf - /config/gateway/passwd = password for "public.localhost" opensrf user + /config/gateway/passwd = password for "public.localhost" opensrf user - # first entry, where "transport/server" == "public.localhost" : - /config/routers/router/transport - username = router - password = password for "public.localhost" router user - # second entry, where "transport/server" == "private.localhost" : - /config/routers/router/transport - username = router - password = password for "private.localhost" router user - -
-
-
- Create Configuration Files for Users Needing srfsh - The software installation will automatically create a utility named srfsh (surf shell). This is a command line diagnostic tool for testing and interacting with the OpenSRF network software. It will be used in a future step to complete and test the Evergreen installation. See the section "Testing the Installation" for further information. - In this step you will set up a special configuration file for each user who will need to run the utility. Copy the short sample configuration file /openils/conf/srfsh.xml.example to the file .srfsh.xml (note the leading dot!) in the home directory of each user who will use srfsh. Finally, edit each file .srfsh.xml and make the following changes: - - Modify domain to be the router hostname (following our domain examples, private.localhost will give the utility srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). - Modify username and password to match the opensrf Jabber user for the chosen domain - Modify logfile to be the full path for a log file to which the user has write access - Modify loglevel as needed for testing - -
- 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 --> - <srfsh> - <router_name>router</router_name> - <domain>private.localhost</domain> - <username>opensrf</username> - <passwd>evergreen</passwd> - <port>5222</port> - <logfile>/tmp/srfsh.log</logfile> - <!-- 0 None, 1 Error, 2 Warning, 3 Info, 4 debug, 5 Internal (Nasty) --> - <loglevel>4</loglevel> - </srfsh> - -
-
-
- Modify the OpenSRF Environment - As the opensrf user, change the file permissions of the directory /openils/var/cgi-bin to executable, then modify the shell configuration file ~/.bashrc of that user by adding a Perl environmental variable. Finally, execute the shell configuration file to load the new variables into your current environment. - - - In a multi-server environment, you must add any modifications to ~/.bashrc to 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 - - # change permissions - $ su - opensrf - $ chmod 755 /openils/var/cgi-bin/*.cgi + # first entry, where "transport/server" == "public.localhost" : + /config/routers/router/transport + username = router + password = password for "public.localhost" router user + # second entry, where "transport/server" == "private.localhost" : + /config/routers/router/transport + username = router + password = password for "private.localhost" router user + +
+
+
+ Create Configuration Files for Users Needing srfsh + The software installation will automatically create a utility named srfsh (surf shell). This is a command line diagnostic tool for testing and interacting with the OpenSRF network software. It will be used in a future step to complete and test the Evergreen installation. See the section "Testing the Installation" for further information. + In this step you will set up a special configuration file for each user who will need to run the utility. Copy the short sample configuration file /openils/conf/srfsh.xml.example to the file .srfsh.xml (note the leading dot!) in the home directory of each user who will use srfsh. Finally, edit each file .srfsh.xml and make the following changes: + + Modify domain to be the router hostname (following our domain examples, private.localhost will give the utility srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). + Modify username and password to match the opensrf Jabber user for the chosen domain + Modify logfile to be the full path for a log file to which the user has write access + Modify loglevel as needed for testing + +
+ 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 --> + <srfsh> + <router_name>router</router_name> + <domain>private.localhost</domain> + <username>opensrf</username> + <passwd>evergreen</passwd> + <port>5222</port> + <logfile>/tmp/srfsh.log</logfile> + <!-- 0 None, 1 Error, 2 Warning, 3 Info, 4 debug, 5 Internal (Nasty) --> + <loglevel>4</loglevel> + </srfsh> + +
+
+
+ Modify the OpenSRF Environment + As the opensrf user, change the file permissions of the directory /openils/var/cgi-bin to executable, then modify the shell configuration file ~/.bashrc of that user by adding a Perl environmental variable. Finally, execute the shell configuration file to load the new variables into your current environment. + + + In a multi-server environment, you must add any modifications to ~/.bashrc to 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 + + # change permissions + $ su - opensrf + $ chmod 755 /openils/var/cgi-bin/*.cgi - # add environmental variable - $ echo "export PERL5LIB=/openils/lib/perl5:\$PERL5LIB" >> ~/.bashrc + # add environmental variable + $ echo "export PERL5LIB=/openils/lib/perl5:\$PERL5LIB" >> ~/.bashrc - # inherit the new environment - $ . ~/.bashrc - -
-
-
- (OPTIONAL) Configuration for Other Languages - This section describes how translations such as Armenian (hy-AM), Canadian French (fr-CA) and others are loaded into the database to complete the translations (default English) available in the OPAC and Staff Client. - [[ ADD SECTION ON LANGUAGE LOCALIZATION ]] -
+ # inherit the new environment + $ . ~/.bashrc + + +
+
+ (OPTIONAL) Configuration for Other Languages + This section describes how translations such as Armenian (hy-AM), Canadian French (fr-CA) and others are loaded into the database to complete the translations (default English) available in the OPAC and Staff Client. + [[ ADD SECTION ON LANGUAGE LOCALIZATION ]]
Starting Evergreen @@ -723,15 +725,14 @@ As the root user, edit the Apache configuration file /etc/apache2/sites-available/eg.conf again and make the following change: - Uncomment the line Allow from 10.0.0.0/8, then comment out the line Allow from all. You modified this file earlier in step 5.1.15 as a temporary measure to expedite testing. Those changes must now be reversed in order to deny access to your CGI scripts by other public networks. You must secure this for a public production system, preferably by explicitly specifying the allowed IP addresses and adding proper authentication. + Uncomment the line Allow from 10.0.0.0/8, then comment out the line Allow from all. You modified this file in an earlier step as a temporary measure to expedite testing (see the section "Modify the Apache Configuration File" for further information). Those changes must now be reversed in order to deny unwanted access to your CGI scripts from users on other public networks. You must secure this for a public production system. - - This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: - + This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: "Getting a Signed SSL Security Certificate" . + + Getting a Signed SSL Security Certificate - [[ ADD EXPLANATION OF HOW TO GET A SIGNED SSL CERTIFICATE ]]
@@ -823,57 +824,74 @@
-
- Installing OpenSRF - [[ Installing OpenSRF 1.2.2 ]] -
Installing Evergreen On Other Linux Systems - [[ Installing on Other Linux Systems ]] + [[ ADD CONTENT FOR INSTALLING ON OTHER LINUX SYSTEMS ]]
Installing Evergreen in Virtualized Unix Environments - Evergreen software currently runs as a native application on any of several well-known Linux distributions (e.g., Ubuntu and Debian). It does not run as a native application on the Windows operating system (e.g., WindowsXP, WindowsXP Professional, Windows7), but the software can be installed and run on Windows via a virtualized Unix-guest Operating System (using, for example, VirtualBox or VMware to emulate a Linux environment). More information on virtualized environments can be found in the section "Installing Evergreen in Virtualized Unix Environments". - [[ Installing Evergreen in Virtualized Unix Environments ]] + Evergreen software currently runs as a native application on any of several well-known Linux distributions (e.g., Ubuntu and Debian). It does not run as a native application on the Windows operating system (e.g., WindowsXP, WindowsXP Professional, Windows7), but the software can be installed and run on Windows via a virtualized Unix-guest Operating System (using, for example, VirtualBox or VMware to emulate a Linux environment). + [[ ADD CONTENT FOR INSTALLING EVERGREEN IN VIRTUALIZED UNIX ENVIRONMENTS ]]
VirtualBox - [[ VirtualBox ]] + [[ ADD CONTENT FOR VirtualBox ]]
VMware - [[ VMware ]] + [[ ADD CONTENT FOR VMware ]]
VirtualPC - [[ VirtualPC ]] + [[ ADD CONTENT FOR VirtualPC ]]
Installing Previous Versions of Evergreen Earlier releases of Evergreen are available. Instructions for installing, configuring and testing earlier versions are found below. + The next most recent previous release of Evergreen is version 1.4.0.6. The accompanying previous release of OpenSRF is version 1.0.x.
Installing Evergreen 1.4.0.6 on Ubuntu or Debian - [[ Installing Evergreen 1.4.0.6 on Ubuntu or Debian ]] + [[ ADD CONTENT FOR INSTALLING EVERGREEN 1.4.0.6 ON UBUNTU OR DEBIAN ]]
Installing OpenSRF 1.0.x - [[ Installing OpenSRF 1.0.x ]] + [[ ADD CONTECNT FOR INSTALLING OPENSRF 1.0.x ]]
-
- Organization and Policy Editing - [[ Organization and Policy Editing ]] +
+ OpenSRF + [[ ADD CONTENT FOR OPENSRF ]]
- Installing the Staff Client - [[ Installing the Staff Client ]] + Installing the Evergreen Staff Client + [[ ADD CONTENT FOR INSTALLING THE EVERGREEN STAFF CLIENT ]] +
+
+ PostgreSQL + [[ ADD CONTENT FOR POSTGRESQL ]] +
+
+ Apache + [[ ADD CONTENT FOR APACHE ]] +
+
+ memcached Servers + [[ ADD CONTENT FOR MEMCACHED ]] +
+
+ Organization and Policy Editing + [[ ADD CONTENT FOR ORGANIZATION AND POLICY EDITING ]]
Installing the SIP Server - [[ Installing the SIP Server ]] + [[ ADD CONTENT FOR INSTALLING THE SIP SERVER ]]
Using nginx to serve static content - [[ Using nginx to serve static content ]] + [[ ADD CONTENT FOR USING NGINX TO SERVE STATIC CONTENT ]] +
+
+ Getting a Signed SSL Security Certificate + [[ ADD EXPLANATION OF HOW TO GET A SIGNED SSL CERTIFICATE ]]