- Verify that you have all the needed software installed according to Quick Start Manual eg. in /home/test/netarchive by starting the Quickstart.
Below, you find other deploy examples ( They have to be modfied to your environment).
- You can now create, run and browse according to the !QuickStart - or User Manual.
Examples of deploy configuration files
The following example of configuration file requires adaptation to your own system before use.
The instance with two replicas divided over two physical locations Each physical locations contain several machines Bitarchive machines, harvester machine and viewerproxy machine Only one physical location has an administator machine, which contains the GUI application, the Bitarchive monitors, the HarvestJobManager, HarvestJobMonitor and the arc repository.
How to add a harvester more on the same machine and set all to HIGHPRIORITY selective harvesting
Using eg deploy_examplexml
- Duplicate the existing harvester <applicationName> definition within <deployMachine>.
In the new duplicate harvester config, change all following duplicate values to new unique values within <deployMachine>:
- <common><jmx><port> and <rmiPort>
- <heritrix><guiport> and <jmxPort>
How to configure which Heritrix report has to be uploaded in the metadata ARC file
Three settings properties control which heritrix reports are added to the metadata ARC file:
- settingsharvesterharvestingmetadataheritrixFilePattern is a java pattern that allows you select which files in the crawl dir (not recursively) to include in the metadata ARC.
- settingsharvesterharvestingmetadatareportFilePattern is also a java pattern that controls which subset of the files selected by heritrixFilePattern are to be considered as report files All the other files will be considered as setup files.
- settingsharvesterharvestingmetadatalogFilePattern is a third java pattern that controls which files in the logs subdirectory of the crawldir are to be added as log files to the metadata ARC.