About the Purge/Archive wizards |
In a production application, work item data volume can grow to a size where hundreds of megabytes of database storage is required. The Purge/Archive wizards enable you to use an agent to automatically delete old work item data from the respective tables and/or store them in ZIP archive files. Purging and archiving old work items and their related history and attachment records helps maintain system performance by reducing database processing demands.
Archiving work item data enables you to retrieve them if needed for audits or for backups. Note the following:
You use the Purge/Archive wizard to set up the agent activity in two phases:
Phase 1: Configure the activity — Define the dataset that will be purged/archived. The dataset comprises a work pool in your application, and a set of work types (classes), folders, and covers within the work pool. The dataset is also qualified by the age of resolved work items to be purged/archived. Each configuration is an instance in class Data-Admin-ArchiveSettings.
Phase 2: Schedule the activity — For each cycle you specify:
At the defined cycle start time, the purge/archive agent first populates an archive ZIP file with the work items and their data as defined in Step 1. The agent then deletes the table data. Although the work items are purge/archived, the work item ID is left unchanged, to allow restoration or archived wok items without affecting current work items.
The ZIP files created by the wizard uses the following naming convention:
<workpool name_dataset name_ file creation date_runn >
for example:
MyCo-Classgroup_AlphaPurge_20070409T22440_0.zip
A run value of 0 (zero) designates the first run.
The ZIP files are stored in the PRPC system temporary directory configured for your installation.
Before you use the Purge/Archive Wizard, do the following:
Indexes created for work items are deleted but not archived. The indexes are recreated when the work items are recovered from the archive. For example, work party indexes (table pc_index_workparty
) are purged but not archived. When the work item is recovered, the work party index is recreated.
Two wizards comprise the Purge/Archive wizard:
Configuration wizard: Select > System > Tools > Purge/Archive Configure when you are:
Scheduling wizard: Select > System > Tools > Purge/Archive Schedule when you are:
Click the Help button () on any form for information about that form.
To retrieve archived work items in your archive system, select> Application > Import & Export > Import.
By default, a setting in prconfig.xml
limits the size of an imported file to 25MB. To upload files that exceed this limit, you can either change the setting or use a file transfer tool such as FTP. For more information, see PDN article How to import large archive .zip files using the Import Rules/Data tool.
As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.
Before using the wizard in a full-scale production system, it is strongly recommended that you test the wizard as follows:
pc_work
table and from the tables listed above in the preceding Prerequisites section. You can use Find by ID to verify that the items are not available.pc_link_folder
. Purge the folder and then verify that the entry in the link table is deleted.By default, only operators who hold the PegaRULES:SysAdm4 role can use these wizard.
To make this available to others.
archive tools | |
Working with the PegaRULES database — Tables for work items Completing the Import Zip file option Understanding the Pega-ImportExport agent |