Example of Purge Scheduler

You can specify the schedule name as PurgeScheduler in the CronSchedules.xml file. You can change the schedule name. In the Jobs node, one job per enterprise must be defined. If you have two enterprises, you must specify two Job nodes.

A Job node can contain more than one job nodes. Each Job node must specify the Job class, the trigger expressions, and a JobPolicy type. The Job class for purge scheduler is com.tibco.mdm.purge.PurgeScheduler.

The following is the sample of the Purge Scheduler process:

<Schedule>
        <Name>PurgeHistory</Name>
        <Jobs>
            <Job>
                <Name>PurgeHistory</Name>
                <Triggers>
                    <TriggerExpression>0 0 0 * * ?</TriggerExpression>
                </Triggers>
                <JobDetails>
                    <Description>Job class name of the job to be executed</Description>
                    <JobDetailsClass>com.tibco.mdm.purge.PurgeScheduler</JobDetailsClass>
                </JobDetails>
                <ExecuteOnStartup>false</ExecuteOnStartup>
                <JobInput>
                    <UserName>test</UserName>
                    <EnterpriseName>test</EnterpriseName>
					<JobPolicy>PurgeJobPolicy.xml</JobPolicy>
                    <JobPolicyParser>
                        <Description>This class is responsible to extract the purge inputs</Description>
                        <ParserClass>com.tibco.mdm.purge.PurgeJobPolicy</ParserClass>
                    </JobPolicyParser>
                </JobInput>
            </Job>
        </Jobs>
    </Schedule>