Example of Scheduler Duplicate Detection

You can specify the schedule name as JobDuplicates in the CronSchedules.xmlfile. You can change the schedule name. In the Jobs node, one job per enterprise must be defined. If you have two enterprises, you need to 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 duplicate detection is com.tibco.dq.scheduler.DuplicateDetectionJob.

The following is the sample of the Scheduler Duplicate Detection process:

<CronSchedules>
  <Schedule>
    <Name>JobDuplicates</Name>
    <Jobs>
      <Job>
        <Name>SDDForXYZEnterprise</Name>
        <Triggers>
          <TriggerExpression>0 0/5 * * * ?</TriggerExpression>
        </Triggers>
        <JobDetails>
          <Description>Class name of the job to be executed. when trigger is fired. Should extend com.tibco.mdm.infrastructure.scheduler.CimSchedulerJob abstract class</Description>
          <JobDetailsClass>com.tibco.dq.scheduler.DuplicateDetectionJob</JobDetailsClass>
        </JobDetails>
        <ExecuteOnStartup>false</ExecuteOnStartup>
        <JobInput>
          <EnterpriseName>DQ</EnterpriseName>
          <UserName>DQ</UserName>
          <JobPolicy>MatchRecordRule.xml</JobPolicy>
          <JobPolicyParser>
            <Description>This class is responsible to extract the rulebase data and send them in map. should implement IRuleParser interface</Description>
            <ParserClass>com.tibco.dq.scheduler.MatchRecordRuleParser</ParserClass>
          </JobPolicyParser>
        </JobInput>
      </Job>
    </Jobs>
  </Schedule>
</CronSchedules>

The CronSchedules.xml file is always initiated on the Server start up and the specified schedules are registered with TIBCO MDM. Whenever the trigger is eligible to be fired, it will get fired.