Starting External Purge for a Certified Container installation

You can start an external purge by enabling and configuring external purge options in the Helm chart during installation. For more information, see Configuring Certified Containers.

  1. Schedule external purge, which is run as a job, to execute for a desired duration on a given date/time. You can schedule and run only one instance of the job at a time. You can use node affinity configuration to isolate and run the job on a specified node that does not host other application pods.
    Note: In a cluster environment, if Document Storage is set to File System, enable the appDocumentsPVC Persistent Volume claim in values.yaml and provision a persistent volume for document storage matching the storage class and labels with the appDocumentsPVC. For more information, see Setting up PersistenceVolumes.
  2. Disable the default purge service. Click Deployment > Schedules, search for PurgeService, and then clear the Enabled checkbox for PurgeService.
    Note: If you have customized the Schedule_PurgeService business process, you need to add the customized code to the new Schedule_PurgeService business process. The new Schedule_PurgeService business process includes a warning message about running external purge while the scheduled new purge is enabled.
  3. Turn off the Important Schedules are Disabled email notifications by adding the following line to the customer_overrides.properties file. This removes the Purge Service SQL query for the schedule. 
    resourceMonitor.ScheduleMonitor.propertyValue.1=SELECT STATUS, SERVICENAME FROM SCHEDULE 
WHERE SERVICENAME IN ('BackupService','IndexBusinessProcessService','AssociateBPsToDocs','BPRecovery','BPLinkagePurgeService')
  4. Set .Values.Purge.enabled = true in values.yaml for the Certified Container Helm charts to enable the purge job. You need to specify the purge Docker image details and a schedule to start the job. For more information, see Configuring Certified Containers.