Setting Up Garbage Collection
Garbage collection is the process by which Content Delivery clears old aggregated audit trail information. This procedure describes how to configure the frequency with which garbage collection occurs and how to enable and disable collection.
About this task
Note: If you change the configuration parameters while the scheduled job is running, it will use the new parameters the next time it runs.
Tip: As you hover over an icon its label appears.
Procedure
- Log on to Content Delivery as admin.
- If you are in a Content Delivery tool, click Home in the breadcrumb trail.
The Content Delivery landing page appears.
- In the Administration Tools pane, click Manage Application.
The Manage Application page appears.
- In the left pane, click Global Config.
- For the
audit.garbagecollection.enableitem, click Yes. - Click Save.
- Edit ContentDelivery_home/conf.xml.
- Un-comment the line that defines the job for garbage collection:
<job name="audit.garbagecollection" type="user" xquery="/db/LiveContent/ui/skins/base/xql/audit_garbagecollection.xql" period="3600000" delay="10000" repeat="1000000"/> - Adjust the following values to set the timing of collection:
Option Description period Frequency, in milliseconds, that the collection occurs. delay Delay, in seconds, before collection occurs after restarting the Content Delivery service. repeat Number of times to repeat collection. - Restart the application or service.
- If you are using a third-party web application server, restart the application server's service. For example, if you are using Apache Tomcat, restart the Apache Tomcat service
- If you are using the bundled web application server, restart the Content Delivery database.
- On Windows, restart the ContentDelivery XML Database service.
- On Linux, log in as the root user, and type the following at a command prompt:
/etc/init.d/SDL_LiveContent restart
- Validate that garbage collection is occurring by viewing the log on the client at ContentDelivery_home/logs/wrapper.log
The success and failure messages appear like the following:
Audit GarbageCollection: status=FAIL message=audit collection does not exist Audit GarbageCollection: status=DISABLED Audit GarbageCollection: status=SUCCESS count=2For example, INFO | jvm 1 | 2010/06/01 15:15:19 | (Line: 63) Audit GarbageCollection: status=SUCCESS count=30Tip: To free up system resources and improve system performance, you should delete audits that you no longer need to reference.