From a34e9b3a46caa3481e3beb8a5ce557f568d298ef Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Thu, 2 Sep 2010 12:35:47 -0400 Subject: [PATCH] expand section "Installing Staff Client"; rework some figures and associated titles; adjust some internal links; --- 1.6/admin/ServersideInstallation.xml | 876 ++++++++++++++++++--------- 1 file changed, 578 insertions(+), 298 deletions(-) diff --git a/1.6/admin/ServersideInstallation.xml b/1.6/admin/ServersideInstallation.xml index 1d3a9a0e40..25ab8394db 100644 --- a/1.6/admin/ServersideInstallation.xml +++ b/1.6/admin/ServersideInstallation.xml @@ -8,140 +8,123 @@
Overview - Installing, configuring and testing the Evergreen server-side software is straightforward with the current stable software release. See the section "Installation of Server-Side Software" 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" . - The current version of the Evergreen server-side software runs as a native application 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 to 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". + Installing, configuring and testing the Evergreen server-side software is straightforward with the current stable software release. See the section "Installation of Server-Side Software" 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". + The current version of the Evergreen server-side software runs as a native application 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 to 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: - "Installing PostgreSQL" , - "Apache" and - "memcached Servers" . +"Installing PostgreSQL", +"Apache" and +"memcached Servers". [[ FURTHER REFINEMENT NEEDED HERE ]] - Finally, installation of the Evergreen Staff Client software is reviewed in the section "Running the Evergreen Staff Client" . + Finally, installation of the Evergreen Staff Client software is reviewed in the section "Installing the Evergreen Staff Client".
Evergreen Software Dependencies The Evergreen server-side software has dependencies on particular versions of certain major software sub-components. Successful installation of Evergreen software requires that software versions agree with those listed here: -
- Evergreen software dependencies - - - - - - - - Evergreen - OpenSRF - PostgreSQL - - - - - 1.6.x - 1.2 - 8.2 / 8.3 - - - - - 1.4.x - 1.0 - 8.1 / 8.2 - - - - - 1.2.x - 0.9 - 8.1 / 8.2 - - - - -
+ + Evergreen Software Dependencies + + + + Evergreen + OpenSRF + PostgreSQL + + + + + 1.6.x + 1.2 + 8.2 / 8.3 + + + 1.4.x + 1.0 + 8.1 / 8.2 + + + 1.2.x + 0.9 + 8.1 / 8.2 + + + +
[[ VERIFY THE DEPENDENCIES IN THIS TABLE ]]
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" . + 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" . - This release of Evergreen software is dependent on the Open Service Request Framework (OpenSRF). The current stable release of OpenSRF is version 1.2.2. Instructions for installing, configuring and testing that version are found in the section "Installing OpenSRF On Ubuntu or Debian" . + This release of Evergreen software is dependent on the Open Service Request Framework (OpenSRF). The current stable release of OpenSRF is version 1.2.2. Instructions for installing, configuring and testing that version are found in the section "Installing OpenSRF On Ubuntu or Debian" .
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 + System Hardware 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 ]] - +
+ Conversation on mailing-list about system requirements - From Dan Scott on [http://list.georgialibraries.org/pipermail/ + >>>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 :) + > 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/ + + >>>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 + + 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 + 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 requires only a single Evergreen Server and a single Evergreen 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; you need only the Staff Client. @@ -155,7 +138,7 @@ [[ ADD FURTHER INFORMATION ON SITKA ]]
- Other working systems + Other Working Systems [[ ADD FURTHER INFORMATION ON OTHER WORKING SYSTEMS ]]
@@ -163,7 +146,7 @@
Installation of Server-Side Software This section describes the installation of the major components of Evergreen server-side software. - As far as possible, you should perform the following steps in the exact order 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. See the section on "Backing Up" for further information. + As far as possible, you should perform the following steps in the exact order 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. See the section on "Backing Up" for further information. 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 On Ubuntu or Debian @@ -174,7 +157,7 @@ In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. Debian -- To become the root user, issue the command "su -" and enter the password of the root user. - Ubuntu -- To become the root user, issue the command "sudo su -" and enter the password of your current user. + Ubuntu -- To become the root user, issue the command "sudo su -" and enter the password of your current user. To switch from the root user to a different user, issue the command "su - USERNAME". For example, to switch from the root user to the opensrf user, issue the command "su - opensrf". Once you have become a non-root user, to become the root user again, simply issue the command "exit". @@ -182,7 +165,7 @@ Add the OpenSRF User As the root user, add the opensrf user to the system. The default shell for the new user is automatically set to /bin/bash to inherit a reasonable environment:
- Adding the user "opensrf" + Commands to add "opensrf" user $ su - opensrf $ useradd -m -s /bin/bash opensrf @@ -210,66 +193,57 @@
Install Prerequisites to Build OpenSRF In this section you will install and configure a set of prerequisites that will be used to build OpenSRF. In a following step you will actually build the software using the make utility. - 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 example with the keyword corresponding to the actual Linux distribution listed in Figure 1.5. + 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 example with the keyword corresponding to the actual Linux distribution listed in the "Keywords" figure below.
Commands to install prerequisites for OpenSRF $ su - root $ cd /home/opensrf/OpenSRF-1.2.2 $ make -f src/extras/Makefile.install [distribution] + ...
-
- Keywords used with "make" - - - - - - - Keyword - Description - - - - - debian-lenny - for Debian Lenny (5.0) - - - - - debian-etch - for Debian Etch (4.0) - - - - - ubuntu-karmic - for Ubuntu Karmic (9.10) - - - - - ubuntu-intrepid - for Ubuntu Jaunty (9.04) or Intrepid (8.10) - - - - - ubuntu-hardy - for Ubuntu Hardy (8.04) - - - - -
+ + Keywords Targets for "make" + + + + + + Keyword + Description + + + + + debian-lenny + for Debian Lenny (5.0) + + + debian-etch + for Debian Etch (4.0) + + + ubuntu-karmic + for Ubuntu Karmic (9.10) + + + ubuntu-intrepid + for Ubuntu Jaunty (9.04) or Intrepid (8.10) + + + ubuntu-hardy + for Ubuntu Hardy (8.04) + + + +
[[ ADD INFO FOR OTHER LINUX DISTRIBUTIONS ]] - This will install a number of packages required by OpenSRF on your system, including some Perl modules from CPAN. You can say "no" to the initial CPAN configuration prompt to allow it to automatically configure itself to download and install Perl modules from CPAN. The CPAN installer will ask you a number of times whether it should install prerequisite modules - say "yes". + This will install a number of packages on the system that are required by OpenSRF, including some Perl modules from CPAN. You can say "no" to the initial CPAN configuration prompt to allow it to automatically configure itself to download and install Perl modules from CPAN. The CPAN installer will ask you a number of times whether it should install prerequisite modules - say "yes".
Configure OpenSRF - As the opensrf user, return to your build directory and configure OpenSRF by using the utility "configure" to prepare for the next step of compiling and linking the software. You can include the --enable-python and --enable-java configuration options if you want to include support for Python and Java, respectively: + As the opensrf user, return to the OpenSRF build directory and use the utility "configure" to prepare for the next step of compiling and linking the software. You can include the --enable-python and --enable-java configuration options if you wish to include support for Python and Java, respectively:
Commands to configure OpenSRF @@ -277,18 +251,20 @@ $ cd /home/opensrf/OpenSRF-1.2.2 $ ./configure --prefix=/openils --sysconfdir=/openils/conf $ make + ...
Compile, Link and Install OpenSRF - As the root user, return to your build directory and compile, link and install OpenSRF: + As the root user, return to the OpenSRF build directory and use the make command to compile, link and install OpenSRF:
Commands to build, link and install OpenSRF $ su - opensrf $ cd /home/opensrf/OpenSRF-1.2.2 $ make install + ...
@@ -306,10 +282,10 @@
Define Public and Private OpenSRF Domains - Define your public and private OpenSRF domains. For security purposes, OpenSRF uses Jabber domains to separate services into public and private realms. Throughout these instructions, we will use the example domains public.localhost for the public domain and private.localhost for the private domain. On a single-server system, the easiest way to define public and private domains is to define separate hostnames by adding entries to the file /etc/hosts. + Define your public and private OpenSRF domains. For security purposes, OpenSRF uses Jabber domains to separate services into public and private realms. Throughout these instructions, we will use the example domains public.localhost for the public domain and private.localhost for the private domain. On a single-server system, the easiest way to define public and private domains is to define separate hostnames by adding entries to the file /etc/hosts. As the root user, edit the file /etc/hosts and add the following entries for our example domains:
- Adding public and private domains to /etc/hosts + Example public and private domains in /etc/hosts 127.0.1.2 public.localhost public 127.0.1.3 private.localhost private @@ -317,27 +293,27 @@
- Change file ownerships + Change File Ownerships As the root user, change the ownership of files installed in the directory /openils to the user "opensrf":
- Changing file ownerships in /openils + Commands to change file ownerships $ chown -R opensrf:opensrf /openils
- Stop the "ejabberd" service + Stop the "ejabberd" Service As the root user, stop the "ejabberd" service:
- Stopping the "ejabberd" service + Commands to stop the "ejabberd" service $ /etc/init.d/ejabberd stop
If "ejabberd" reports that it is already stopped, it may have run into a problem starting back at the installation stage. One possible fix is to kill any remaining beam and epmd processes, then edit the ejabberd configuration file to hardcode a domain:
- Recovering from "ejabberd" error + Commands to recover from "ejabberd" error $ su - root $ epmd -kill @@ -351,18 +327,18 @@ Edit the "ejabberd" configuration As the root user, edit the file /etc/ejabberd/ejabberd.cfg and make the following changes: - Change {hosts, ["localhost"]}. to {hosts, ["localhost", "private.localhost", "public.localhost"]}. - Change {max_user_sessions, 10}. to {max_user_sessions, 10000}. If you see something like this instead: {access, max_user_sessions, [{10, all}]}., then change it to {access, max_user_sessions, [{10000, all}]}. + Change {hosts, ["localhost"]}. to {hosts, ["localhost", "private.localhost", "public.localhost"]}. + Change {max_user_sessions, 10}. to {max_user_sessions, 10000}. If you see something like this instead: {access, max_user_sessions, [{10, all}]}., then change it to {access, max_user_sessions, [{10000, all}]}. Change all three occurrences of max_stanza_size to 2000000. Change both occurrences of maxrate to 500000. - Comment out the line {mod_offline, []} by placing two % comment signs in front. + Comment out the line {mod_offline, []} by placing two % comment signs in front.
Restart the "ejabberd" service As the root user, restart the ejabberd service to test the configuration changes and to register your users:
- Restarting the "ejabberd" service + Commands to restart the "ejabberd" service $ /etc/init.d/ejabberd start @@ -377,7 +353,7 @@ As the root user, use the utility "ejabberdctl" to register your ejabber users router and opensrf for the OpenSRF router service on each domain. The users should have different passwords on each domain. These users will correspond to those configured in the file /openils/conf/opensrf_core.xml:
- Registering "router" and "ejabberd" users + Commands to registe "router" and "ejabberd" users # Syntax for registering a user with ejabberdctl: # ejabberdctl register <user> <domain> <password> @@ -393,7 +369,7 @@ Create configuration files As the opensrf user, use the example templates to create the configuration files /openils/conf/opensrf_core.xml and /openils/conf/opensrf.xml:
- Creating configuration files + Commands to create configuration files $ su - root $ cd /openils/conf @@ -411,7 +387,7 @@
- Updates needed to the file "/openils/conf/opensrf_core.xml" + Updates needed in the file "/openils/conf/opensrf_core.xml" /config/opensrf/username = opensrf @@ -439,7 +415,7 @@ Modify the file /openils/conf/opensrf.xml. As the opensrf user, edit the file to set the location of the persistent database in the <dbfile> element near the end of the file:
- Modify the file "opensrf.xml" + Example of the file "opensrf.xml" <!-- Example of an app-specific setting override --> <opensrf.persist> @@ -453,7 +429,7 @@
Create Configuration Files for Users Needing srfsh In this section you will set up a special configuration file for each user who will need to run the srfsh (surf shell) utility. - The software installation will automatically create srfsh. 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. + The software installation will automatically create srfsh. 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. As the root user, 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. When you finish, remember to change the owner of the file to match the owner of the home directory. Modify domain to be the router hostname (following our domain examples, private.localhost will give srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). @@ -462,7 +438,7 @@ Modify loglevel as needed for testing
- Sample of configuration file /openils/conf/srfsh.xml.example + Example of the file "/openils/conf/srfsh.xml.example" <?xml version="1.0"?> <!-- This file follows the standard bootstrap config file layout --> @@ -481,10 +457,10 @@
- Modify environmental variable PATH for "opensrf" user + Modify Environmental Variable PATH for "opensrf" User As the opensrf user, modify the environmental variable PATH by adding a new file path to the opensrf user's shell configuration file .bashrc:
- Adding path to ".bashrc" configuration file + Commands to add path to ".bashrc" configuration file $ su - opensrf $ echo "export PATH=/openils/bin:\$PATH" >> ~/.bashrc @@ -495,7 +471,7 @@ Starting OpenSRF As the root user, start the "ejabberd" and "memcached" services:
- Starting some services + Commands to start "ejabberd" and "memcached" services $ su - root $ /etc/init.d/ejabberd start @@ -505,7 +481,7 @@ Finally, as the opensrf user, start OpenSRF:
- Starting OpenSRF + Commands to start OpenSRF $ su - opensrf @@ -527,7 +503,7 @@ Testing connections to OpenSRF Once you have installed and started OpenSRF, as the root user, test your connection to OpenSRF using the utility srfsh and trying to call the add method on the OpenSRF "math" service:
- Testing OpenSRF with "srfsh" + Commands to test OpenSRF with "srfsh" $ su - opensrf $ /openils/bin/srfsh @@ -547,7 +523,7 @@ Stopping OpenSRF As the opensrf user, stop OpenSRF:
- Stopping OpenSRF + Commands to stop OpenSRF $ su - opensrf $ osrf_ctl.sh -l -a stop_all @@ -564,13 +540,13 @@ In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. Debian -- To become the root user, issue the command "su -" and enter the password of the root user. - Ubuntu -- To become the root user, issue the command "sudo su -" and enter the password of your current user. + Ubuntu -- To become the root user, issue the command "sudo su -" and enter the password of your current user. To switch from the root user to a different user, issue the command "su - USERNAME". For example, to switch from the root user to the opensrf user, issue the command "su - opensrf". Once you have become a non-root user, to become the root user again, simply issue the command "exit".
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" . + 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.
@@ -589,90 +565,73 @@
Install Prerequisites to Build Evergreen In this section you will install and configure a set of prerequisites that will be used to build Evergreen. In a following step you will actually build the software using the make utility. - 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 example with the keyword corresponding to the actual Linux distribution listed in Figure 1.26. + 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 example with the keyword corresponding to the actual Linux distribution listed in the "Keywords" figure below.
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] + ...
-
- Keywords used with "make" - - - - - - - Keyword - Description - - - - - 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 - - - - -
+ + Keywords Targets for "make" + + + + + + Keyword + Description + + + + + 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 ]]
(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 @@ -681,9 +640,11 @@ # 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 + ...
@@ -744,7 +705,7 @@
Configure and Evergreen - As the opensrf user, return to your build directory and configure Evergreen by using the utility "configure" to prepare for the next step of compiling and linking the software: + As the opensrf user, return to the Evergreen build directory and use the utility "configure" to prepare for the next step of compiling and linking the software:
Commands to configure Evergreen @@ -752,19 +713,30 @@ $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ ./configure --prefix=/openils --sysconfdir=/openils/conf $ make + ...
-
+
Compile, Link and Install Evergreen - As the root user, return to your build directory and compile, link and install Evergreen. - In the following commands, 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 the directory /openils/var/web/xul to the /server subdirectory of your Staff Client build: + In this step you will actually compile, link and install Evergreen and the default Evergreen Staff Client. + As the root user, return to the Evergreen build directory and use the make command to compile, link and install Evergreen. The Staff Client is built automatically, but you must 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. + For further information on manually building the Staff Client, see the section "Installing the Evergreen Staff Client".
- Commands to build, link and install Evergreen + Commands to build, link and instal Evergreen $ su - root $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_6 install + $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_7 install + ... + + The above commands will create a new subdirectory /openils/var/web/xul/rel_1_6_0_7 containing the Staff Client. +
+ As the root user, create a symbolic link named server in the head of the Staff Client directory /openils/var/web/xul that points to the /server subdirectory of the new Staff Client build: +
+ Commands to create symbolic link + + $ su - root $ cd /openils/var/web/xul $ ln -sf rel_1_6_0_7/server server @@ -772,7 +744,7 @@
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: + As the root user, copy the example OpenSRF configuration files into place. This replaces the configuration files that you set up in a previous step when you installed and tested 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 @@ -785,7 +757,7 @@
- Create and configure PostgreSQL Database + 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/ . @@ -813,9 +785,9 @@ Create new Evergreen superuser - As the postgres user on the PostgreSQL system, create the new user evergreen : + As the postgres user on the PostgreSQL system, create the new user evergreen:
- Commands to create the 'evergreen' user + Commands to create the "evergreen" user # create superuser 'evergreen' and set the password $ su - postgres @@ -845,7 +817,7 @@
- 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. + 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.
@@ -882,7 +854,7 @@
- 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: [[ ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE ]] @@ -898,7 +870,7 @@ - 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. @@ -911,13 +883,13 @@ [[ 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: + 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: + 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 @@ -937,7 +909,7 @@ 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 + (OPTIONAL) Example of updates to Apache configuration <IfModule mpm_prefork_module> StartServers 20 @@ -957,7 +929,7 @@ 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 + Commands to enable the Evergreen Web Site $ su - root @@ -972,7 +944,7 @@
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. + 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. @@ -980,15 +952,15 @@ [[ ADD A BETTER DIAGRAM HERE ]]
- Updates needed to the file "/openils/conf/opensrf_core.xml" + Updates needed in the file "/openils/conf/opensrf_core.xml" - /config/opensrf/username = opensrf + /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 @@ -1004,7 +976,7 @@
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. + 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 section 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 srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). @@ -1013,7 +985,7 @@ Modify loglevel as needed for testing
- Sample of configuration file /openils/conf/srfsh.xml.example + Example of the file "/openils/conf/srfsh.xml.example" <?xml version="1.0"?> <!-- This file follows the standard bootstrap config file layout --> @@ -1040,7 +1012,7 @@
- Modify the OpenSRF environment + Commands to modify the OpenSRF environment # change permissions $ su - opensrf @@ -1068,7 +1040,7 @@ Testing Connections to Evergreen Once you have installed and started Evergreen, test your connection to Evergreen. As the opensrf user start the utility srfsh and try logging onto the Evergreen server using the default administrator username and password. Following is sample output generated by executing that script after a successful Evergreen installation:
- Testing Evergreen with "srfsh" + Commands to test Evergreen with "srfsh" $ su - opensrf $ /openils/bin/srfsh @@ -1101,7 +1073,7 @@ As the opensrf user, run the script settings-tester.pl to see if it finds any system configuration problems. Following is sample output generated by executing that script after a successful Evergreen installation: [[ REWORK THIS DIAGRAM TO USE SAME IMAGE STANDARDS AS OTHER CHAPTERS ]]
- Executing the script <emphasis> settings-test.pl</emphasis> + Executing the script <emphasis>settings-test.pl</emphasis> @@ -1113,7 +1085,7 @@
- If the output from the script does not help you find the problem, please do not make any further significant changes to your configuration. Follow the steps in the troubleshooting guide, "Troubleshooting" . + If the output from the script does not help you find the problem, please do not make any further significant changes to your configuration. Follow the steps in the troubleshooting guide, "Troubleshooting" . If you have followed the entire set of installation steps listed here closely, you are probably extremely close to a working system. Gather your configuration files and log files and contact the [[ http://open-ils.org/listserv.php|Evergreen development mailing list ]] for assistance before making any drastic changes to your system configuration. @@ -1143,7 +1115,7 @@ Once you have started Evergreen and confirmed that a basic login attempt works, you can test and start the Apache web server. As the root user, execute the following commands. Note the use of restart to force the new Evergreen modules to be reloaded even if the Apache server is already running. Any problems found with your configuration files should be displayed:
- Test the Apache Web Server + Commands to test the Apache Web Server $ su - root $ apache2ctl configtest && /etc/init.d/apache2 restart @@ -1155,9 +1127,9 @@ Starting Evergreen - As the root user, start the "ejabberd" and "memcached" services (if they aren't already running): + As the root user, start the "ejabberd" and "memcached" services (if they are not already running):
- Starting some services + Commands to start "ejabberd" and "memcached" services $ su - root $ /etc/init.d/ejabberd start @@ -1169,7 +1141,7 @@ As the opensrf user, start Evergreen. Use the flag -l to force Evergreen to use localhost (your current system) as the hostname. Using the start_all option will start the OpenSRF router, Perl services, and C services:
- Starting Evergreen + Commands to start Evergreen $ su - opensrf @@ -1183,13 +1155,13 @@
- You can also start Evergreen without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. + You can also start Evergreen without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. [[ ADD EXPLANATION 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 + (OPTIONAL) Commands to determine the fully qualified domain name $ perl -e 'use Net::Domain qw(hostfqdn); print hostfqdn()."\n"' @@ -1203,7 +1175,7 @@ As the opensrf user, generate the Web files needed by the Staff Client and catalogue, and calculate the proximity of locations in the Organizational Unit tree (which allows Holds to work properly). You must do this the first time you start Evergreen, and after any time you change the library hierarchy in the configuration file config.cgi.
- Generate web files + Commands to generate web files $ su - opensrf $ cd /openils/bin @@ -1224,7 +1196,7 @@ As the root user, restart the Apache Web server:
- Restart the Apache web server + Commands to restart Apache web server $ su - root $ /etc/init.d/apache2 restart @@ -1238,7 +1210,7 @@ Stopping Evergreen As the opensrf user, stop all Evergreen services by using the following command:
- Stopping all Evergreen services + Commands to stop Evergreen $ su - opensrf @@ -1249,7 +1221,7 @@
- You can also stop Evergreen services without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. + You can also stop Evergreen services without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. [[ ADD EXPLANATION FOR CONFIGURING "opensrf.xml" ]] @@ -1259,24 +1231,24 @@
Remove temporary changes from Apache configuration file 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 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. + 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.
Configure a permanent SSL key In a previous step, we used the command openssl to temporarily create a new SSL key for the Apache server. For a public production server you should configure or purchase a signed SSL certificate - The temporary SSL key was only created 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" . + The temporary SSL key was only created 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" .
Set Up Support For Reports - Evergreen reports are extremely powerful, but some configuration is required. See the section "Reports" for details. + Evergreen reports are extremely powerful, but some configuration is required. See the section "Reports" for details.
Starting the Reporter Daemon Once the open-ils.reporter process is running and enabled on the gateway, you can start the reporter daemon. That process periodically checks for requests for new reports or scheduled reports and gets them running. As the opensrf user, start the reporter daemon using the following command:
- Starting the Reporter Daemon + Commands to start the Reporter daemon $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/src/reporter @@ -1296,11 +1268,11 @@ To stop the Reporter daemon, you must kill the process and remove the lockfile. The daemon may have just a single associated process, with a lockfile in the default location. - It is possible that several processes are running; see the optional commands in the previous section. As the opensrf user, perform the following commands to stop the Reporter daemon: + It is possible that several processes are running; see the optional commands in the previous section. As the opensrf user, perform the following commands to stop the Reporter daemon:
- Stopping the Reporter Daemon + Commands to stop the Reporter daemon $ su - opensrf # find and kill the process ID number(s) @@ -1313,12 +1285,320 @@
+ Installing the Evergreen Staff Client + The Staff Client is automatically built by default as part of the normal make install process for Evergreen server-side software. See the section "Compile, Link and Install Evergreen" to review the final compile/link/install phase of the default Evergreen build process. +
+ Building the Evergreen Staff Client + You can also build the Staff Client manually by running the make command in the source directory /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client. The make command accepts a number of options to build special versions of the Staff Client. Following is a list of environment variables that can be passed to make to influence the manual build process: + + + STAFF_CLIENT_BUILD_ID + This variable defaults to an automatically generated date/time string during the normal Evergreen server-side software installation process. The following command was probably used during the normal Evergreen build process: +
+ Commands used during normal Evergreen build + + $ make STAFF_CLIENT_BUILD_ID=my_test_id install + ... + +
+ Following is a method to manually build the Staff Client while using a specific BUILD_ID. As the opensrf user, set the variable and build the Staff Client: +
+ Commands to manually build Staff Client + + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_BUILD_ID=my_test_id build + ... + +
+ + + STAFF_CLIENT_VERSION + This variable is normally pulled from a README file in the Evergreen source root. The following command could be used during the normal Evergreen build process: +
+ Commands used during normal Evergreen build + + $ make STAFF_CLIENT_VERSION=0mytest.200 install + ... + +
+ + +If you manually build the Staff Client, version will default to 0trunk.revision, where revision is either automatically pulled from SVN or an empty string on failure. If you wish to make extensions update automatically then your version needs to conform to the format found in [[https://developer.mozilla.org/en/Toolkit_version_format|Toolkit Version Format]] and newer versions need to be "higher" than older versions. + +Following is a method to manually build the Staff Client while using a specific VERSION. As the opensrf user, set the variable and build the Staff Client: +
+ Commands to manually build Staff Client + + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_VERSION=0mytest.200 build + ... + +
+ + + STAFF_CLIENT_STAMP_ID variable + This variable is generated from STAFF_CLIENT_VERSION, but you can also specify it manually. You may wish to have multiple versions of the Staff Client with different stamps, possibly for different uses or client-side customizations. The following command could have been used during the normal Evergreen build process: +
+ Commands used during normal Evergreen build + + $ make STAFF_CLIENT_VERSION=0mytest.200 install + ... + +
+ Following is a method to manually build the Staff Client while using a specific VERSION. As the opensrf user, set the variable and build the Staff Client: +
+ Commands to manually build Staff Client + + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_VERSION=0mytest.200 build + ... + +
+ + +
+
+ Advanced Build Options + In addition to the basic options above there are a number of other options for building the Staff Client. Most are target names for the make utility and thus require that you build from the Staff Client directory. See the following table for a list of keywords that can be used with the make utility: + + Keywords Targets for "make" Command + + + + + + Keyword + Description + + + + + clients + Runs "make win-client", "make linux-client", and "make generic-client" individually + + + client_dir + Builds a client directory from the build directory, without doing a rebuild. This mainly amounts to "copy everything but server/". + + + client_app + Prereq "client_dir"; Removes "install.rdf" from client directory so that an app bundle can't be installed as an extension + + + client_ext + Prereq "client_dir"; Removes "application.ini", "autoupdate.js", "standalone_xul_app.js" from client directory so that an extension won't break Firefox + + + extension + Prereq "client_ext"; Re-written to use client_ext. + + + generic-client + Prereq "client_app"; Makes an xpi suitable for xulrunner --install-app usage + + + win-xulrunner + Prereq "client_app"; Adds windows xulrunner to the client build + + + linux-xulrunner + Prereq "client_app"; Adds Linux xulrunner to the client build + + + win-client + Prereq "win-xulrunner"; Builds "setup exe" (requires that nsis package be installed, will add options for automatic update if configured and developer options if client build was a "make devbuild") + + + linux-client + Prereq "linux_xulrunner"; Builds a tar.bz2 bundle of the Linux client + + + [generic | win | linux | extension]-updates[-client] + Calls external/make_updates.sh to build full and partial updates generic/win/linux/extension prefix limit to that distribution; Adding -client builds clients and copies them to a subdirectory of the updates directory as well; extension-updates-client doesn't exist. + + + +
+ + + Developer Build + A so-called "developer build" of the Staff Client will be created if you substitute "devbuild" for "build" when running the command make from the Staff Client directory. The build will contain an extra configuration file that enables some developer options. + + As the opensrf user, run the make from the Staff Client directory: +
+ Commands to do a "developer build" + + $ su - opensrf + $ cd /openils/var/web/xul/ + $ make devbuild + ... + +
+ + + Compressed Javascript + +If you replace "build" with "compress-javascript" then Google's Closure Compiler will be run on the Staff Client after the build process. + From the Staff Client directory: $ make compress-javascript + If you want to combine a developer build with this you can tack them together, order is important: + From the Staff Client directory:$ make devbuild compress-javascript + + + Automatic Update Host + The host used for automatic update checking can be set or overridden with the AUTOUPDATE_HOST option: + During install: $ make AUTOUPDATE_HOST=localhost install + From Staff Client directory: $ make AUTOUPDATE_HOST=localhost build + For more information see the section "Staff Client Automatic Updates". + + +
+
+ Installing/Activating the Staff Client + The Staff Client built at the make install stage is automatically installed and activated for use. However, if you are building from the Staff Client directory you need to take additional steps. + Assuming your installation is in the directory /openils and you have already built the Staff Client, the from the Staff Client directory run: + + $ mkdir -p "/openils/var/web/xul/$(cat build/STAMP_ID)" + $ cp -R build/server "/openils/var/web/xul/$(cat build/STAMP_ID)" + +
+
+ Packaging the Staff Client + Once the Staff Client is built you can build several forms of client packages with make commands from the Staff Client directory. + + + Generic Client + Building a generic client requires that you have the "zip" utility installed in your system, and will produce an xpi file that is suitable for use with the xulrunner parameter --install-app. The output file evergreen_staff_client.xpi will be created. + +$ make generic-client + + + + Windows Client + Making a windows client requires that you have the "unzip" and "makensis" utilities installed in your system. The "makensis" utility may be installed with a "nsis" package, although you will need a recent version for all functionality to be available. We recommend using Version 2.45 or later of makensis. + As a side note, if you wish for the Staff Client to have a link icon/tray icon by default you may wish to provide a pre-modified xulrunner-stub.exe. Place it in the Staff Client directory and the makefile will use it instead of the one that comes with the downloaded xulrunner release. + If you wish to do so the version of xulrunner-stub.exe need not match exactly. You can use a tool like [[http://www.angusj.com/resourcehacker/|Resource Hacker]] to embed icons. + Useful icon ID strings: + + IDI_APPICON - Tray icon + 32512 - Default window icon + + The output file "evergreen_staff_client_setup.exe" will be created. + + $ make win-client + ... + + + + Linux Client + The linux client is merely a tar.bz2 file with xulrunner bundled with it. The output file "evergreen_staff_client.tar.bz2" will be created. + + $ make linux-client + ... + + + + Extension + The Staff Client can optionally be built as a Firefox extension. Doing so requires the "zip" utility be installed. The output file "evergreen.xpi" will be created. + + make extension + + + +
+
+ Staff Client Automatic Updates + The Staff Client can be set up to be automatically updated. + + WARNINGS + Automatic update server certificate requirements are more strict than normal server requirements. XULRunner and Firefox will both ignore any automatic update server that is not validated by a trusted certificate authority. Servers with exceptions added to force the Staff Client to accept them WILL NOT WORK. + In addition, extension updates require one of two things to be done for the file update.rdf. It must either be served from an SSL server, or it must be signed with the [[https://developer.mozilla.org/en/McCoy|McCoy]] tool. You can pre-install the signing key into the file install.rdf directly, or install it into a copy as install.mccoy.rdf . If the latter exists it will be copied into the build instead of the original file install.rdf. + + Autoupdate Host + The automatic update host can be provided in two ways: + + + At configure time: ./configure --with-updateshost=hostname + Remember to include your other configure options. + + + During the Staff Client build process + You will used the variable AUTOUPDATE_HOST=hostname (see above). If you specify just a hostname (such as example.com) then the url will be an HTTPS url (such as https://example.com). If you wish to use a non-HTTPS url then prefix the hostname with "http://". (such as "http://example.com"). + If neither option is used then the Staff Client will not include the automatic update preferences by default. + + + + + Building updates + Similar to building clients, the generic-updates, win-updates, linux-updates, and extension-updates targets will build the update files for the Staff Client. If you plan on building them all you can just use the "updates" target. + A "full" update will be built for each specified target (or for all if just "updates" is used). For all but extensions any previous "full" updates (archived in /openils/var/updates/archives by default) will be used to make "partial" updates. Partial updates tend to be much smaller and will thus download more quickly, but if something goes wrong with a partial update the full update will be used as a fallback. Extensions do not appear to support partial updates at this time. + + $ make updates + ... + $ make generic-updates + ... + $ make win-updates + ... + $ make linux-updates + ... + $ make extension-updates + ... + + + + Building updates with clients + To save time/effort you can build updates and manual download clients at the same time by adding -client to the target, such as win-updates-client. This does not work for extension-updates, but does work for the "build all" updates target. + The clients will be installed alongside the updates and listed on the manualupdate.html page, rather than left in the Staff Client directory. + + $ make updates-client + ... + $ make generic-updates-client + ... + $ make win-updates-client + ... + $ make linux-updates-client + ... + + + + Activating the update server + The apache example configuration creates an "updates" folder that, by default, points at /openils/var/updates/pub. This folder contains several script files that pretend to be normal files and/or folders, as well as one HTML file. + The following scripts should be marked as executable: check, download, manualupdate.html, update.rdf. + The updatedetails.html file is the fallback page for the update details. + The check script is used for xulrunner updates, the update.rdf script for extension updates. + The manualupdate.html script checks for clients to provide download links when automatic updates have failed and uses the download script to force a download of the generic client xpi (compared to Firefox trying to install it as an extension). + + +
+
+ Other tips + + + Multiple workstations on one install + Multiple workstation registrations for the same server can be accomplished with a single Staff Client install by using multiple profiles. When running xulrunner you can specify -profilemanager or -P (ensure that P is uppercase on Linux!) as an option to force the profile manager to come up. Unchecking the "Don't ask at startup" option will make this the default. + Once you have opened the profile manager you can create additional profiles, one for each workstation you want to register. You may need to install SSL exceptions for each profile. + When building win-client, win-updates-client, or updates-client, specifying "NSIS_EXTRAOPTS=-DPROFILES" will add an "Evergreen Staff Client Profile Manager" option to the start menu. + +$ make NSIS_EXTRAOPTS=-DPROFILES win-client + + + + Multiple Staff Clients + It may get confusing if you are not careful, but you can log in to multiple evergreen servers at the same time, or a single evergreen server multiple times. In either case you will need to create an additional profile for each additional server or workstation you want to log in as (see previous tip). + Once you have done so, run xulrunner with the -no-remote command line option (in addition to -profilemanger or -P if neeeded). Instead of xulrunner opening a new login window on your existing session it will start a new session instead, which can then be logged in to a different server or workstation ID. + + +
+
+
Running the Evergreen Staff Client [[ ADD CONTENT: LINUX VS WINDOWS STAFF CLIENT ]] Run the Evergreen Staff Client on a Linux system by using the application XULRunner (installed automatically and by default with Firefox version 3.0 and later on Ubuntu and Debian distributions). For example, if the source files for the Evergreen installation are in the directory /home/opensrf/Evergreen-ILS-1.6.0.7/, start the Staff Client as shown in the following command example:
- Running the Linux Staff Client + Commands to run the Staff Client $ su - opensrf $ xulrunner /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client/build/application.ini @@ -1367,7 +1647,7 @@ Apache
Securing Apache (httpd) - The main consideration is to secure the directory cgi-bin . The only persons that need access to this directory are Evergreen system administrators. This directory should be restricted by both IP (to those workstations designated as Evergeen Administration systems), and by username/password. + The main consideration is to secure the directory cgi-bin. The only persons that need access to this directory are Evergreen system administrators. This directory should be restricted by both IP (to those workstations designated as Evergeen Administration systems), and by username/password. [[ ADD CONTENT ON HOW TO RESTRICT APACHE BY IP AND USERNAME/PASSWORD ]] A user could add new libraries, re-arrange consortia, or change user groups; or a staff member could access the directory, and change his associated security group to administrative level privileges.
@@ -1379,7 +1659,7 @@
Organization and Policy Editing - After installing Evergreen, you will want to make configuration changes to reflect the organizational hierarchy and the policies of your library or libraries. See the section "Organizational Unit Types and Organizational Units" for further information. Examples of what can be configured include: + After installing Evergreen, you will want to make configuration changes to reflect the organizational hierarchy and the policies of your library or libraries. See the section "Organizational Unit Types and Organizational Units" for further information. Examples of what can be configured include: Adding a branch library Changing circulation rules for an existing library -- 2.43.2