• IntegrationOfWaybck

Integrating wayback development into the main project is urgent as the current situation

1. Lacks version control
2. Lacks quality control
3. Requires fiddly manual intervention for rebuild
4. Has poor knowledge management (ie only CSR knows how it works)

Wayback comes as a war file (with supporting scripts for, e.g. url canonicalization). In order to use it one must

1. Unpack the war
2. Replace the supplied configuration files with relevant configuration files
3. Add netarchivesuite jar-files and dependencies to the webapps lib directory (taking appropriate decisions when there are version conflicts)
4. Add the compiled Arcrepository-connector class to the webaps classes directory
5. Repack the war file and deploy to ROOT.

In the current configuration, settings.xml is located in the webapp. It should be moved outside and made available to the classloader by starting tomcat with the appropriate -Ddk.netarkivet.settings.file parameter.

In order to integrate wayback development with netarchivesuite we should

1. Add the current wayback war file to the subversion repository
2. add wayback-core.jar to the main project lib directory
3. Create a wayback module for our own wayback-related code

4. Create a directory in which to place relevant configuration files describing our wayback collection (e.g. wayback.xml, ProxyReplay.xml, CDXCollection.xml)

5. Find an appropriate place to put any scripts we have used for collecting and sorting index files
6. Create an ant target which unpacks the war-file and repacks it ready for deployment to out prod server.

There is a comparative list of dependencies between the wayback and netarchivesuite.

A useful resource on deploying to the tomcat ROOT context: http://www.andrew-eells.com/2009/03/21/tomcat-root-war/