Overview of Wayback

Wayback in netarchivesuite consists of three components

1. The wayback webapplication. This is a tomcat webapplication configured with a NetarchiveSuite plugin that allows it communicate with the archive.

2. The NetarchiveSuite batch-indexer. This is a standalone NetarchiveSuite application which indexes newly harvested material.

3. The NetarchiveSuite index-aggregator. This is a standalone NetarchiveSuite application which sorts the indexes and merges them into the large index files used by wayback.

Status of Wayback

The first two components are complete and the third is nearing completion. However the batch-indexer is not useful without the index-aggregator so it should not be run at the present time. However, in the setup used for the release test, the settings file generated for the batch-indexer is also used for wayback itself. Therefore it is necessary to configure and deploy the indexer although it should not be started.

Configuration of Tomcat

Tomcat should be configured with two Connectors in server.xml:

    <Connector port="8080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443"  />
    <Connector port="8090" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443"  />

There are start and stop scripts for tomcat in the webarkivering CVS under conf/wayback/test/scripts. The start script should be modified to point to the desired location of the NetarchiveSuite settings file, the name of the archive environment (PROD or ACCEPT) and a unique applicationInstanceId (e.g. WAYBACK). Note that the stop script includes a cleanup command which removes an unwanted directory from tomcat's temp area.

Configuration of Apache

As discussed at the February teleconference, PROD wayback must only be visible externally via a secured apache proxy (connected to port 8080).

http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/BriefMeeting22Feb2010