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

Elements in an XML Message

Elements in an XML Message

The following table describes the elements in an XML message.
Root Node
Root node in the XML message.
Event Metadata  
Root node for event metadata.
Unique ID for siperianEvent messages.
Type of event with one of the following values:
  • Insert
  • Update
  • Update XREF
  • Accept as Unique
  • Merge
  • Unmerge
  • Merge Update
UID of the base object affected by this action.
UID of the package associated with this action.
Date/time when this message was generated.
ID of the Operational Reference Store (ORS) associated with this event.
UID of the rule that triggered the event that generated this message.
Event Details  
Root node for event details.
Name of the source system associated with this event.
Value of the PKEY_SRC_OBJECT associated with this event.
Date/time when the event was generated.
RowID of the base object record that was affected by the event.
Root node of a cross-reference record affected by this event.
System name of the cross-reference record affected by this event.
PKEY_SRC_OBJECT of the cross-reference record affected by this event.
Name of the secure package associated with this event.
Each column in the package is represented by an element in the XML file. Examples: rowidObject and consolidationInd. Defined in the ORS-specific XSD that is generated using the JMS Event Schema Manager tool.
List of ROWID_OBJECT values for the losing records in the merge. This field is included in messages for Merge events only.


We’d like to hear from you!