Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

User Exits Overview

A user exit is custom Java code that you develop that runs at specific points in the batch or Services Integration Framework (SIF) API processes to extend the functionality of

MDM Hub

exits regular MDM Hub processing to run code that users develop.

For example, you can use a post-landing user exit to perform pre-cleansing on addresses before the delta detection process.

You upload all the user exits to

MDM Hub

in a single JAR file. You can upload one JAR file to each Operational Reference Store.

MDM Hub

supplies input parameter values when it calls a user exit. Follow the guidelines for implementing user exits to ensure that the user exits do not unnecessarily decrease performance.

You can implement user exits in the following MDM Hub processes:

Stage Process: The stage process moves data from a landing table to a staging table associated with a base object. You can run the following user exits during the stage process:
Post-landing user exit. Use the post-landing user exit to refine data in a landing table after you populate the landing table through an ETL process.
Pre-stage user exit. Use a pre-stage user exit to perform custom handling of delta processes.
Post-stage user exit. Use a post-stage user exit to perform custom processing at the end of a stage job.

Load Process: The load process moves data from a staging table to a base object table. You can run the following user exit during the load process:
Post-load user exit. Use a post-load user exit to perform custom processing after the load process.
Match Process: The match process identifies base object records that are potential duplicates. You can run the following user exits during the match process:
Pre-match user exit. Use a pre-match user exit to perform custom processing before the match process.
Post-match user exit. Use a post-match user exit to perform custom processing on the match table.
Merge Process: The merge process consolidates duplicate base object records into a single master base object record. You run the following user exit during the merge process:
Post-merge user exit. Use a post-merge user exit to perform custom processing after the merge process.
Unmerge Process: The unmerge process unmerges a single master base object record into the individual base object records that existed before the records were merged. You can run the following user exits during the unmerge process:
Pre-unmerge user exit. Use a pre-unmerge user exit to perform custom processing before the unmerge process.
Post-unmerge user exit. Use a post-unmerge user exit to perform custom processing after the unmerge process.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

User Exits Overview

User Exits Overview