| Excerpt |
|---|
Released 11 June 2012. |
HighlightsNote: That a blocker bug, BITMAG-565 Monitoring service doesn't received any messages was found in the 0.14 release. Please use the 0.14.1 monitoring-service instead. Updating from 0.14 Referencesettings Remove <ReceiverDestination> under ClientSettings and PillarSettingsAdd PillarSettings Add <AuditContributerDatabaseSpecifics> to PillarSettingsAdd PillarSettings Add <AlarmDatabaseSpecifics> to AlarmServiceSettingsAdd <AuditServiceDatabaseSpecifics> to AuditTrailServiceSettingsAdd <IntegrityDatabaseSpecifics> to IntegrityServiceSettingsAdd <AuditContributerDatabaseUrl> to IntegrityServiceSettingsAdd AlarmServiceSettings Add <AuditServiceDatabaseSpecifics> to AuditTrailServiceSettings Add <AuditTrailPreservationInterval> to AuditTrailServiceSettings Change <DatabaseUrl> to <IntegrityDatabaseUrl> under IntegrityServiceSettings Add <IntegrityDatabaseSpecifics> to IntegrityServiceSettings Add <AuditContributerDatabaseUrl> to IntegrityServiceSettings Add <AuditContributerDatabaseSpecifics> to IntegrityServiceSettings Integrity service Database: TBD The AuditTrailServiceDatabase has been changed, an a new field in the Contributor table has been created. No update method have been made, so the database has to be recreated from scratch. Other services???? |