Preface
Part 1: Introduction
Part 2: Configuring Hub Console Tools
- Configuring Access to Hub Console Tools
- Implementing Custom Buttons in Hub Console Tools
Part 3: Building the Data Model
Part 4: Configuring the Data Flow
Part 5: Executing Informatica MDM Hub Processes
- Using Batch Jobs
- User Exits
Part 6: Configuring Application Access
Appendix A: MDM Hub Properties
Appendix B: Viewing Configuration Details
Appendix C: Row-level Locking
Appendix D: MDM Hub Logging
Appendix E: Table Partitioning
- Support for Table Partitioning
Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
Appendix G: Glossary
- Glossary of Terms

Configuration Guide

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

Back Next

Input Table Population

Before you run an External Match job, you must populate the EMI table with records to match against the records in the base object. The process of loading data into an EMI table is external to the

MDM Hub

. Use a data loading tool that works with your database environment.

When you populate the EMI table, you must supply data for at least one of the system columns to help link back from the _EMI table. The C_
BaseObject
_EMI table must also contain flat records with unique source keys and no foreign keys to other tables.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Input Table Population

Input Table Population