Introduction to Integration | ||
---|---|---|
Previous | Next | |
Preface | External Load |
Semarchy Convergence for MDM is designed to support any kind of Enterprise Master Data Management initiative. It brings an extreme flexibility for defining and implementing master data models and releasing them to production. The platform can be used as the target deployment point for all master data of your enterprise or in conjunction with existing data hubs to contribute to data transparency and quality with federated governance processes. Its powerful and intuitive environment covers all use cases for setting up a successful master data governance strategy.
Semarchy Convergence for MDM is based on a coherent set of features for all Master Data Management projects.
Semarchy Convergence for MDM certifies golden data from source applications' data and allows applications to consume this golden data.
Integration with Convergence for MDM is performed in several ways:
In the context of integration, we refer to applications publishing source data into the hub as
Publishers.
We also refer to application consuming golden data from the hub as
Consumers.
These roles are not exclusive. An application can publish data into the MDM hub and consume certified golden data from the hub to update its records.
For example, a business intelligence application is typically a consumer-only as it consumes only golden records for reporting purposes. An operational application may publish its
contact information to the MDM hub for certification and update its contact information with the certified golden records.
This term refers to the original application from which the data originates, and not necessarily to the middleware tool or user-designed program actually doing the data movement. The publisher is typically an operational application such as a Customer Relationship Management (CRM), a Product Lifecycle Management (PLM) or an Enterprise Resource Planner (ERP).
A middleware tool may be an Extract-Transform-Load (ETL), Enterprise Service Bus (ESB) or any other data integration product. It may also be a user-designed program or script implemented in SQL, Java, etc. The middleware tool or user-designed program communicates with the publisher to extract data and communicates with the MDM Hub using the publishing methods described in this guide to load this data.
For the rest of this guide, we will refer to the middleware tool or user-defined product used for publishing data as the middleware.
Similarly to the publisher, this term refers to the applications consuming data from the hub. This consumption usually takes place via a middleware tool or a user-designed program, and uses the consumption methods described in this guide.
For the rest of this guide, we will refer to the middleware tool or user-defined product used for consuming data as the middleware.
A deployed hub has several components involved in the integration mechanism.
The platform provides a central interface for managing external loads (publishing transactions).
These services include:
These services are accessed for managing the external load transaction used to publish data into the hub.
The database schema of a data location stores a set of tables that contain the hub data.
This schema contains the landing (or staging) tables used to publish data into the hub. It contains also the golden records tables and the intermediate tables handled by the integration job that create golden records from the source records. There is a single data structure for the entire hub, and a single set of tables for each entity regardless of the model edition or data edition.
The data location schema is accessed for integration purposes to:
An integration job is a sequence of tasks used to certify golden data for a group of entities. Each data model edition deployed in the data location has integration several jobs definitions attached to it. Each of these job definitions is designed to certify data for a group of entities.
Integration jobs definitions as well as integration job logs are stored in the repository
For example, a multi-domain hub contains entities for the PARTY domain and for the PRODUCTS domain, and has two integration jobs definition:
Integration jobs are triggered when source data has been loaded in the landing tables and is submitted for golden data certification.
The Data Services provide access to the data editions stored in the data locations attached to an application instance. These data services are generated per data edition, and their capabilities depend on the underlying deployed model edition.
The data services for each data edition include:
Previous | Top | Next |
Preface | External Load |