What is Informatica MDM Hub Architecture?

Informatica MDM Hub consists of the following core components:

Hub Store: Business data is stored and consolidated in the Hub Store. The Hub Store contains general information about all databases that are part of your Informatica MDM Hub implementation. The Hub Store resides in a supported database server environment in Informatica Master Data Management.

The Hub Store consists of following things.

All master data records for all entities in different source systems

Extensive metadata and associated rules required to discover and continuously maintain only the most reliable cell-level attributes within each master data set

The logic of the data aggregator, such as B. Merge and unmerge data

Hub Server: The Hub Server is the run-time component that manages Informatica MDM Hub core and general services. The Hub Server is a J2EE application deployed on an application server that coordinates data processing in the Hub Store and integration with external applications.

Process Server: Process Server cleans and reconciles data and runs batch jobs such as loading, recalculating BAT, and revalidating. A process server is deployed in an application server environment.

This process is linked to a cleaning engine that standardizes the data and optimizes it for reconciliation and consolidation

Hub Console: The Hub Console is the Informatica MDM Hub user interface that includes a set of tools for administrators and data stewards. Each tool allows the user to perform a specific action or set of related actions, such as: For example, creating data models, running batch jobs, configuring dataflows, configuring external application access to Informatica MDM Hub resources, and other system configuration and operational tasks.

The Hub Console is included in the Hub Server application. It can be launched on any client machine via a URL using a browser and Sun's Java Web Start.

Hierarchy Manager:

Use Hierarchy Manager to manage relationship data between different source systems. For example, data sets in the original source system often have existing hierarchies. B. Customer to Account, Sales to Account, or Product to Sales. You can view these relationships and define new relationships using the Hierarchy Manager. You can also search, navigate, and consolidate relational data.

1st Role

Role: Administrator

Tool: Model workbench > Hierarchies

Purpose: Configure the items required to view and edit data relationships in Hierarchy Manager. For example: B. Entity Types, Hierarchies, Relationship Types, Packages, and Profiles.

2nd Role

Role: Data Steward         

Tool: Model workbench > Data Steward workbench > Hierarchy Manager

Purpose: To create, manage, search, navigate, and consolidate relationship data in the Hub Store.

Security Access Manager (SAM):

Informatica Security Access Manager (SAM) is part of Informatica MDM Hub that provides comprehensive and highly granular security mechanisms that ensure that only authenticated and authorized users can access Informatica MDM Hub data, resources, and functionality. department. Security Access Manager provides a security decision-making mechanism and enables integration with security providers and third-party products that provide security services (authentication, authorization, and user profile services) to users accessing Informatica MDM Hub.

Repository Manage (RM):

Repository Manager is a Hub Console tool that enables administrators to manage metadata within an Informatica Master Data Management Hub implementation. Metadata describes various schema design and configuration components such as base objects and their columns, matching rules, sanitization functions, and mappings in the hub store.

Services Integration Framework (SIF):

It is part of Informatica MDM Hub that works with external programs and applications. SIF allows external applications to implement request/response interactions using one of the following architectural flows:

A loosely coupled web service over the SOAP protocol. Tightly coupled Java remote procedure calls based on Enterprise JavaBeans (EJB) or XML (Extensible Markup Language). Asynchronous Java Message Service (JMS) based messages. These features enable Informatica MDM Hub to support multiple data access modes, expose numerous Informatica MDM Hub data services through the SIF SDK, and generate events based on data changes in Informatica MDM Hub. This facilitates inbound and outbound integration with external applications and data sources that can be used in both synchronous mode as well as in asynchronous modes.

Informatica Data Director (IDD):

It is a records governance utility for Informatica MDM Hub that permits enterprise customers to correctly create, manage, consume, and display grasp records. Informatica Data Director (IDD) is web-primarily based totally, challenge-oriented, workflow-driven, enormously customizable and configurable, imparting a web-primarily totally based configuration wizard that creates an easy-to-use interface primarily based totally in your organization`s records model.

Integrated challenge control guarantees that each one records modifications are robotically routed to the right employees for approval before impacting to the `pleasant model of the truth.' As responsibilities are routed, the Informatica Data Director Dashboard presents enterprise customers with a view of assigned responsibilities, whilst additionally imparting a graphical view into key metrics consisting of productiveness and records best trending.

In addition, Informatica Data Director leverages Informatica's Security Access Manager (SAM) module, imparting a complete and bendy safety framework - allowing each characteristic and records stage safety. With this, clients can strike that elusive stability among open and stable with the aid of using strengthening coverage compliance and making sure get right of entry to vital information.

Informatica Data Director (IDD) enables data stewards and other business users to create following data:

Create Master Data.

Manage Master Data

Consume Master Data

Monitor Master Data

Workflow Manager:

Use Workflow Manager to register a BPM (Business Process Management) tool as a workflow engine and associate the workflow engine with an operational reference store. The default predefined workflow engine is a licensed version of ActiveVOS® Server included with Multidomain MDM. The installation process integrates this version of ActiveVOS Server with MDM Hub and Data Director, providing predefined MDM workflows, task types, and roles. The Informatica ActiveVOS workflow engine supports the below mentioned adapters.

An adapter for tasks applied to business entities through business services.

This adapter name is BE ActiveVOS. An adapter for tasks that manipulate subject areas through the SIF API. The adapter name is Informatica ActiveVOS in informatica MDM.

Entity 360 (E360) framework:

It uses a business entity model to support customized record view layouts and web-based services to user.

Once user defined your business entity models, user can create custom record view layouts for each business entity model. Record view layouts can display both master data and external data sources such as Twitter feeds or excerpts from CRM systems. Create layouts in the deployment tool and view the layouts in Informatica Data Director (IDD).

User can use business entity services to work on the master data directly. Business entity services support following Enterprises.

1. Java Beans       2. REST       3. SOAP.