Download and installation

Action(edit)

For a quick start, we have prepared a bash script that starts all the necessary components on one machine. We will use this script throughout this quickstart manual to allow you to get a feel for what the system can do and how it works without having to deal with issues of distributing to other servers.

Base system required

For the quick startup, NetarchiveSuite requires

To check that you have the right version of Java do the following

Downloading

Download and unzip of the newest release is described here

JMS

NetarchiveSuite uses JMS for inter-process communication. JMS is the Java Messaging Service, which provides asynchronous communication between processes. You do not need any knowledge of JMS to use NetarchiveSuite. However you need to make sure that there are not already JMS brokers running on your system using PORT 8100.

Currently only the open-source version of Sun's JMS implementation is supported, since some functionality of other implementations does not match our assumptions well.

To download and install it, do the following:

Configuration

Assuming the NetarchiveSuite files were unzipped to the directory ~/netarchive as described above, you must do the following to configure the NetarchiveSuite for your system:

For the simple harvest setup, the startup script needs to know a few paths. You can either do this by exporting the environment variables in your shell or by changing the harvest script.

The following describes how to set the environment variables:

Note that these environment variables need to be set every time you log in, if you wish to use the quickstart scripts. You can also edit the file harvest.sh and set the variables there, if you wish the settings to be persistent.

[http://netarchive.dk/suite/Installation_Manual_3.10/AppendixC?action=AttachFile&do=get&target=RunNetarchiveSuite.sh RunNetarchiveSuite.sh]

[http://netarchive.dk/suite/Installation_Manual_3.10/AppendixC?action=AttachFile&do=get&target=deploy_example_one_machine.xml deploy_example_one_machine.xml]

The first script is a simple script for doing all the steps during deployment. It takes a NetarchiveSuite package ('.zip'), a configuration file (the second file), and a temporary installation directory as arguments (in the given order).

In the configuration file all the applications are placed on one machine (e.g. the current machine, localhost). If run directly it is installed and run from the directory /home/test/netarchive/USER.

E.g.

cd /home/test/netarchive
bash RunNetarchiveSuite.sh NetarchiveSuite.zip deploy_example_one_machine.xml USER/
#if you have not setup your ssh keygen correctly, you need to login some times before the installation finish successfully. You must allso have permission to ssh and scp to localhost ( try e.g "ssh localhost" and "scp somefile localhost:")

The script creates a "USER" folder in e.g. /home/test/netarchive , which contains e.g. methods for starting and stopping NetarchiveSuite and starts the whole NetarchiveSuite.