Scheduler Examples

The scheduler process samples are listed in the CronSchedules.xml file located at $MQ_HOME\config folder. If you want to use any one of the samples, you can uncomment the sample.

The following table lists the samples of the scheduler processes:
Scheduler Process Name Description
Scheduler Duplicate Detection Detects duplicate records in an existing repository.

The CronSchedules.xml file is always initiated on the server start up and the specified schedules are registered with ibi MDM. Based on the trigger expression, the job is invoked.

Purge RecordSyncLog Deletes the record synchronization log entries.

The following table lists the input parameters that must be specified in the <JobInput> tag:

Purge Scheduler Schedules a purge of specific enterprise.
NoFS Purge Scheduler Identifies and deletes the older work and temporary files from the database file system. By default, the value is set to false for Execute on startup. This feature works in conjuction with the Temporary files expiration interval configuration property. For information, see Expiration Interval for Deleting Temporary Files.
Right To Be Forgotten Permanently deletes the marked records from one or more repositories based on the attribute name and its value. For information, see Right to Be Forgotten.
Index Entity Checkpoint By using the Index Entity Checkpoint, you can schedule a job to checkpoint the provided list of ibi Patterns - Search tables or index entities when the trigger is fired. Checkpoint signifies that the ibi Patterns - Search tables are saved to a permanent storage device, and the saved copies can be quickly restored at a later time on a periodic intervals. As a result of checkpoint, you can see the data files getting created in the specified checkpoint directory.

To checkpoint, the ibi Patterns - Search server must have been started with check pointing or restore enabled (use the -R option).

  • -R restoredir: enables checkpoint or restore using the indicated directory as the checkpoint or restore directory. The indicated directory must already exist. If this argument is not specified, the checkpoint feature is disabled.
  • -A Auto restore: restores all checkpointed tables in the restore directory. Restores upon start up.

  • -a common-dir: restores from a common directory. Upon start up all checkpointed tables in the indicated directory are restored. Checkpointing is not enabled by this option, although it may be used with the -R and -A options.

For more information, see "CheckpointWorkflow Activity" in ibi MDM Workflow Reference.

Note: The Index Entity Checkpoint scheduler job has been deprecated. You can now use the Data Durability feature of ibi Patterns - Search. The feature automatically checkpoints the ibi Patterns - Search tables when the server is restarted. You do not need to enable the Checkpoint or Restore feature from ibi MDM.
For information, see the "Durable Table" section in the ibi Patterns - Search Concept Guide.
Fast Cache Update Updates the golden copy record into the fast cache. Ensure that you have set the value of the Golden Copy Cache Update Immediately or Later on by Scheduler property to Scheduler.
Data Quality Score Processes the verification of the quality attributes data and saves the attribute score summary in the database.
Hierarchy Lock Expiry Unlocks the hierarchy locks that are expired and are no more valid.

The hierarchy locks are valid until the session time out of the application server. After the session times out, the previously set hierarchy locks become invalid. For example, if any hierarchy remains locked for some reason (which is identified by the server as invalid lock), then you can unlock the hierarchy (if you are owner of the lock.) Alternatively, another user who has permissions to release the locks on hierarchies owned by you can also unlock the hierarchy. Note that if a hierarchy is pending in event and a work item is generated, then such locks are not removed by this scheduler as they are still valid locks.

Caution: If a hierarchy is pending in the event and a work item is generated, then the hierarchy remains in the locked state. Such hierarchy locks are not removed by the hierarchy lock expiry scheduler job as these locks are still valid.

You can also schedule the hierarchy lock expiry job to unlock the invalid locks set on the hierarchy. By default, expired hierarchy locks are unlocked after 24 hours. To change the default value, edit the <JobInputParam name="ExpiryIntervalInHrs">24</JobInputParam> parameter.

For information about locking and unlocking hierarchy, see the "Locking and Unlocking Hierarchy" section in ibi MDM User Guide.

Hierarchy Linkage Cleanup Cleans the hierarchy record linkage data that is linked to the deleted records.

When you delete a record, record linkages are not automatically deleted from the hierarchy. To delete these record linkages, run the linkage cleanup scheduler job after you delete the record.

Automatic Hierarchy Scheduler

Processes the confirmed records created after the last update to the hierarchy. The scheduler searches for the golden copy records (which are created, modified, or deleted after the last modification time of an automatic hierarchy) by using the product logs and processes them.

The records are processed on each repository. If a repository is found to be deleted, then scheduler marks the hierarchy as inactive.
Learn Collect Pairs Schedule

Extracts new record pairs for AI Matching. After you schedule a job, record pairs are collected automatically at the specified interval.

  • Record pairs are collected only for the activity projects that already have the features defined.
  • Any projects that do not yet have features defined are skipped during record pair collection.
  • You can click Refresh from the AI Matching UI to see any changes from the scheduled record pair collection.
  • You can turn off the scheduled job from the AI Matching UI to temporarily suspend the scheduled pair collection for the selected activity project.
Note: If the AutoDeploy property is set to false in the LearnConfig.xml file, then the scheduler job is created but it does not run and collect pairs.

For information about the common properties defined in the CronSchedules.xml file, see Job Type Common Parameters.