NetarchiveSuite|
⇤ ← Revision 1 as of 2009-02-02 11:07:35
Size: 16236
Comment:
|
Size: 9384
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This version of !NetarchiveSuite was released on 2009-MM-DD. [[TableOfContents]] | This version of !NetarchiveSuite was released on 2009-MM-DD. [[TableOfContents]] |
| Line 6: | Line 9: |
Apart from a general fixing of bugs (see below) the most important new features are: |
|
| Line 7: | Line 13: |
==== Issue tracking cleanup ==== We have cleaned up the bug/feature request/patch trackers, removing a lot of confusing fields. We are working on the final documentation of explaining the precise definition of each remaining field, and how bugs are handled |
|
| Line 8: | Line 19: |
| ==== Improved stability with JMS connections ==== Previously, if an application lost its connection to the JMS server, the application had to be restarted. It will now attempt to reconnect in known recoverable scenarios. |
|
| Line 11: | Line 20: |
| ==== Security manager supported ==== The !NetarchiveSuite now comes with security.policy files, that limit what source code not in the !NetarchiveSuite jar files or libraries is allowed to do. This will increase the security, especially for bitarchives. The file is distributed as conf/security.policy, and to use it you need to start java with {{{-Djava.security.manager -Djava.security.policy=conf/test.policy}}} See the new batch job possibilities for use case. |
==== New settings structure ==== |
| Line 14: | Line 22: |
| ==== Embedded web server upgraded to Jetty 6.1.6 ==== The embedded web server has been upgraded. This should help on stability in some rare situations where large form fields caused exceptions to happen, and generally improve web server stability. ==== Code supporting MacOS/X ==== Although we do not test our software for compatibility with MacOS/X, we have received a patch that should enable !NetarchiveSuite to run on macs, and the report that with this patch it runs fine. Many thanks to Lars Clausen and The National Library of Scotland for this patch. ==== Better log file naming in QuickStart scripts ==== It is a lot easier to debug !QuickStart installations after the logfiles have been properly named for each application. Many thanks to Lars Clausen and The National Library of Scotland for this patch. |
The way we read settings has been radically updated. It is no longer required to have a settings file with all settings, instead default values are used, if the settings are not set. Furthermore, more than one settings file can be used, one overriding the other. Refer to the ["Installation Manual devel"] for more info on hw they are read. It is recommended to not set values where the default values are acceptable, so new defaults will be deployed automatically, in new versions of !NetarchiveSuite. |
| Line 24: | Line 25: |
| ==== Switch to DecidingScope ==== !NetarchiveSuite now controls Heritrix using deciding scope, rather than the older deprecated !HostScope and !DomainScope. This is expected to improve harvesting performance. For the end user, there is no visible difference. |
|
| Line 27: | Line 26: |
| ==== HarvestDefinitionApplication replaced by GUIApplication ==== The application !HarvestDefinitionApplication has been removed. Instead, use dk.netarkivet.common.GUIApplication. It will work exactly as the old application, assuming you have the !HarvestDefinition site section deployed in settings, that is: |
==== Access to harvest logs ==== |
| Line 30: | Line 28: |
| From the job page of any DONE or FAILED job, there is now a link to inspect the Heritrix logs, metadata files, and harvested files from that job! This greatly enhances the possibilities of debugging why a job behaved as it did. You can also get the subset of a crawl.log that referred to a specific domain in a harvest. === Archive Module === ==== Better handling of third-party batch jobs with tool ==== The command-line tool for submitting third-party batch jobs now supports a much better syntax. Simply launch the tool ({{{dk.netarkivet.archive.tools.RunBatch}}}) with no arguments for a description. == Documentation == The documentation has been brought up to day, and some parts have been elaborated. Especially, the database documentation in the ["Developer Manual"] has been updated, and the scripts to generate a new harvest database now has elaborate documentation on the tables used by the harvest definition interface. These can be found in the distribution packages under {{{scripts/sql}}} == Bugs fixed since NetarchiveSuite 3.6.* == === Common Module === |
|
| Line 31: | Line 44: |
| <settings> ... <common> ... <webinterface> ... <siteSection> <!-- A subclass of SiteSection that defines this part of the web interface. --> <class>dk.netarkivet.harvester.webinterface.DefinitionsSiteSection</class> <!-- The directory or war-file containing the web application for this site section.--> <webapplication>webpages/HarvestDefinition</webapplication> <!-- The URL path for this section of the web interface. --> <deployPath>/HarvestDefinition</deployPath> </siteSection> ... |
bug 1247: FileUtils.unzip does not unzip directories properly |
| Line 49: | Line 46: |
| This is the default, and unchanged since previous versions. | |
| Line 51: | Line 47: |
| ==== OutOfMemory fix ==== When running very large harvests, the index over the harvests caused out of memory errors, both on harvests, due to the index used for deduplications, and on access, due to the index used for browsing. This has been fixed in this release. |
=== Harvester Module === {{{ bug 1157: jobs disappeared in a strange way bug 1181: The templates in scripts/simple_harvest/data/originals/harvestdefinitionbasedir/order_templates are invalid bug 1240: PAUSED heritrix gets terminated by JMXHarvestController bug 1292: Possible to store Jobs in database coming from unknown harvestdefinition bug 1468: If harvest process ends with non-zero exit code for any reason, it will never be retried to start the harvester by the SideKick bug 1469: Wrong translation label in Definitions-find-domains if no domains are in the database FR 1108: Heritrix logs should be accessible in harvest definition interface }}} |
| Line 54: | Line 58: |
| ==== Support for setting a byte limit on event harvests ==== When adding seeds to a harvest definition using the "Add seeds" functionality, it is now possible to set a byte limit. Many thanks to Lars Clausen and The National Library of Scotland for this patch. ==== Support for byte limits over 2GB ==== A previous limit on how large byte limits you can set has been removed. ==== The default byte limit for new configurations is now a setting ==== Previously, when creating a new configuration, the default byte limit was hardcoded to 500MB. Now, it is a setting. Simply set |
=== Archive Module === |
| Line 64: | Line 60: |
| <harvester> <datamodel> <domain> ... <!-- Default byte limit for domain configuration. --> <defaultMaxbytes>1000000000</defaultMaxbytes> ... </domain> </datamodel> </harvester> |
bug 1191: NullPointerException in BitarchiveMonitorServer bug 1193: Exceptions from FileBatchJob stop batch job processing (patially) bug 1212: When a file with bit errors has been restored, it still appears on the list of files with checksum errors bug 1261: Wrong table headings (mostly Danish) in info part on page "Missing Files" bug 1278: Error from RunBatch unexpected bug 1279: Missing toString method on FileBatchJob classes bug 1294: ref. to argument before check of argument in Filelist batchjob FR 1263: Confusing layout of "Files with checksum errors" |
| Line 75: | Line 69: |
| === Archive Module === ==== Bit preservation restructuring ==== The bit preservation has undergone a huge restructuring. This is partly preparation for more actions that will improve bit preservation, but it has the immediate effect, that reestablishing a missing file, or fixing a file with a bit error, will require fewer mouse clicks, and generally perform faster now. It should be possible to restore more files in one go, than was previously possible. ==== Support for submitting externally contributed batch jobs ==== The bit archive now has support for launching a batch job on the archive, that is written by an external source, without recompiling. This is a great tool for researchers wishing to do some analysis on the entire archive. All you have to do is to subclass the abstract class dk.netarkivet.common.utils.arc.!FileBatchJob and implement methods for initialisation, finishing and what to do on each file. The results must be written to an output stream. It will then be executed on all bitarchive machines. The results will be written to a file, or to the screen. To work on individual arc records, rather than entire files, subclass dk.netarkivet.common.utils.arc.ARCBatchJob instead. The mechanism to do this is the command line tool dk.netarkivet.archive.tools.!RunBatch. E.g. {{{ java dk.netarkivet.archive.tools.RunBatch MyBatchJob.class }}} Optionally, you can run the job on a subset of all files, on a specific location, and save the output to a file. Try starting the command line client woth no arguments for an example. It is important to run your bitarchive with a security manager, and a restrictive policy (see above) to use this option. Otherwise external batch jobs might damage you bit archives. === ViewerProxy Module === ==== Feedback when only a partial browse index is available ==== When using the !ViewerProxy for QA, it is relevant that you know exactly what set you are browsing. When requesting a browse index, you will automatically be given the largest available subset of an index that is actually available. However, if some parts are not available, it was previously silently ignored, now it is reported in the !ViewerProxy status interface. |
|
| Line 92: | Line 71: |
| ==== Automatic registering of applications for monitoring ==== Applications now automatically register themselves for monitoring by the monitor GUI. This has two effects: * Positive: You do not need to have a list of the machines to monitor in monitor_settings.xml, and you do not need to update it when adding new machines * Negative: You will not get an error message, if an expected machine does not show up on the list of monitored machines. |
{{{ bug 1223: System overview takes more than 20 secs and Show all never returns bug 1388: Too much logging during automatic registering of applications FR 1471: Monitor plugin had no alternative }}} |
| Line 95: | Line 77: |
| == Documentation == The documentation has been brought up to day, and some parts have been elaborated. Especially, the database documentation in the ["Developer Manual"] has been updated, and the scripts to generate a new harvest database now has elaborate documentation on the tables used by the harvest definition interface. These can be found in the distribution packages under {{{scripts/sql}}} |
=== Deploy Module === {{{ bug 1271: Naming of GuiApplication scripts are misleading }}} |
| Line 98: | Line 82: |
| == Bugs fixed since NetarchiveSuite 3.4.* == === Common Module === |
== Upgrade instructions == === New settings structure === As mentioned above, settings now have defaults, and can be read from multiple settings files. It is recommended that you no longer set settings, where you wish to use the default values. === Default Monitor class moved === The plugin for distributed monitoring using !StatusSiteSection has moved. The setting {{{settings.monitorregistryClient.class}}} that was previously {{{dk.netarkivet.common.distribute.monitorregistry.JMSMonitorRegistryClient}}} is now {{{dk.netarkivet.monitor.distribute.JMSMonitorRegistryClient}}} === New settings === Settings from monitor_settings.xml are now settings in the standard settings files. The new settings are: {{{settings.monitor.jmxUsername}}}: Must match the JMX username in all monitored applications. Default: monitorRole Note that if you change the jmxUsername, you must change the security.policy accordingly. Assuming you set jmxUsername to "anonymous", we need the following line in the security.policy: |
| Line 101: | Line 101: |
| 555 JMS connections cannot reconnect 788 problems with removing MessageListener 1063 Mention environment in webpages 1163 Upgrade to jetty 6.1.6 1175 Underscore in setting environmentName results in Internal Server error in Viewerproxy 1184 Notification is not sent, if backup fails 1185 ProcessUtils starts timer threads that cause random interrupts in our code 1194 Source for webpages is not packaged in source-zipball 1220 Wrong javadoc for method HTMLUtils.makeTableHeader() 1235 Mac support |
grant principal javax.management.remote.JMXPrincipal "anonymous" { permission java.security.AllPermission; }; |
| Line 112: | Line 104: |
| === Harvester Module === {{{ 924 jobs that completely fails reports IOException 1078 DeDuplikator index too large 1093 Domain configurations with large limits are wrongly handled, causing unharvested configurations and schedule time 1100 Distributed heritrix.properties file contains wrong version number 1161 Use of known null value in dk.netarkivet.harvester.webinterface.SelectiveHarvest.updateHarvestDefinition 1118 Harvest templates should have their URL and email address checked 1165 Switch to DecidingScope 1182 Logging of job status no longer contains headings 1206 JMXHeritrixController can fail to initialize without throwing an exception 1213 Missing space before listing of aliases of this domain 1232 Incorrect ArgumentNotValid check in constructor of dk.netarkivet.harvester.harvesting.distribute.DomainStats 1234 Allow max bytes setting for event harvests 1238 JMX connection to Heritrix fails immediately after Heritrix process being started 1242 TimeUnit should be public enumeration type 1245 Required arcsdir value not checked 1248 NPE in deduplicator-0.3.0-20061218b.jar 1250 Check on table version of tabel harvestdefinitions is missing 1255 The default bytelimit for configurations should be a setting }}} === Archive Module === {{{ 1079 snap shot harvest not browsable due to large index 1203 Reestablishing missing files is a lot more inefficient than it should be 1246 Bitpreservation GUI fails 1258 no "Shift infobox for 4 files" on the "Missing Files" page }}} === ViewerProxy module === {{{ 1253 It is impossible to see that only a partial index is available }}} === Monitor Module === {{{ 900 Liveness logger logs too often, every 2 minutes 1042 Automatic registering to monitor of running applications desirable 1050 monitor_settings.xml is not parsed properly 1190 missing letter in danish translation of error message }}} === Documentation === {{{ 1177 UserManual contains wrong information about domains 1273 QuickStart using Mysql as Database fails due to Java access permissions }}} === Tools === {{{ 1029 A tool in dk.netarkivet.archive.tools to retrieve a file from the archive would be nice }}} === Scripts === {{{ 1233 Make harvest.sh name logfiles properly }}} == Upgrade instructions == === Upgrading from 3.4.* === Please note that we only support upgrading from the previous stable release. Upgrading across several stable releases is not supported. You will need to upgrade step-by-step through all stable releases (for instance 3.0 -> 3.2 -> 3.4). |
|
| Line 168: | Line 105: |
| === Upgrade your templates to use DecidingScope === !NetarchiveSuite now requires that you use !DecidingScope in all Heritrix templates. You will need to download al your templates, do the updates described in the ["Installation Manual"], Appendix E, and upload them again. |
|
| Line 171: | Line 106: |
| === Upgrade of jobs table in database === !NetarchiveSuite will automatically upgrade the jobs table in the database. For Derby databases, this may take some time depending of the number of entries in the jobs table. In case of system crash during the upgrade, you will get an error on this when rebooting the system. The upgrade is done safely, therefore no data will be lost, but reestablishment of the system in this rare case must be done manually. Please do not hesitate to contact us on the mailing list in case of such an unfortunete accident. For more detailed information please refer to ConvertingJobsTableFromVersion3To4. |
{{{settings.monitor.jmxPassword}}}: Must match the JMX password in all monitored applications. Default: JMX_MONITOR_ROLE_PASSWORD_PLACEHOLDER |
| Line 174: | Line 108: |
| === Automatic monitor registration settings === The automatic registering of clients is a new pluggable setting. The default implementation sends a JMS notification to the monitoring interface every minute, that informs the monitor that this application is alive and can be monitored. This needs to be set in settings with the following setting: |
=== Changed setting names === |
| Line 177: | Line 110: |
| {{{ <settings> ... <common> ... <monitorregistryClient xsi:type="jmsmonitorregistryclient"> <!-- The class instantiated to register JMX urls at a registry. --> <class>dk.netarkivet.common.distribute.monitorregistry.JMSMonitorRegistryClient</class> </monitorregistryClient> }}} The settings from monitor_settings.xml that describe running applications can be removed. The only thing left in that settings file is: |
The setting {{{settings.common.jms.environmentName}}} is now {{{settings.common.environmentName}}} |
| Line 189: | Line 112: |
| {{{ <settings> <monitor> <!-- the password used to connect to the all Mbeanservers started by the application. This password must be same as the one in jmxremote.password --> <jmxMonitorRolePassword>JMX_MONITOR_ROLE_PASSWORD_PLACEHOLDER</jmxMonitorRolePassword> </monitor> </settings> }}} === Add setting for time out when waiting for responses from JMX subsystems === We communicate with the monitoring framework and Heritrix using JMX. A new setting controls how long we wait for a reply before giving up when trying to communicate. You should add the following to you settings.xml files |
The setting {{{settings.common.harvester.datamodel.domain.tld}}} is now {{{settings.common.topLevelDomains.tld}}} |
| Line 200: | Line 114: |
| {{{ <common> <jmx> ... <!-- How many seconds we will wait before giving up on a JMX connection. --> <timeout>120</timeout> </jmx> </common> }}} === Add setting for default configuration byte limit === It is now configurable what the byte limit is set to, when creating new configurations. You should add the following to you settings.xml files |
The setting {{{settings.common.database.specificsclass}}} is now {{{settings.common.database.class}}} |
| Line 213: | Line 116: |
| {{{ <harvester> <datamodel> <domain> ... <!-- Default byte limit for domain configuration. --> <defaultMaxbytes>1000000000</defaultMaxbytes> ... </domain> </datamodel> </harvester> }}} |
The setting {{{settings.archive.bitarchive.limitForRecordDatatransferInFile}}} is now {{{settings.common.repository.limitForRecordDatatransferInFile}}} The setting {{{settings.archive.arcrepository.location}}} is now {{{settings.common.locations.location}}} The setting {{{settings.archive.arcrepository.batchLocation}}} is now {{{settings.common.locations.batchLocation}}} The setting {{{settings.archive.bitarchive.thisLocation}}} is now {{{settings.common.thisPhysicalLocation}}} The setting {{{settings.monitor.applicationName}}} is now {{{settings.common.applicationName}}} === Removed settings === The setting {{{settings.common.siteSection.deployPath}}} is no longer used. |
| Line 226: | Line 131: |
| If you are maintaining a translation, please note that the following new keys have been added: '''viewerproxy/Translations.properties''': | If you are maintaining a translation, please note that the following new keys have been added: |
| Line 228: | Line 133: |
| {{{ errormsg;request.was.for.0.but.got.1.missing.2=WARNING: The request was for the jobs {0}, but only the jobs {1} had available data for the index. Missing data for the jobs {2} }}} |
|
| Line 234: | Line 136: |
| change.0.failed=Change {0} failed change.0.may.be.added=Change {0} that can be added errormsg;admin.data.not.consistent.for.file.0=Admin data are not consistent for the file {0} replace.file.in.bitarchive.0=Replace the file in bitarchive {0} file.0.has.been.replaced.in.1=The file {0} has been replaced at bitarchive {1} unable.to.correct=Unable to correct no.info.on.file.0=No information could be found on the file ''{0}''. no.checksum=No checksum |
no.files.with.checksum.errors=No files with checksum errors were found location=Location |
| Line 243: | Line 139: |
| The following translations are no longer used, and can be removed: | '''harvester/Translations.properties''' |
| Line 246: | Line 143: |
| change failed may.be.added admin.data.not.consistent.for.file.0 remove.file.from.bitarchive.0 file.0.has.been.deleted.in.1.needs.copy |
subtitle;reports.for.job=Harvest information for job harvest.reports=Browse reports for jobs harvest.files=Browse harvest files for job crawl.log.lines.for.domain.0=Browse only relevant crawl-log lines for domain {0} |
| Line 253: | Line 148: |
| '''archive/Translations.properties''' and '''monitor/Translations.properties'''): All properties starting with "errmsg;" have been renamed to "errormsg;" | '''viewerproxy/Translations.properties''' {{{ pagetitle;qa.get.files=Get harvested files pagetitle;qa.get.reports=Get harvest reports pagetitle;qa.crawllog.lines.for.domain=Lines from crawl.log about domain pagetitle;files.for.job.0=Files for job {0} pagetitle;reports.for.job.1=Reports for job {0} pagetitle;qa.crawllog.lines.for.domain.0.in.1=Lines from crawl.log of job {1} concerning domain {0} helptext;get.job.qa.information.with.viewerproxy=The links below will only work \ if your browser is set up to use the viewerproxy as web proxy. }}} |
| Line 256: | Line 163: |
| ||Version 3.6.0 ||2008-07-03 || Improvement of archive component with regard to security, batch, and preservation; greater JMS stability; important bug fixes, automatic registering of applications for monitoring || ||Version 3.5.0 ||2008-03-04 || Development version aiming for 3.6.0 || ||Version 3.4.2 ||2008-03-14 ||Bug fix release, fixing JMX timeout || ||Version 3.4.1 ||2008-01-16 ||Bug fix release, fixing out of memory on very large indexes || ||Version 3.4.0 ||2008-01-03 ||Separation of Heritrix, work on developing our open source platform, two-part TLDs like co.uk, and lots of bugfixes || ||Version 3.3.* || ||Develop versions aiming for 3.4.0 || ||Version 3.2.3 ||2007-09-27 ||Bugfix of 3.2.2 with patched deduplicator, that fixes problem in parallel indexing || ||Version 3.2.2 ||2007-08-03 ||Bugfix of 3.2.1 with patched Heritrix 1.12.1, that supports ARCRecords larger than 2GBs || ||Version 3.2.1 ||2007-07-04 ||Bugfix of 3.2.0 fixing trouble using the quick start manual. || ||Version 3.2.0 ||2007-07-04 ||Open source release || ||Version 3.1.* || ||Development versions. Version 3.1.7 was kindly reviewed by Internet Archive and the Norwegian national library. || ||Version 3.0.0 ||2007-02-02 ||Marked the naming of the !NetarchiveSuite, the splitting of !NetarchiveSuite into independent modules, and the licensing of !NetarchiveSuite under LGPL || ||Version 2.* || ||Various features and updates || ||Version 2.0 ||2006-08-30 ||Marked a general restructuring of the code, where harvest definition data was backed by a database, the viewerproxy was trimmed and rewritten. || ||Version 1.* || ||Various features and updates || ||Version 1.0 ||2005-07-01 ||The first version of the netarchive| software put in production for harvesting the entire Danish web || ||Version 0.* || ||Various pre-production development versions || |
||Version 3.7.0||2008-11-04||Develop version aiming for 3.8.0|| ||Version 3.6.0||2008-07-03||Improvement of archive component with regard to security, batch, and preservation; greater JMS stability; important bug fixes|| ||Version 3.5.*|| ||Develop versions aiming for 3.6.0|| ||Version 3.4.2||2008-03-14||Bug fix release, fixing JMX timeout|| ||Version 3.4.1||2008-01-16||Bug fix release, fixing out of memory on very large indexes|| ||Version 3.4.0||2008-01-03||Separation of Heritrix, work on developing our open source platform, two-part TLDs like co.uk, and lots of bugfixes|| ||Version 3.3.*|| ||Develop versions aiming for 3.4.0|| ||Version 3.2.3||2007-09-27||Bugfix of 3.2.2 with patched deduplicator, that fixes problem in parallel indexing|| ||Version 3.2.2||2007-08-03||Bugfix of 3.2.1 with patched Heritrix 1.12.1, that supports ARCRecords larger than 2GBs|| ||Version 3.2.1||2007-07-04||Bugfix of 3.2.0 fixing trouble using the quick start manual.|| ||Version 3.2.0||2007-07-04||Open source release|| ||Version 3.1.*|| ||Development versions. Version 3.1.7 was kindly reviewed by Internet Archive and the Norwegian national library.|| ||Version 3.0.0||2007-02-02||Marked the naming of the !NetarchiveSuite, the splitting of !NetarchiveSuite into independent modules, and the licensing of !NetarchiveSuite under LGPL|| ||Version 2.* || ||Various features and updates|| ||Version 2.0 ||2006-08-30||Marked a general restructuring of the code, where harvest definition data was backed by a database, the viewerproxy was trimmed and rewritten.|| ||Version 1.* || ||Various features and updates|| ||Version 1.0 ||2005-07-01||The first version of the netarchive| software put in production for harvesting the entire Danish web|| ||Version 0.* || ||Various pre-production development versions|| |
Release Notes for NetarchiveSuite 3.8.0
This version of NetarchiveSuite was released on 2009-MM-DD.
New features since NetarchiveSuite 3.6.*
Apart from a general fixing of bugs (see below) the most important new features are:
General
Issue tracking cleanup
We have cleaned up the bug/feature request/patch trackers, removing a lot of confusing fields. We are working on the final documentation of explaining the precise definition of each remaining field, and how bugs are handled
Common Module
New settings structure
The way we read settings has been radically updated. It is no longer required to have a settings file with all settings, instead default values are used, if the settings are not set. Furthermore, more than one settings file can be used, one overriding the other. Refer to the ["Installation Manual devel"] for more info on hw they are read. It is recommended to not set values where the default values are acceptable, so new defaults will be deployed automatically, in new versions of NetarchiveSuite.
Harvester Module
Access to harvest logs
From the job page of any DONE or FAILED job, there is now a link to inspect the Heritrix logs, metadata files, and harvested files from that job! This greatly enhances the possibilities of debugging why a job behaved as it did. You can also get the subset of a crawl.log that referred to a specific domain in a harvest.
Archive Module
Better handling of third-party batch jobs with tool
The command-line tool for submitting third-party batch jobs now supports a much better syntax. Simply launch the tool (dk.netarkivet.archive.tools.RunBatch) with no arguments for a description.
Documentation
The documentation has been brought up to day, and some parts have been elaborated. Especially, the database documentation in the ["Developer Manual"] has been updated, and the scripts to generate a new harvest database now has elaborate documentation on the tables used by the harvest definition interface. These can be found in the distribution packages under scripts/sql
Bugs fixed since NetarchiveSuite 3.6.*
Common Module
bug 1247: FileUtils.unzip does not unzip directories properly
Harvester Module
bug 1157: jobs disappeared in a strange way bug 1181: The templates in scripts/simple_harvest/data/originals/harvestdefinitionbasedir/order_templates are invalid bug 1240: PAUSED heritrix gets terminated by JMXHarvestController bug 1292: Possible to store Jobs in database coming from unknown harvestdefinition bug 1468: If harvest process ends with non-zero exit code for any reason, it will never be retried to start the harvester by the SideKick bug 1469: Wrong translation label in Definitions-find-domains if no domains are in the database FR 1108: Heritrix logs should be accessible in harvest definition interface
Archive Module
bug 1191: NullPointerException in BitarchiveMonitorServer bug 1193: Exceptions from FileBatchJob stop batch job processing (patially) bug 1212: When a file with bit errors has been restored, it still appears on the list of files with checksum errors bug 1261: Wrong table headings (mostly Danish) in info part on page "Missing Files" bug 1278: Error from RunBatch unexpected bug 1279: Missing toString method on FileBatchJob classes bug 1294: ref. to argument before check of argument in Filelist batchjob FR 1263: Confusing layout of "Files with checksum errors"
Monitor Module
bug 1223: System overview takes more than 20 secs and Show all never returns bug 1388: Too much logging during automatic registering of applications FR 1471: Monitor plugin had no alternative
Deploy Module
bug 1271: Naming of GuiApplication scripts are misleading
Upgrade instructions
New settings structure
As mentioned above, settings now have defaults, and can be read from multiple settings files. It is recommended that you no longer set settings, where you wish to use the default values.
Default Monitor class moved
The plugin for distributed monitoring using StatusSiteSection has moved. The setting settings.monitorregistryClient.class that was previously dk.netarkivet.common.distribute.monitorregistry.JMSMonitorRegistryClient is now dk.netarkivet.monitor.distribute.JMSMonitorRegistryClient
New settings
Settings from monitor_settings.xml are now settings in the standard settings files. The new settings are:
settings.monitor.jmxUsername: Must match the JMX username in all monitored applications. Default: monitorRole
Note that if you change the jmxUsername, you must change the security.policy accordingly. Assuming you set jmxUsername to "anonymous", we need the following line in the security.policy:
grant principal javax.management.remote.JMXPrincipal "anonymous" {
permission java.security.AllPermission; };settings.monitor.jmxPassword: Must match the JMX password in all monitored applications. Default: JMX_MONITOR_ROLE_PASSWORD_PLACEHOLDER
Changed setting names
The setting settings.common.jms.environmentName is now settings.common.environmentName
The setting settings.common.harvester.datamodel.domain.tld is now settings.common.topLevelDomains.tld
The setting settings.common.database.specificsclass is now settings.common.database.class
The setting settings.archive.bitarchive.limitForRecordDatatransferInFile is now settings.common.repository.limitForRecordDatatransferInFile
The setting settings.archive.arcrepository.location is now settings.common.locations.location
The setting settings.archive.arcrepository.batchLocation is now settings.common.locations.batchLocation
The setting settings.archive.bitarchive.thisLocation is now settings.common.thisPhysicalLocation
The setting settings.monitor.applicationName is now settings.common.applicationName
Removed settings
The setting settings.common.siteSection.deployPath is no longer used.
New translations
If you are maintaining a translation, please note that the following new keys have been added:
archive/Translations.properties
no.files.with.checksum.errors=No files with checksum errors were found location=Location
harvester/Translations.properties
subtitle;reports.for.job=Harvest information for job
harvest.reports=Browse reports for jobs
harvest.files=Browse harvest files for job
crawl.log.lines.for.domain.0=Browse only relevant crawl-log lines for domain {0}viewerproxy/Translations.properties
pagetitle;qa.get.files=Get harvested files
pagetitle;qa.get.reports=Get harvest reports
pagetitle;qa.crawllog.lines.for.domain=Lines from crawl.log about domain
pagetitle;files.for.job.0=Files for job {0}
pagetitle;reports.for.job.1=Reports for job {0}
pagetitle;qa.crawllog.lines.for.domain.0.in.1=Lines from crawl.log of job {1} concerning domain {0}
helptext;get.job.qa.information.with.viewerproxy=The links below will only work \
if your browser is set up to use the viewerproxy as web proxy.
Version History
Version 3.7.0 |
2008-11-04 |
Develop version aiming for 3.8.0 |
Version 3.6.0 |
2008-07-03 |
Improvement of archive component with regard to security, batch, and preservation; greater JMS stability; important bug fixes |
Version 3.5.* |
|
Develop versions aiming for 3.6.0 |
Version 3.4.2 |
2008-03-14 |
Bug fix release, fixing JMX timeout |
Version 3.4.1 |
2008-01-16 |
Bug fix release, fixing out of memory on very large indexes |
Version 3.4.0 |
2008-01-03 |
Separation of Heritrix, work on developing our open source platform, two-part TLDs like co.uk, and lots of bugfixes |
Version 3.3.* |
|
Develop versions aiming for 3.4.0 |
Version 3.2.3 |
2007-09-27 |
Bugfix of 3.2.2 with patched deduplicator, that fixes problem in parallel indexing |
Version 3.2.2 |
2007-08-03 |
Bugfix of 3.2.1 with patched Heritrix 1.12.1, that supports ARCRecords larger than 2GBs |
Version 3.2.1 |
2007-07-04 |
Bugfix of 3.2.0 fixing trouble using the quick start manual. |
Version 3.2.0 |
2007-07-04 |
Open source release |
Version 3.1.* |
|
Development versions. Version 3.1.7 was kindly reviewed by Internet Archive and the Norwegian national library. |
Version 3.0.0 |
2007-02-02 |
Marked the naming of the NetarchiveSuite, the splitting of NetarchiveSuite into independent modules, and the licensing of NetarchiveSuite under LGPL |
Version 2.* |
|
Various features and updates |
Version 2.0 |
2006-08-30 |
Marked a general restructuring of the code, where harvest definition data was backed by a database, the viewerproxy was trimmed and rewritten. |
Version 1.* |
|
Various features and updates |
Version 1.0 |
2005-07-01 |
The first version of the netarchive| software put in production for harvesting the entire Danish web |
Version 0.* |
|
Various pre-production development versions |