Purge Job Scheduler

To initiate purge from Job Scheduler, you need to define the purge job policy which is invoked from the scheduler.

The data source purge is supported from scheduler. The purge job supports all execution modes except event and record modes. You can specify the following inputs in the purge job policy:

  • Scope - applies to enterprise scope only. If specified, it should be set to ALL. If specified, all enterprises are considered in scope.
  • PurgeExecMode
  • VersionsToRetain
  • RetentionDays
  • RepositoryName
  • DatasourceName
  • Interval
  • Hints

The schema for the PurgeJobPolicy.xml file is specified in the $MQ_HOME\schema\config\scheduler\1.0\PurgeJobPolicy.xsd folder.

The PurgeJobPolicy.xml file is located in the $MQ_HOME\Config folder. The contents of PurgeJobPolicy.xml is as follows: 

<JobPolicy>
  <PurgeJobPolicy>
    <Scope>ALL</Scope>
    <PurgeExecMode>history</PurgeExecMode>
    <!--RepositoryName>retail</RepositoryName-->
    <!--VersionsToRetain>3</VersionsToRetain-->
    <!--DatasourceName>MYDATASOURCE</DatasourceName-->
    <!--Interval>10</Interval-->
    <!--Hints>FG</Hints-->
    <RetentionDays>365</RetentionDays>
  </PurgeJobPolicy>
</JobPolicy>
Note:
  • The combination of <Scope>ALL</Scope> and <RepositoryName>ALL</RepositoryName> parameters is not supported when the purge job policy is invoked from the scheduler.
  • The Interval input parameter supports only the recordversions purge execution mode.
  • The Hints input parameter supports only the repository and record purge execution modes.
  • StartDate and EndDate parameters are not supported.