Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Released 6 May 2012.

Highlights

  • Large number of bug fix.
  • Alarm service persistentcy implemented
  • Status implemented for all components.
  • FileID format formalised through collection setting.

Updating from 0.12

Referencesettings

The values may be changed according to the specific collection.

  1. Add the following lines to the PillarSettings
      <ChecksumPillarChecksumSpecificationSalt></ChecksumPillarChecksumSpecificationSalt>
      <AuditContributerDatabaseUrl>jdbc:derby:audittraildb</AuditContributerDatabaseUrl>
    
  2. Add the following lines to the AuditTrailServiceSettings
      <SendAlarmOnMissingContributer>false</SendAlarmOnMissingContributer>
      <AuditContributerDatabaseUrl>jdbc:derby:auditservicedb</AuditContributerDatabaseUrl
      <CollectAuditInterval>3600000</CollectAuditInterval> <!-- One day.. -->
    
  3. Add the following section for the new MonitoringService
    <MonitoringServiceSettings>
      <ID>monitoring-service</ID>
      <CollectionInterval>60000</CollectionInterval>
      <MaxRetries>3</MaxRetries>
    </MonitoringServiceSettings>
    

List of issues resolved in this release.

type key priority summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Issues found in this release

type key priority summary fixversion

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels