The Avoka Purge Tool for LiveCycle ES enables you to free up your database and file system which would otherwise continually store excess information associated with processes that have completed.
Warning
The Avoka Purge Tool has been thoroughly tested on our own systems, and we find it that it effectively removes redundant data without any effect on the operation of the LiveCycle system. However, the Purge Tool will permanently remove data from your database and your Global Storage Directory (GSD), and this data can not be recovered. Use the Purge Tool at your own risk. We strongly recommend that you
a) verify to your own satisfaction, on a non-production system, that the Purge Tool behaves according to your expectation, and
b) that you backup your database/GSD prior to running the Purge Tool on any system.
Avoka provides no warranty, implied or stated, that your system will not be affected in some way after purging. Avoka will accept no responsibility for any errors or problems which result or appear to result from running the Purge Tool.
Purge Events
LiveCycle ES added a new capability for sending events within the process engine. Both internal and exterally defined events can be thrown and received. There is a table in the database which stores event information, and this table is not automatically purged by LiveCycle.
The Purge Tool deletes:
- delivered events for which all notifications are delivered
- new events that have no associated notifications.
It frees up space in the database table 'tb_evt_event'.
Purging events is benign - it removes data which is no longer needed.
Purge Job Instances
A job instance is a created when a long-lived process is invoked. The job instance id provides a way to track the completion of a long-lived process. The job instance also stores all the data passed to the process when the job is invoked as a document in the Global Storage Directory. Job instances are not automatically purged when the job is completed or terminated.
The Purge Tool Deletes completed or terminated jobs and documents associated with those job instances.
It frees up space in the database table 'tb_job_instance', and in the Global Storage Directory.
Purging job instances is benign - it removes data which is no longer needed.
Purge Task Attachments
End-users using Workspace may optionally store attachments when they complete a task in their inbox. The attachments are stored either in a database table, or if they exceed the maximum inline document size (specified in adminui), they are stored permanently in the Global Storage directory. These attachments may be any size that the user chooses to attach. The attachments may also be copied (based on User Task component settings) to subsequent User Task steps in the process. This can result in very high database and/or Global Storage Directory growth.
The Purge Tool replaces content of attachments for completed or terminated tasks with empty data, while keeping the associated file name for reference.
It frees up space in the database table 'tb_task_attachment', and any associated documents in the Global Storage Directory.
Important: removing task attachments is NOT benign. It will permanently remove the task attachments. These attachments are not recoverable, they are permanently deleted. If you use this option, any attachments will still be visible within the Task Tracking tab, but will have zero size and zero content. If you wish to retain an archival copy of these attachments, you must do so by copying the attachments to secondary storage location prior to purging.
Avoka Purge Tool for Adobe LiveCycle ES
