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

Using Hard Delete Detection within User Exits

You can implement the Post Landing and Post Stage user exits to detect hard deleted records in source systems. To perform a direct hard delete detection you need the Post Landing user exit. To perform a consensus hard delete detection you need both Post Landing and Post Stage user exits.

Create an instance of the HardDeleteDetection class to use within the implementation of the Post Landing user exit.

The HardDeleteDetection class is available in

mdm-ue.jar

, which is in the following directory:

On Windows.

<infamdm installation directory>\hub\server\lib

On UNIX.

<infamdm installation directory>/hub/server/lib

Add the following lines to the Java code for the Post Landing or Post Stage user exits to detect hard deleted records:

For Post Landing user exit.

public void processUserExit(UserExitContext userExitContext, String stagingTableName, String landingTableName, String previousLandingTableName)
						throws Exception
{ 
	HardDeleteDetection hdd = new HardDeleteDetection(userExitContext.getBatchJobRowid(), stagingTableName);
	hdd.startHardDeleteDetection(userExitContext.getDBConnection());
}

For Post Stage user exit.

public void processUserExit(UserExitContext userExitContext, String stagingTableName, String landingTableName, String previousLandingTableName)
						throws Exception
{
	ConsensusFlagUpdate consensusProcess = new ConsensusFlagUpdate(userExitContext.getBatchJobRowid(), stagingTableName);
	consensusProcess.startConsensusFlagUpdate(userExitContext.getDBConnection());
}

Package the user exits JAR and upload it to the

MDM Hub

Run the stage job.

The

MDM Hub

supplies input parameter values to detect hard deletes when the stage job calls the user exit.

Hard Delete Detection

Implementing the User Exit JAR File

Uploading User Exits to the MDM Hub

Download Guide

Watch

Comments