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

Auditable Events

Auditable Events

Integration with external applications often involves complexity.
Multiple applications interact with each other, exchange data synchronously or asynchronously, use data transformations back and forth, and engage various business rules to execute business processes across applications.
To expose the details of application integration to application developers and system integrators, Informatica MDM Hub provides the ability to create an audit trail whenever:
  • an external application interacts with Informatica MDM Hub by invoking a Services Integration Framework (SIF) request. For more information, see the
    Multidomain MDM Services Integration Framework Guide
  • Informatica MDM Hub sends a message (using JMS) to a message queue for the purpose of distributing data changes to other systems.
The Informatica MDM Hub audit mechanism is optional and configurable. It tracks invocations of SIF requests that are audit-enabled, collects data about what occurred when, and provides some contextual information as to why certain actions were fired. It stores audit information in an audit log table (C_REPOS_AUDIT) that you can subsequently view using TOAD or another compatible, external data management tool.
Auditing is in effect whether metadata caching is enabled (on) or disabled (off).


We’d like to hear from you!