Release test step: Run Test Setup with Clean Install

Ensure that you have the current versions of the required tools installed:

tsh@pc214:~$ java -version
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode)
tsh@pc214:~$ javac -version
javac 1.6.0_03
tsh@pc214:~$ ant -version
Apache Ant version 1.7.0 compiled on August 29 2007
tsh@pc214:~$ bzr
Bazaar -- a free distributed version-control tool
http://bazaar-vcs.org/

Basic commands:
  bzr init           makes this directory a versioned branch
  bzr branch         make a copy of another branch

  bzr add            make files or directories versioned
  bzr ignore         ignore a file or pattern
  bzr mv             move or rename a versioned file

  bzr status         summarize changes in working copy
  bzr diff           show detailed diffs

  bzr merge          pull in changes from another branch
  bzr commit         save some or all changes

  bzr log            show history of changes
  bzr check          validate storage

  bzr help init      more help on e.g. init command
  bzr help commands  list all commands
  bzr help topics    list all help topics

Make a new directory, and change to it.

Make sure you don't have a running Fedora/tomcat server, and that the fedora_install folder does not exist in the new directory. (Do a ps ax | grep tomcat and kill all that it finds.)

Beware of $FEDORA_HOME and $TOMCAT_HOME and $CATALINA_HOME variables. They might point to an old install, and this can cause weird errors in the test. Make sure they are always set as defined below. Remember, if you start a new terminal, they wont be inherited.

Get the Doms distribution from the Fedora Server

export FEDORA_HOME=$PWD/fedora_install
export CATALINA_HOME=$FEDORA_HOME/tomcat
svn co https://merkur.statsbiblioteket.dk/svn/doms/trunk doms
cd doms/test/bin

The following statement reads a password from stdin, and thus cannot be entered in a block of statements.

Install the fedora system. If the system writes ERROR or anything, you probably did not enter the correct SQL password

./domssetup.sh ../../../fedora_install

Build and install the disseminator webservice.

cd ../../disseminator_webservice
ant war
cp dist/gentofte_disseminator.war ../../fedora_install/tomcat/webapps
cd ../../fedora_install
./bin/stop.sh
./bin/start.sh

Install the OAI provider in the fedora server. Same story with the SQL password.

cd ../doms/test/bin
./oaiprovidersetup.sh ../../../fedora_install

cd ../../..

Ensure Fedora is running by visiting http://localhost:7900/fedora/search and search. There should be no items found.

Notes about the stop script

In some special circumstances, the stop script fedora_install/bin/stop.sh will fail to terminate. The cause for this is unknown.

The symptons are that the system is eternally waiting with the message

INFO  [2008-02-21 10:37:19 @ pc987]: Checking that http://localhost:7900/fedora/search is down
INFO  [2008-02-21 10:37:19 @ pc987]: Waiting for server response...
INFO  [2008-02-21 10:37:20 @ pc987]: Waiting for server response...

Killing the script is not a viable option, as the stop script is sometimes called from other install scripts, and these might not be finished at this time.

Instead, open another terminal, ps ax | grep tomcat and kill it. Then the script will continue unpertubed.