1. Check of monitoring and basic settings

Check that

• No error messages are received at start up
• The monitoring works
• The database works and contains test data

Do following in a browser:

Start Program

1. Go to http://$GUIadminserver:$http-port/HarvestDefinition/ where GUIadminserver and http-port are specified in the deploy configuration file under the application named dk.netarkivet.common.webinterface.GUIApplication. In the one-machine setup (deploy_example_one_machine.xml ) the link will be : http://localhost:8074

Check that JMX works (Partially tested by SystemOverviewTest#generalTest)

• Click 'Systemstate'->'Overview of the system state' (At first, only the 'SystemState' link is visible, which leads to the same script, viz. Status/Monitor-JMXsummary.jsp   
• Check that all internally developed applications are up and running. This depends on the configuration, of course, but there should be
  
  • One GUIApplication
  • One HarvestJobManagerAppplication

  • One or more HarvestControllerApplication. One of these should be HIGHPRIORITY, if you need to run selective/event harvests, and/or
    LOWPRIORITY, if you need to run snapshot harvests

  • One IndexServerApplication
  • One or more ViewerProxy applications
  • One WaybackIndexerApplication (optional)
  • One AggregatorApplication (Optional)
  • If you're using the distributed archive solution (ie using the JMSArcrepositoryClient and not the LocalArcRepositoryClient or BitmagArcRepositoryClient) there should also be
    
    • One ArcRepositoryApplication
    • One or more BitarchiveServer applications per bitarchive replica in your configuration
    • One ChecksumFileApplication representing a checksum replica (if you have a checksum replica)
    • One BitarchiveMonitorServer for each bitarchive replica in your configuration
• Check that last status message for each application do not contain errors or warnings (ignore any spurious messages from "GUIWebServer")
• Check that there are no empty log messages

Check that basic database data is present

• Click 'Definitions'->'Find Domain(s)'
• Search for netarkivet.dk by writing this text and click 'Search'
• Check that the GUI returns a result-set of one, namely the domain netarkivet.dk
• Click on the link netarkivet.dk, and the page for domain netarkivet.dk should be shown without errors
• Click 'Edit' on the configuration line for defaultconfig
• Check that Name is "defaultconfig"
• Check that Harvest template is "default_orderxml"
• Check that Maximum number of objects is "2,000" (in some languages (e.g. Danish) this is represented as 2.000
• Check that Maximum number of bytes is "500,000,000" (in some languages (e.g. Danish) this is represented as 500.000.000
• Check that max hops is set to 20
• Check that Honour robots.txt? is unchecked
• Check that Extract Javascript? is checked

Check that mail recipients specified in the start of this test receive no error mails

• Check that there are no mails with error messages about non-existing files
• Check that there are no mails with error messages about applications that could not be started

Check that the default_orderxml template is a Heritrix3 template( go to the Edit Harvest Templates tab, and retrieve the default_orderxml: If the file-header contains "HERITRIX 3 CRAWL JOB CONFIGURATION FILE ", it is ok.

Check that the DispositionChain includes a deduplicator: 

<ref bean="DeDuplicator"/>

2. Running selective harvest

Partially tested by SelectiveHarvestTest

1. Go to http://$GUIadminserver:$http-port/HarvestDefinition/where GUIadminserver and http-port are specified in the deploy configuration file under the application named dk.netarkivet.common.webinterface.GUIApplication. In the one-machine setup (deploy_example_one_machine.xml ) the link will be : http://localhost:8074
2. Make a new selective harvest definition with a name you can remember
   
   1. Click 'Definitions'->'Selective Harvests' in the left menu
   2. *Click 'Create new harvest definition' in the bottom of the main window
   3.  Fill in the Harvest name and note the name for later use (from now referred as sh.name)
   4. Choose "Once_a_week" in the drop down list for 'Schedule'
   5. In the 'Enter Domain...' window add the name of a domain not already in the system (e.g. mazda.dk) and click 'Add domains'
   6. There should be a button "Create and add to the harvest definition" shown. Click on it.
   7. Click 'Save'
3. Activate the selective harvest
   
   1. Click 'Activate' in column 5 on the line with the sh. name
   2. Check that the time in the "Next Run" column time on the line with the sh. name is now.
4. Check harvest status of the selective harvest
   
   1. Click 'Harvest status'->'All Jobs' in the left menu
   2. Click the "Show" button, until the name appears in a new job line (approx. after a minute)
   3. Check that the job has status "NEW", it may have turned into status "SUBMITTED" or status "STARTED" before you see it.
5. Check job creation in the system status for the selective harvest
1. Click 'Systemstate'->'Overview of the system state'
2. Find and click 'HarvestJobManagerApplication' in the 'Application' column.
3. Click 'show all' in the 'Index' header.
4. Check that there exists a line with the message "INFO: Created 1 jobs for harvest definition ' and a line after that "INFO: Job #1 submitted, and later the line: "INFO: Job #1 has been started by the harvester."

2.1 Run an Umbra Harvest (Skip)

Note: In the netarkivet test environment, umbra runs on test@kb-test-har-005. If umbra is not running, it can be started with 

[test@kb-test-har-005 ~]$ /opt/rh/rh-python36/root/usr/bin/python3 /opt/rh/rh-python36/root/usr/bin/umbra --max-browsers 5 --executable /home/test/run-chrome.sh --url amqp://guest:guest@localhost:5672/%2f --log_config_file /home/test/logging.conf > umbra.log

1. For the same domain as above create a new Harvest Configuration using template default_orderxml (the other template available has not been modified for use with Umbra)
2. Create a Selective Harvest definition using this new configuration
3. Use the Mapping functionality under Harvest Channels in the GUI to map this new configuration to the UMBRA channel
4. Activate the harvest and wait for it to complete
5. Check the crawl log for the completed harvest for the strings "sentToAMQP" and "receivedFromAMQP"

3. Define and run an event harvest

This page describes how to define and run an event harvest. It also test that seeds lists are created from first and second level definition of the domain names.

NB OBS Makes sure all harvests use default_orderxml. The other cxml produces non-compressed warc-files and will not work with the new architecture.

1. Make a new selective (event) harvest definition with a name you can remember
   
   1. Click 'Definitions'->'Selective Harvests' in the left menue
   2. Click 'Create new harvestdefinition' in the bottom of the main window
   3. Fill in the Harvest name and note the name for later use (from now referred as EH)
   4. Choose '''Once_an_hour''' in the drop down list for 'Schedule'
   5. Click Save (DO NOT CLICK ACTIVATE YET)
2. Add seeds to the selective (event) harvest
   
   1. Click 'Edit' in column 6 on the line with the EH
   2. Write the domain list from 'Seed list 1' given below to a file on your desktop e.g. notepad)
   3. Click 'Add seeds from a file' at the bottom of the main page
   4. Click 'Browse" and pick up the just created file with seeds
   5. Choose default_orderxml in the drop-down list for 'Harvest template' (set maxobjects pr domain to 500; max bytes to 400.000.000, maxhops to 0, obey robots.txt? unchecked and extract_javascript checked)  [previously used template frontpages]
   6. Click 'Insert'
   7. Now click 'Add seeds'
   8. Choose default_orderxml in the drop-down list for 'Harvest template'
   9. Write domain list from 'Seed list 2' given below (you can cut and paste from this page) (set maxobjects pr domain to 300; max bytes to 500.000.000, maxhops to 2, obey robots.txt? unchecked and extract_javascript checked) [previously used template frontpages_2levels]
   10. Click 'Insert'
   11. *Click 'Save'
3. Check that seed lists for domains in Seed list 1 has changed correspondingly
   
   1. For each of the domains raeder.dk, netarkivet.dk do:
   2. Click 'Definitions'->'Find Domain(s)'
   3. Search for domain by writing its name as text and click 'Search'
   4. Click the domain name link and on this 'Edit domain' page make sure to click on 'show unused configurations' and 'show unused seedlists')
   5. Check that there exists a configuration with the name "EH_default_orderxml_400000000Bytes_500Objects" (verify that the config has maxHops=0, obey robots unchecked, extract javascript checked)
   6. Check that there exists a seed list with the name "EH_default_orderxml_400000000Bytes_500Objects
   7. Click 'Edit' in the line with seed list "EH_default_orderxml_400000000Bytes_500Objects
   8. Check that the seed list shown corresponds to the seed list for the domain (see below)
   9. Check that seed lists for domains in Seed list 2 has changed correspondingly (you have to click on Show unused configurations/seedlists show all)
   10. For the domains kaarefc.dk, netarkivet.dk do:
   11. Click 'Definitions'->'Find Domain(s)'
   12. Search for the domain by writing this text (either kaarefc.dk or netarkivet.dk) and click Search
   13. Check that there exists a configuration with name EH_default_orderxml_500000000Bytes_300Objects (verify that the config has maxHops=2)
   14. Check that there exists a seed list with the name EH_default_orderxml_500000000Bytes_300Objects
   15. Click 'Edit' in the line with seed list EH_default_orderxml_500000000Bytes_300Objects
   16. Check that the seed list shown corresponds to the seed list for the domain (see below)
4. Activate the harvest
   
   1. Click 'Definitions'->'Selective Harvests' in the left menu
   2. Click 'Activate' in column 5 on the line with the <eh. name>
5. Check harvest status of the event harvest using menu "All Jobs"
   
   1. Click 'Harvest status'->'All Jobs' in the left menu
   2. Select "All" in "Only display job status" to the right from the menu
   3. Click the "Show" button, until the <eh. name> appears in a new job line (approx. after a minute)
   4. Check that two jobs appears and that they both have Harvest name <eh. name>
   5. Check the menu "Running jobs", that the jobs appears and that you can go to H3 Remote Access and monitor the jobs progress e.g. by viewing the cached crawl-log.

Seed list 1 (Harvest template "default_orderxml", maxhops=0, extract_javascript=true, robots.txt=ignore, max objects=500; max bytes=400.000.000):

http://netarkivet.dk/adgang/
http://netarkivet.dk/in-english/
http://www.raeder.dk/
# Fjern denne linie og linien nedenunder
#http://kb-prod-udv-001.kb.dk/netarchivesuite/clock.php (is not visible from any of the harvesters in the test-system, therefore replaced for now by the link below) 
http://localtimes.info/Europe/Denmark/Copenhagen/

Seed list 2 (Harvest template "default_orderxml", maxhops=2, extract_javascript=true, robots.txt=ignore, max objects=300; max bytes=500.000.000):

http://netarkivet.dk/in-english/
http://www.kaarefc.dk/
http://www.kaarefc.dk/private/
http://www.kaarefc.dk/wop/

Seed list "<eh. name>_default_orderxml_400000000Bytes_500Objects" for domain =raeder.dk= __"

http://www.raeder.dk/

Seed list "<eh. name>_default_orderxml_400000000Bytes_500Objects" for domain localtimes.info

http://localtimes.info/Europe/Denmark/Copenhagen/

Seed list "<eh. name>_default_orderxml_400000000Bytes_500Objects" for domain =netarkivet.dk=

http://netarkivet.dk/in-english/
http://netarkivet.dk/adgang/

Seed list "<eh. name>_default_orderxml_500000000Bytes_300Objects" for domain =netarkivet.dk=

http://netarkivet.dk/in-english/

Seed list "<eh. name>_default_orderxml_500000000Bytes_300Objects"" for domain =kaarefc.dk=

http://www.kaarefc.dk/
http://www.kaarefc.dk/wop/
http://www.kaarefc.dk/private/

4. Verify that the harvest is activated and done

This page describes how to verify that a harvest is carried out correctly

1. Click 'Harvest status'->'All Jobs' in the left menu
2. Select "All" in "Only display job status" to the right from the menu
3. Click the "Show" button, until the jobs have stepped through statuses "NEW", "SUBMITTED", "STARTED", "DONE"
4. Wait until all jobs have got status "DONE"
5. Check that you can search on Harvest name, start and end date
6. Check that you can change number of rows to be displayed per page e.g. 1 and
7. Check that you can press next and previous page and
8. Check that the reset button resets all changes to default(note that the display value is also blanked, but is 100 by default)
9. Check the following for the domain raeder.dk: (For example by loading the domain in the Find Domains page and clicking on "History")
   
   1. Check that the domain has been harvested by one job of the name <eh. name>e
   2. Check that this job has configuration EH_default_orderxml_40000000Bytes_500Objects
   3. Check that there is a number for 'Run number' and 'Job ID'
   4. Check that the 'Start time' and 'End time' columns approximately corresponds to time of test with the EH harvest
   5. Check that the 'Bytes Harvested' and 'Documents Harvested' columns contains positive numbers
   6. Check that the 'Stopped due to' columns contains "Domain-config object limit reached"
10. Check the following job details for the domain netarkivet.dk: (Using page SelectiveHarvests->History->Run Number 0 ->JobID 1)
    
    1. Check that the 'Submit time', 'Start time' and 'End time' columns approximately corresponds to time of test with EH harvest
    2. Click on "Browse reports for jobs"
    3. Check that you don't get any errors when you click on some of the links
    4. Click on "Browse harvest files for job"
    5. Check that you don't get any errors when you click on some of the links
    6. Click on "Browse only relevant crawl-log lines for domain netarkivet.dk"
11. Check the following for the domain netarkivet.dk: (Using page Harvest Status -> All jobs per domain)
    
    1. Check that the domain has been harvested by 2 jobs of the name EH
    2. Check that one of the jobs has configuration EH_default_orderxml_400000000Bytes_500Objects
    3. Check that the 'Start time' and 'End time' columns approximately corresponds to time of test with EH
    4. Check that one of the jobs has configuration EH_default_orderxml_500000000Bytes_300Objects
    5. Check that the 'Start time' and 'End time' approximately corresponds to time of test with EH harvest
    6. Check that 'Run number' and 'Job ID' columns contains positive numbers
    7. Check that the 'Bytes Harvested' and 'Documents Harvested' columns contains positive numbers
    8. Check that the 'Stopped due to' columns contains "Domain Completed" or "Domain-config object limit reached"
12. Check the following for the domain kaarefc.dk: (Using page Harvest Status -> All jobs per domain)
    
    1. Check that the domain has been harvested by 1 job of the name EH
    2. Check that the job has configuration EH_default_orderxml_500000000Bytes_300Objects
    3. Check that the 'Start time' and 'End time' approximately corresponds to time of test with EH harvest
    4. Check that 'Run number' and 'Job ID' columns contains positive numbers
    5. Check that the 'Bytes Harvested' and 'Documents Harvested' columns contains positive numbers
    6. Check that the 'Stopped due to' columns contains "Domain Completed"

5. Follow the schedule of the next job

1. Click 'Definitions'->'Selective Harvests' in the left menu
2. Check that the selective harvest <sh. name> is schedule to start in a week
3. Check that the event harvest <eh. name> is schedule to start in approx. an hour
4. Click on edit on the event harvest and override the next run time with current date and time + 5 min
5. Click 'save'
6. Click 'Harvest status'->'All Jobs' in the left menu after 5 min
7. Check that two new event harvest <eh. name> job has been generated
8. Check that NO new selective harvest <sh. name> job has been generated
9. Deactivate the event harvest <eh.name> after number two run.