After deploying Process Automation, the Archive and Purge feature needs to be enabled for overall health of the Orchestrator. The single largest contributor to performance issues within Process Automation is directly related to not Archiving and Purging completed instances. As the number of rows grow in both the Runtime database, and the Runtime Archive database tables, overall performance decreases, to the point where the engine can no longer complete instance activity.
It is vital ensure the runtime and archive database tables are kept to as small as possible. To this effect we recommend being as aggressive as possible with the archive and purge settings.
All Process Automation 4.x releases
Instructions for enabling Archive and Purge for completed Processes:
Log into Process Automation as Pam Admin.
To ensure the overall runtime database is kept to as small a size as
possible we recommend being as aggressive as possible with the archive
and purge settings.
For example if you determine that you need 7 days worth of historical process data you could set Minimum Number of Days of Process History to 1, and Option to Purge Archived Data to Purge Daily, and Number of Days to Keep Archived Data to 6;
Or you could set Days of Process History to 3 and Option to Purge to 4; or you could set Minimum Number of Days of Process History to 7, and set Option to Purge Archived Data to Purge Data without archiving, which would simply Purge the process completely after 7 days.
There are a variety of additional configuration options that can be used to ensure that there is a minimum of instance history kept for review, while ensuring that the majority of instances are quickly archived and purged from the database.
1. Minimum Number of Days of Process History
Default is 2 days. This is the setting that tells PAM how long to wait after an instance has completed before Archiving. In 4.2 Sp02 and later, instances are rolled up and moved to the archive table immediately upon completion. This setting now controls how long that completed instance remains in the Current view, and indicates to PAM how long it should wait before moving the instancing into the purging engine.
2. Minimum Number of Failed Instances
3. Minimum Number of Finished (Completed, Aborted) Instances
Default for both is 0. These settings allow you to override the other time based Archive policies forcing a certain number of failed, Completed, or Aborted, instances to remain in the Current view - this would ensure an admin can review if necessary.
4. Option to Purge Archived Data
What happens to Archived data - default is Do Not Purge Archived Data meaning that even once archived the instance will remain until manually purged. We recommend the 'Purge Archived Data Daily' option.
5. Number of Days to Keep Archived Data
Default is 10. Indicates how long after an instance has been marked as archived, and displayed under the Archive area of the Operations tab before it is purged entirely from the database.
Please note, these settings are applied at run-time. The configuration at the time an instance is initiated is stored within that Instance run and will not be updated if the configuration changes later.
Changes to the policies will only be applied to new instance runs.
If your Process Automation engine has been running for without the Archive and Purge configured, you will need to use the Right Click / Archive option from the Operations view to push instances into the Archive:
And then on the Configuration> Orchestrator > Policies Tab, use the Delete Archived Instances button to delete the existing Archived Instances: