If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

MDM Configuration

These articles are intended to provide a detailed description of the configuration files and configuration possibilities in general.

MDM consists of the following artifacts:

Data Quality Center (DQC) core. DQC features are fully available for MDM as well.
MDM Engine. Adds integrated framework based on Ataccama best practices. Configuration is in the New Matching Engine (NME) - an engine capable of handling large volume loads as well as online queries and modifications.
1. MDM Engine Configuration File. See MDM Engine Configuration File.
2. Persistent Storage. Tables and columns including pseudocolumns. See Persistence Layer.
MDM model project templates. Definitions written in Advanced Metadata Editor (AME), which is represented in the Model Explorer.
1. Sample projects suitable for the matching engine.
  1. General CDI project. A sample project including a small data set.
  2. Blank general MDM project. Project structure without content.
Web Console. Enables to administer MDM via a graphical user interface. See MDM Admin Center Extras for additional engine component items added into the standard WebConsole.

MDM can be extended by a variety of Ataccama Server components.

Server Component

The NME engine is exposed as an Ataccama Server component with the following definition.

<component class="com.ataccama.nme.engine.NmeServerComponent">
    <configFile>nme-config.xml</configFile>
</component>

Required:
- HTTP Dispatcher
- Web Console Component
Recommended/Useful:
Integrates with:
- Workflow Server Component
- Scheduler Server Component
- High Availability Component
- Service Mapper / PME
Parameters: <configFile> - path (relative to the default mdm.serverConfig) to nme-config.xml defined below.

When the MDM server starts, additional items are shown in the Admin Center (see MDM Admin Center Extras).

Configuration files naming convention

Mentioned names of configuration files are generally used as outlined above and also on related pages. See the typical names used in this description and their hierarchy.

application.properties (see MDM Server Application Properties)
- nme-config.xml (MDM Engine Configuration File)
  - nme-model.gen.xml (see Model)
  - nme-datasets.gen.xml
  - nme-event_handler.gen.xml(see Event Handler)
  - nme-consolidation-plan.xml
  - nme-services.gen.xml (see Native Services)
  - nme-batch.gen.xml (see Batch Interface)
  - nme-executor.xml (see Executor)
  - nme-stream.gen.xml (see Streaming Interface)
  - nme-security.xml (see Security and Audit)
  - nme-history.gen.xml (see History Plugin)
mdm.serverConfig
- mdm.runtimeConfig

Was this page useful?