Architecture and concepts for InfoSphere MDM

InfoSphere® MDM provides a unified architecture that works with various types of master data. Common services, a unified workbench, and customizable applications are at the core of the architecture.

Standard and Advanced Editions

The following deployment diagram shows how the clients, the application server, the MDM operational server, and the database server can be deployed in your environment. To start, the data that you want to master is stored in source systems. You perform most of your master data tasks within the clients, such as the Workbench, InfoSphere MDM Inspector, or your own custom-built clients. Those clients connect to the application server that hosts the operational server, where most MDM processing occurs. Finally, the application server uses a database server to host the MDM database and other databases that are applicable to optional components.

The diagram shows four computer systems: clients, application server, database server, and source systems. The InfoSphere MDM clients are on the client. The MDM operational server is on the application server. The MDM database and supplemental databases are on the database server. The data sources are on the source systems.
The primary components are defined as follows:
Operational server
The software that provides services for managing and taking action on master data. The operational server includes the data models, business rules, and functions that support entity management, security, auditing, and event detection capabilities. Examples of functions that support entity management include data loads, cleansing, linkage, and de-duplication. Previously referred to as master data engine in Initiate Master Data Service® and MDM Hub or MDM Server in InfoSphere MDM Server.
Application server
A server program in a distributed network that provides the execution environment for an application program.
Database server or DBMS
A software program that uses a database manager to provide database services to other software programs or computers.
Software programs that request services from the operational server. The following clients provide entry points to your key MDM activities.
Table 1. Client applications
MDM activities Clients Primary users
Configuration and customization of your MDM solution
  • InfoSphere MDM blueprints in InfoSphere Blueprint Director
  • InfoSphere MDM Workbench
Architect, Solution Developer, Data Steward Lead
Data governance and stewardship
  • IBM Stewardship Center
  • IBM® Cognos® reports
  • InfoSphere MDM Enterprise Viewer
  • Flexible search
  • InfoSphere MDM Inspector
  • InfoSphere MDM Pair Manager
  • InfoSphere MDM Reference Data Management Hub
  • InfoSphere MDM Unstructured Text Correlation
  • InfoSphere MDM Web Reports
Some stewardship activities are configured in InfoSphere MDM Workbench.
Data Steward, Business Analyst, Business User, Application User
  • InfoSphere MDM Administration UI
  • WebSphere® Administrative Console
System Administrator, Database Administrator
  • InfoSphere MDM Application Toolkit
  • InfoSphere MDM Batch Console (sample)
  • InfoSphere MDM for IBM Business Process Manager
  • InfoSphere MDM Workbench
  • SDKs, APIs
Solution Developer, Application Developer

For a more detailed look at the architecture, the following diagram shows the components that form the whole architecture:

The architectural diagram shows the three components: user interfaces (clients, APIs, toolkit), the application server that holds the MDM operational server and its services, and the database server (the MDM database and artifacts).

Collaborative Edition

For the Collaborative Edition, a component-based architecture can consist of a two-tier or three-tier configuration. The Collaborative Edition has these components: core components, integration components, and collaboration components.

The core components are as follows:
  • An API layer
  • A business object layer
  • An infrastructure layer
  • A storage layer
The integration components are as follows:
  • Custom tools
  • Import-export
  • Portal framework
  • Web services
The collaboration components are as follows:
  • Data authoring UI
  • Import-export
  • Workflow engine