MDM Implementation Styles with Boomi Master Data Hub

Blog Post created by teemu_hyle Employee on Jun 3, 2018

With Dell Boomi Master Data Hub (Hub) you can implement different MDM architectural styles like Consolidation, Centralized, Coexistence and Registry.


Consolidation style

Consolidation is a typical starting point to implement MDM solution. In Consolidation there are systems that contribute the data to the MDM repository. These systems can be either on-premise application like Oracle Database or SAP R/3, or cloud based application like Salesforce.com or ServiceNow.




Concepts: Source

In MDM implementations there are systems that are data providers or data consumers. In Boomi these systems are called as source.
When a source is attached to a data model it is configured to be a data provider and/or data consumer. A source that is a data provider contributes data and a source that is a data consumer accept channel updates.


Data Model Sources

After configuring and deploying a data model to a repository you attach source systems to the model.
Below is an example where three systems is attached to the Customer model that is in repository called Hub Repository.



Integration implementation

For each system that contribute data to the model there is created an integration process.
Below is an example that send SAP Customer (DEBMAS) records to the Hub.


Integration process in Boomi:

Customer upsert operation to the Hub from SAP :

Data synchronization

Below is an example golden record. The record is from SAP and SAP ID (KUNNR) is shown as Entity ID.

The record is not yet consolidated or distributed with other systems (MySQL and and Salesforce.com).



Registry style

In registry style implementation the master data exists in source systems.
Boomi Hub match functionality can be used in registry style implementation to identify duplicate records.
Source system IDs, fields that are used for matching and potentially reference/link to the source data are stored in Boomi Hub.