TIBCO MDM Customization Guide - TIBCO Product Documentation

Scheduler Duplicate Detection Process| 231method is called. You can extend a job by specifying thecom.tibco.mdm.infrastructure.scheduler.CimSchedulerJob classand implement the executeJob methods by passing the context object. TheScheduler framework provides the context object to the implemented job.The context object contains the job name, trigger name, its description, andso on. The signature of the executJob method is public voidexecuteJob(JobExecutionContextjobExecutionContext) throwsMqException{…}• ExecuteOnStartup: If you specify true value, the scheduler runs the job at thestart of the application. By default, the value is false.• Job Inputs:— EnterpriseName: Specify the enterprise name on which duplicatedetection process must invoke.— UserName: Specify the user name. User name is case sensitive.— JobPolicy: Specify the XML file name that is parsed for repositoryattributes. For example, the MatchRecordRule.xml file.— ParserClass: Specify the class that parses through XML file and sends thevalues in a form of match. For example,com.tibco.dq.scheduler.MatchRecordRuleParser. If user has differentMatchRecordRule format, the parser class can be customized according tothe XML file.The job inputs are retrieved from the JobDataMap object in the Job classwith key as IRuleParser.GET_PARAMETER. A custom policy parser mustbe defined to implement IRuleParser interface.The Job Input tag is optional for other schedulers.You can customise other schedule jobs. These can be defined for any periodicexecutable task. For example, the Future Effective Date job or an email job to sendout a summary of pending work items every Friday evening. For moreinformation, refer to the samples located in the$MQ_COMMON_DIR/standard/samples/Scheduler sample folder.TIBCO MDM Customization Guide