Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Resource Kit Installation
  12. Resource Kit Post-Installation Tasks
  13. Troubleshooting the MDM Hub
  14. Uninstallation

Installation Guide for IBM DB2 with Red Hat JBoss

Installation Guide for IBM DB2 with Red Hat JBoss

Multidomain MDM Installation

Multidomain MDM Installation

Multidomain MDM
is a master data management solution that enhances data reliability and data maintenance procedures.
Multidomain MDM
is also referred to as the
MDM Hub
. You can access the
MDM Hub
features through the
Hub Console
.
The
MDM Hub
consists of multiple components. You can install the MDM Hub in the graphical mode, the console mode, or the silent mode.

Core Components

The following table describes the core installation components:
Component
Description
MDM Hub Master Database
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.
You can create multiple MDM Hub Master Databases, each with its own set of Operational Reference Stores, in the same database instance.
Operational Reference Store
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.
Hub Server
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
.
Process Server
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.
Provisioning tool
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
.
Informatica ActiveVOS
®
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.
When you install
ActiveVOS Server
as part of the
Hub Server
installation, you install the
ActiveVOS Server
,
ActiveVOS Console
, and Process Central. Also, you install predefined MDM workflows, tasks, and roles.
Data Director
(IDD)
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.

Optional Components

The following table describes the optional installation components:
Component
Description
Resource Kit
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.
Informatica platform
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.
When you install the Informatica platform as part of the
Hub Server
installation, you install the Data Integration Service, Model Repository Service, and Informatica Developer (the Developer tool).
Dynamic Data Masking
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
.
Informatica Data Controls (IDC)
Applicable to Informatica Data Director (IDD) based on the subject area data model only.
IDC is a set of user interface controls that expose the MDM Hub data in third-party applications that are used by business users.
Zero Downtime (ZDT) module
A module to ensure that applications have access to data in the
MDM Hub
during the
MDM Hub
upgrade. In a ZDT environment, you duplicate the databases: source databases and target databases. During the
MDM Hub
upgrade, the ZDT module replicates the data changes in the source databases to the target databases.
To buy the ZDT module, contact your Informatica sales representative. For information about installing a zero downtime environment, see the
Multidomain MDM Zero Downtime Installation Guide
for the database.