Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Load Process User Exits

Load Process User Exits

The load process can call the post-load user exit.
The post-load user exit is called if the loaded count of the job is greater than 0. The post-load user exit runs after the MDM Hub processes each block instead of at the end of the batch process. The post-load user exit runs for each record in the block after the MDM Hub processes the updates and inserts for all records in the block.
The following image shows the load process and the user exits that the load process can call:
The post-load user exit runs within the load process in the following sequence:
  1. The MDM Hub registers the load job.
  2. The MDM Hub updates or inserts the records for the first block.
  3. The post-load user exit runs for each record in the block.
  4. The MDM Hub commits the changes.
  5. If the MDM Hub has more blocks to load, the process returns to step 2 to process the next block.
  6. The load job ends after the MDM Hub loads all blocks.
  7. If strip_on_load_ind equals 1, the tokenize job generates match tokens required to perform fuzzy matching.


We’d like to hear from you!