perl translate install fr-FR # or use your preferred language codes
2. make
-3.(optional) make test
+3.(optional) make test
4. sudo make install
5. sudo ln -s /etc/koha/koha-httpd.conf /etc/apache2/sites-available/koha
(note that the path to koha-httpd.conf may be different depending on your
=======
If you are running in another language other than english, please
switch to english before doing the upgrade, the templating system has
-changed and the templates will need to be regenerated.
+changed and the templates will need to be regenerated.
Once you have upgraded, please regenerate your templates in your
chosen languages.
sudo make upgrade
Koha 3.4.x or later no longer stores items in biblio records.
-If you are upgrading from an older version ou will need to do the
+If you are upgrading from an older version ou will need to do the
following two steps, they can take a long time (several hours) to
complete for large databases
3. Fast Index:
$ misc/migration_tools/rebuild_zebra.pl -b -w
- Once the indexing has completed, you will be able to search for records in your
- system. NOTE: if you don't run the Fast Index utility, and you have the index
- updates scheduled as per 7.3 the indexing process will happen in the background,
Once the indexing has completed, you will be able to search for records in your
system. NOTE: if you don't run the Fast Index utility, and you have the index
updates scheduled as per 7.3 the indexing process will happen in the background,
but it will be orders of magnitude slower.
4. Schedule regular index updates
- run rebuild_zebra.pl -b -a -z as a regular cron job, check misc/cronjobs/crontab.example
- for usage examples
+ run rebuild_zebra.pl -b -a -z as a regular cron job, check the 'misc/cronjobs/crontab.example' file for usage examples
+
+ You can also configure zebra-indexing as an background daemon, see http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra
5. To enable public Z39.50/SRU servers, you'll need to edit your koha-conf.xml and
change the <listen> options to listen on a TCP port; then restart the zebra daemon.
Feedback/bug reports: Koha Developer's List:
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
-This document last modified: 2011-06-19
+This document last modified: 2012-March-20
Installation Instructions
=============================
You can test your SAX parser by running:
$ cd koha
- $ misc/sax_parser_print.pl
+ $ misc/sax_parser_print.pl
You should see something like:
XML::LibXML::SAX::Parser=HASH(0x81fe220)
-If you are configured to use PurePerl or Expat, the script will say you have a problem and
+If you are configured to use PurePerl or Expat, the script will say you have a problem and
you'll need to edit your ini file to correct it.
The file is typically located at:
Point your browser to http://<servername>:8080/
Note: <servername> is (usually) the IP of your server, or localhost (if you are connecting
- from the same machine Koha is installed on. You can verify the location by checking
+ from the same machine Koha is installed on. You can verify the location by checking
the VirtualHost settings for both the opac and intranet virtual hosts in koha-httpd.conf
-Koha will redirect you to the Web Installer where you can continue the setup. You will be prompted to enter in your DATABASE username and password. It is through this interface
-that
+Koha will redirect you to the Web Installer where you can continue the setup. You will be prompted to enter in your DATABASE username and password. It is through this interface
+that
you can install the sample data for libraries, patrons, and much more.
-Be aware that removing sample data at a later time (when you may want to take the
-server into production) may not be easy, and if your intent is to take this
+Be aware that removing sample data at a later time (when you may want to take the
+server into production) may not be easy, and if your intent is to take this
install from testing to production, go with minimal sample data (no patrons or bibliographic records).
6. Configure and start Zebra
$ sudo -u <kohauser> crontab -e
For Zebra indexing, you are looking for the example that begins with
-
+
# ZEBRA INDEX UPDATES with -z option, incremental index updates throughout the day
# for both authorities and bibs
It may be easiest to copy/paste the example into your own crontab and modify as necessary.
+You can also configure zebra-indexing as an background daemon, see http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra
7. What next?
Once the indexing has completed, you will be able to search for records in your system.
NOTE: This script should be run as the kohauser (the default is 'koha', this is the user we set up in step 2.3).
-7.3 Schedule regular index updates
+7.3 Schedule regular index updates with cron ,or configure zebra indexing as a background daemon
+
You need to run rebuild_zebra.pl -b -a -z as a regular cron job in orde to pick up new bibs
and items as you add them. Check misc/cronjobs/crontab.example for usage examples. See 7.0 above.
NOTE: This job should be setup under the kohauser (the default is 'koha', this is the user we set up in step 2.3).
+ To setup indexing in background see 6.2.2
+
7.4 To enable public Z39.50/SRU servers, you'll need to edit your koha-conf.xml and
change the <listen> options to listen on a TCP port; then restart the zebra daemon.
No liability for the contents of this document can be accepted.
-Feedback/bug reports: Koha Developer's List:
+Feedback/bug reports: Koha Developer's List:
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
-This document last modified: 15 Oct 2010
+This document last modified: 20 Mar 2012
== Installation Instructions ==
This document describes the different stages of installing the software Koha 3 on the openSUSE 11.3 Linux distribution in a "new" computer, the author uses a VirtualBox virtual machine, that is, a virtual computer that will have its virtual hard disk contents COMPLETELY ERASED to install openSUSE and Koha!
-In this example, the virtual machine uses a bridged network connection, which mimics a separate computer in the local network, it's assumed that your server gets an IP address by DHCP that later will be changed to 192.168.1.16.
+In this example, the virtual machine uses a bridged network connection, which mimics a separate computer in the local network, it's assumed that your server gets an IP address by DHCP that later will be changed to 192.168.1.16.
You'll have to change this to the real IP address that your machine should get (or use DHCP, if that's the case).
After the "Welcome" screen, you'll get a First menu, with the following options:
----
-Boot from Hard Disk
+Boot from Hard Disk
Installation
Rescue System
-Firmware Test
+Firmware Test
Memory Test
----
You'll see two Dropdown Lists: "Language" and "Keyboard Layout"
-This depends of your place and preference, naturally.
-I live in The Netherlands, and we use the English (US) Keyboard Layout but I prefer an Operating System in English.
+This depends of your place and preference, naturally.
+I live in The Netherlands, and we use the English (US) Keyboard Layout but I prefer an Operating System in English.
So I leave the default option selected for "Language" and "Keyboard Layout" to (English (US)).
Check the "I Agree to the License Terms" checkbox (under the "License Agreement" textbox).
You may now login with your "root" user.
==== Changing the Hostname and Domain Name ====
-
+
Maybe you want to change the hostname, domain name and switch from DHCP to a Static IP address.
Changing the hostname and domain name will not be shown here, because we assume that was done according to your whishes during installation.
I want to disable IPv6, so I first go to the "Global Options" section (by pushing the key combination ALT+G to press the "G" letter in Global Options that is highlighted).
In the next screen, I push ALT+E to uncheck the "Enable IPv6" checkbox.
I'll get a dialog box with a Warning saying that "To apply this change a reboot is needed.".
-I just press ENTER on that dialog box, but I do NOT reboot (at least not yet).
+I just press ENTER on that dialog box, but I do NOT reboot (at least not yet).
Then I press Alt+V to go to the "Overview" (still in "Network Settings").
Then I press ALT+I to "Edit" the information for this Network Card.
Find the lines starting with AcceptEnv and insert a # in front of these, There are three lines.
Afterwards these lines will look like:
|--------------------
-#AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
-#AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
+#AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
+#AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
#AcceptEnv LC_IDENTIFICATION LC_ALL
|--------------------
==== "Configured Software Repositories" screen ====
-When on this screen, you already see a table that has:
+When on this screen, you already see a table that has:
* as configured repositories (in the "Name" column)
** "Updates for openSUSE 11.3 11.3-1.82"
** "openSUSE-11.3 11.3-1.82"
** "openSUSE-11.3-Debug"
-** "openSUSE-11.3-Non-Oss" "openSUSE-11.3-Oss" ...
+** "openSUSE-11.3-Non-Oss" "openSUSE-11.3-Oss" ...
* at least the following repositories have an "x" in the "Enabled" column
** "Updates for openSUSE 11.3 11.3-1.82"
** "openSUSE-11.3-Oss"
* you still have to add the folowing repositiory to this list
-** "openSUSE BuildService - devel:languages:perl"
+** "openSUSE BuildService - devel:languages:perl"
Press ALT+A to Add Repositories.
==== "Media type" screen ====
|--------------------
System -> Language
-The "Languages" screen should appear.
+The "Languages" screen should appear.
In the first section (Primary Language Settings):
Starting service MySQL done
|--------------------
-Now, let's type again the show variables like 'char%' mysql command to see if
-the character_set_variables have changed from latin1 to utf8 (character_set_filesystem
+Now, let's type again the show variables like 'char%' mysql command to see if
+the character_set_variables have changed from latin1 to utf8 (character_set_filesystem
will still read "binary" but I think that's OK:
|--------------------
myhost:/etc # mysql -p
=== Create the koha database and user with associated privileges ===
|--------------------
-# mysqladmin -uroot create koha -p
+# mysqladmin -uroot create koha -p
|--------------------
(you may name the koha database something different from koha)
-=== Grant privileges to a MySQL user to the koha database ===
+=== Grant privileges to a MySQL user to the koha database ===
Assuming that you want to have a MySQL user called "kohaadmin" to administer a database called "koha" with the password "kohapassword", you'd enter this:
|--------------------
|--------------------
# cd /root/koha-3.00.00/
-myhost:~/koha-3.00.00 # misc/sax_parser_print.pl
+myhost:~/koha-3.00.00 # misc/sax_parser_print.pl
|--------------------
You will probably see this:
XML::SAX::PurePerl=HASH(0x8356a4c)
|--------------------
-If you're using PurePerl (you probably are) or Expat, you'll need to edit your ParserDetails.ini file to use the LibXML Parser.
+If you're using PurePerl (you probably are) or Expat, you'll need to edit your ParserDetails.ini file to use the LibXML Parser.
To find the ParserDetails.ini file, you may use locate.
To do this, first update the locate database by running the updatedb command:
|--------------------
|--------------------
myhost:/usr/lib/perl5/vendor_perl/5.10.0/XML/SAX # cd /root/koha-3.00.00
|--------------------
-After installation of a number of CPAN/perl packages we will run perl Makefile.PL to run the Koha installer.
+After installation of a number of CPAN/perl packages we will run perl Makefile.PL to run the Koha installer.
=== Using zypper to install CPAN modules ===
== Running the Makefile.PL module to configure Koha ==
My installation is a UNIMARC installation, so I'm answering unimarc to the "MARC format for Zebra indexing (marc21, unimarc) [marc21]" question below.
-If your Library uses the MARC21 format instead of UNIMARC, you should press ENTER to accept the default (which is marc21).
+If your Library uses the MARC21 format instead of UNIMARC, you should press ENTER to accept the default (which is marc21).
Because my bibliographic catalog will have mainly records in English and Arabic, I'm answering "en" (English) to the "Primary language for Zebra indexing (en, fr) [en]" question below.
[many more lines beginning with "cp" should appear...]
-t/Amazon.t .................. ok
-t/Barcodes_PrinterConfig.t .. ok
-t/Bookfund.t ................ ok
-t/Bookseller.t .............. ok
-t/Boolean.t ................. ok
-t/Branch.t .................. ok
-t/Calendar.t ................ ok
-t/Charset.t ................. ok
+t/Amazon.t .................. ok
+t/Barcodes_PrinterConfig.t .. ok
+t/Bookfund.t ................ ok
+t/Bookseller.t .............. ok
+t/Boolean.t ................. ok
+t/Branch.t .................. ok
+t/Calendar.t ................ ok
+t/Charset.t ................. ok
t/Debug.t ................... # BEFORE use: $debug is not defined
# BEFORE use: $cgi_debug is not defined
t/Debug.t ................... 1/3 # AFTER use: $debug is 0
# AFTER use: $cgi_debug is 0
# Done.
-t/Debug.t ................... ok
-t/dummy.t ................... ok
-t/Input.t ................... ok
-t/Koha.t .................... ok
-t/Languages.t ............... ok
-t/Maintainance.t ............ ok
-t/Output.t .................. ok
-t/Record.t .................. ok
-t/Review.t .................. ok
+t/Debug.t ................... ok
+t/dummy.t ................... ok
+t/Input.t ................... ok
+t/Koha.t .................... ok
+t/Languages.t ............... ok
+t/Maintainance.t ............ ok
+t/Output.t .................. ok
+t/Record.t .................. ok
+t/Review.t .................. ok
t/Scrubber.t ................ 1/10 # Note: scrubber test output will have whitespace collapsed for readability
# done.
-t/Scrubber.t ................ ok
-t/Stats.t ................... ok
+t/Scrubber.t ................ ok
+t/Stats.t ................... ok
All tests successful.
Files=19, Tests=47, 3 wallclock secs ( 0.06 usr 0.08 sys + 2.12 cusr 0.25 csys = 2.51 CPU)
Result: PASS
|--------------------
myhost:/etc # exit
|--------------------
-After logging back in, type the following commands to check if
+After logging back in, type the following commands to check if
the KOHA_CONF and PERL5LIB environment variables have been correctly set:
|--------------------
myhost:~ # env | grep KOHA
|--------------------
Listen 8080
|--------------------
-In that file, you should find two VirtualHost sections: one for the OPAC area of Koha and the other one for the Intranet.
+In that file, you should find two VirtualHost sections: one for the OPAC area of Koha and the other one for the Intranet.
If the two virtualHost directives - the lines that start with <nowiki><VirtualHost</nowiki> - in that file are set for the IP Address 127.0.0.2, replace them by the correct IP address of your server.
That file will have 2 ServerName directives (one for each of the 2 VirtualHosts).
You may now login with your koha administrator username and password and reply to the several questions you will be asked.
+== Add Zebra Indexer ==
+
+Add an entry in Koha user crontab to process scheduled added/updated/deleted records
+indexing by Zebra. <script_dir>cronjobs/crontab.example contains examples for these cron jobs (and many more).
+
+NOTE: The cronjobs should be setup under the kohauser (the default is 'koha', but
+this is the user you set up in section 'Create the Koha User and Group').
+
+Edit the crontab for the koha user by running
+ $ sudo -u <kohauser> crontab -e
+
+For Zebra indexing, you are looking for the example that begins with
+
+ # ZEBRA INDEX UPDATES with -z option, incremental index updates throughout the day
+ # for both authorities and bibs
+
+It may be easiest to copy/paste the example into your own crontab and modify as necessary.
+
+You can also configure zebra-indexing as an background daemon, see http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra
projects / koha.git / commitdiff