Differences between revisions 3 and 4

Set-up and System Maintenance of DOMS Test Setup

$/!\$ Do not use this script at the moment. It is currently broken. Please follow the instructions in the "Automated Setup" section below.

Check out the DOMS project from SVN.
Install MySQL 5 on the machine (see below), if it is not already installed. (sudo /sbin/service mysqld status will tell you if it is installed)
If the MySQL-daemon is not running do sudo /sbin/service mysqld start to start it.
Execute domssetup.sh in test/bin with the wanted test installation folder (no spaces in the name, please) as argument. (F.x. create a test installation folder where the doms folder was created.)

It will prompt for the root password to the MySQL installation (not to be confused with the root password for the machine), create a database with the name fedora_testfoldername and install Fedora under the test folder.

If you want to install with demo-objects, add the command line switch -d. Example:

  ./domssetup.sh -d ~/mydoms

will install a test DOMS at the folder mydoms under home, with the provided demo-objects.

Controlling Fedora

The installation script installs two scripts bin/start.sh and bin/stop.sh in the the root of the installation folder. These should be used for starting and stopping the Fedora server.

When the fedora server has started, installation can be verified by visiting

http://localhost:7900/fedora/search

Overview over software components

MySQL installation

$/!\$ Still current

Note: This was taken verbatim from Fedora.

If you do not yet have MySQL 5 installed, you need to do this, set the password, and start it up.

For Fedora Core Linux 3 or above, or Redhat Enterprise Linux 4 or above, you should be able to install MySQL, and make it start up at system boot, with the following commands:

sudo yum install mysql-server

Continue with:

sudo /sbin/chkconfig mysqld on
sudo /sbin/service mysqld start

which enables start of MySQL server on startup.

Now you should set the root password:

/usr/bin/mysql -u root
mysql> set password for root@localhost=password('new-password');
mysql> set password for root@<<$HOSTNAME>>=password('new-password');

(Remember to replace <<$HOSTNAME>> with your host name)

Summa on a Stick

$/!\$ Almost current. Follow the exact commands in Iteration7ReleaseTest

Download the latest version from http://hera/~te/
Unzip it and run summa-setup.sh
Change the line <entry key="create_new_index">false</entry> to <entry key="create_new_index">true</entry> in summa-storage-build-4327/config/controllucene.properties

Add the following lines to summa-ingest-build-4327/config/targets.properties.xml:

<!-- Properties for the DOMS target -->
    <entry key="doms">/fedora/domsTestHarvest20080123/summa/data/doms</entry>
    <entry key="doms_run">true</entry>
    <entry key="doms_DigesterClass">dk.statsbiblioteket.summa.ingest.OAI.OAIHarvestDirectoryDigester</entry>
    <entry key="doms_full_ingest">false</entry>
    <entry key="doms_encoding">UTF-8</entry>
    <entry key="doms_prefix"></entry> <!-- All ids from DOMS are already prefixed with 'doms:'. -->
    <entry key="doms_check_output">true</entry>
    <entry key="doms_base_name">doms</entry>

Change the line <entry key="targets">oai</entry> to <entry key="targets">doms</entry> in the same file

Copy DOMS-data to data/doms
Copy DOMS-XSLT's to summa-index-build-4327/config/targets/doms

In the file summa-index-build-4327/config/index.properties.xml remove all lines with OpenArchive and add lines like the following:

    <entry key="DOMS_run">true</entry>
    <entry key="DOMS_io_storage">//localhost:8500/summa_storage</entry>
    <entry key="DOMS_xslt_url">file:///home/te/projects/doms_test/summa-build-4327/summa-index-build-4327/config/targets/doms/doms_index.xsl</entry>
    <entry key="DOMS_last_id"></entry>
    <entry key="DOMS_complete_full_index">false</entry>
    <entry key="DOMS_time"></entry>

If the installation is considered stable, it is advisable to point to the XSLTs in CVS instead of the local file-system. Change the line with xslt-url to http://merkur/viewvc/trunk/summa/data/index/targets/doms/doms_index.xsl?root=doms&view=co.

Note: create_new_index in controllucene.properties controls whether the index is created from scratch upon each index or if the existing index should be used.

Summa harvester

The harvester is responsible for harvesting data from Fedora (or any other OAI-PMH source) and dump them as XML in a designated data dir. The dumped data can be ingested by Summa.

The harvester is located in the folder summa-harvest-build-4327 in the Summa on a Stick folder. The config.properties and the targets.xml files in the config folder contains setup-information. The detault-settings put harvested data in a data-subfolder in the summa-harvest-build-4327 folder and performs the harvest from http://alhena:7900/oaiprovider/.

The harvester is started with the harvest.sh-script.

Starting the Summa Prototype

It is strongly recommended that the following guide is executed by a user called summa, although this should not be strictly necessary.

Start rmiregistry

Run $JAVA_HOME/bin/rmiregistry 8500 &