Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Ways to Populate Landing Tables

Ways to Populate Landing Tables

Landing tables can be populated in the following ways:
Load Method
Description
external batch process
An ETL (Extract-Transform-Load) tool or other external process copies data from a source system to
Informatica MDM Hub
. Batch loads are external to
Informatica MDM Hub
. Only the results of the batch load are visible to
Informatica MDM Hub
in the form of populated landing tables.
This process is handled by a separate ETL tool of your choice. This ETL tool is not part of the
Informatica MDM Hub
suite of products.
real-time processing
External applications can populate landing tables in on-line, real-time mode. Such applications are not part of the
Informatica MDM Hub
suite of products.
For any given source system, the approach used depends on whether it is the most efficient—or perhaps the only—way to data from a particular source system. In addition, batch processing is often used for the initial data load (the first time that business data is loaded into the
Hub Store
), as it can be the most efficient way to populate the landing table with a large number of records.
Data in the landing tables cannot be deleted until after the load process for the base object has been executed and completed successfully.

0 COMMENTS

We’d like to hear from you!