Over time, a very large number of log records will accumulate in the log database, which makes the handling of log records difficult, and directly affects the performance of a log database. Therefore, it is important to purge unwanted log records from the log database occasionally.
However, purging large number of log records at one time would definitely
result in system failures. In order to avoid such failures, CentraSite
supports purging of the log records in a batch mode. Purging of log records in
a batch mode can be initiated by enabling the
enable.partial.commit
property to
true
in the purger.properties
file. The purger.properties file is located in the
logpurging/resources folder under the CentraSite
installation directory.
Note:
Disabling the enable.partial.commit=true
property would lead to failures if the system is not able to process the huge
amount of log records.
Basically, the log records accumulate at a different rate for each log unit. CentraSite defines a default threshold value for batch purging each of the log units as follows:
##partial commit enabled/disabled enable.partial.commit=true ##policy log threshold policy.log.partial.commit.threshold=1000 ##approval log threshold approval.log.partial.commit.threshold=500 ##events threshold runtime.events.partial.commit.threshold=1000 ##metrics log threshold runtime.performance.log.partial.commit.threshold=1000 ## No of days before the current day for which the data will not be included in the purging, ## in case of Export Log Entries & Delete Log Entries (i.e. No date criteria specified). ## purge.older.than=1
You can modify the threshold values for batch purging the log units as required.
Note:
If the purging type in the Log Configuration page is set to
Export or Delete (No date criteria),
then purging would exclude the log records by the number of days defined in the
purge.older.than
property. For example, if the
purging is scheduled on a weekly on Saturday with
purge.older.than=7
, then log records that are
available a ahead of the week or 7 days would be purged from the log
database.
To change the batch purging properties
Edit the purger.properties that is located in the CentraSite installation directory.
Enable/disable batch purging setting the
enable.partial.commit
property to
true
or false
, as
required. The default value is "true".
Specify the threshold values in the
partial.commit.threshold
property of each log
unit, as required.
Save and close the file.
The changes will take effect immediately in the next purging.
In previous releases of CentraSite, some auditable events remained in the log after purging, even though the events referred to CentraSite objects that no longer existed.
There is one known situation where many of these events were created: the Integration Server can be configured to write metrics information for virtual services into CentraSite at regular intervals. Each metrics update resulted in some leftover events.
If you have upgraded your CentraSite Registry Repository from a previous release, such leftover auditable events might still exist in the log. To remove these auditable events, you can use a command line tool. The tool consists of an executable jar file in the bin folder of the CentraSite installation. It requires a Java 6 runtime and needs to be called in the following way:
java -jar CentraSiteOptimizeAuditableEvents.jar <CentraSite DB URL> <administrator user id> <password>
For example:
java -jar CentraSiteOptimizeAuditableEvents.jar "http://localhost:53307/CentraSite/CentraSite" DOMAIN\admin pAsSw0rD
Note that you need the "CentraSite Administrator" role to run this tool.