A schema that stores and consolidates business data for the

MDM Hub

. Contains the

MDM Hub

environment configuration settings, such as user accounts, security configuration,

Operational Reference Store

registry, and message queue settings. You can access and manage an

Operational Reference Store

from an

MDM Hub Master Database

. The default name of an

MDM Hub Master Database

is CMX_SYSTEM, but you can use a custom name.

A schema that stores and consolidates business data for the

MDM Hub

. Contains the master data, content metadata, and the rules to process and manage the master data. You can configure separate

Operational Reference Store

databases for different geographies, different organizational departments, and for the development and production environments. You can distribute

Operational Reference Store

databases across multiple server machines. The default name of an

Operational Reference Store

is CMX_ORS.

A J2EE application that you deploy on an application server. The

Hub Server

processes data stored within the

MDM Hub

and integrates the

MDM Hub

with external applications. The

Hub Server

manages core and common services for the

MDM Hub

.

A J2EE application that you deploy on an application server. The

Process Server

processes batch jobs such as load, recalculate BVT, and revalidate, and performs data cleansing and match operations. The

Process Server

interfaces with the cleanse engine that you configure to standardize and optimize data for match and consolidation.

A tool to build business entity models, and to configure the Entity 360 framework for

Data Director

. After you build business entity models, you can publish the configuration to the

MDM Hub

.

A business process management (BPM) tool that is required internally by the

MDM Hub

for processing data.

Informatica ActiveVOS

supports automated business processes, including change-approval processes for data. You can also use

Informatica ActiveVOS

to ensure that changes to master data undergo a review-and-approval process before inclusion in the best version of the truth (BVT) records.

A user interface to master and manage the data that is stored in the

MDM Hub

. In IDD, data is organized by business entities, such as customers, suppliers, and employees. Business entities are data groups that have significance for organizations.

Set of samples, applications, and utilities to integrate the

MDM Hub

into your applications and workflows. You can select the

Resource Kit

components that you want to install.

An environment that comprises the Informatica services and Informatica clients that you use to cleanse and transfer source data to the MDM Hub. You can use

Informatica platform

instead of the cleanse functions available in the MDM Hub to cleanse data.

A data security tool that operates between the

MDM Hub

and databases to prevent unauthorized access to sensitive information.

Dynamic Data Masking

intercepts requests sent to databases and applies data masking rules to the request to mask the data before it is sent back to the

MDM Hub

.

Applicable to Informatica Data Director (IDD) based on the subject area data model only.