Configuring MDM Server

Talend MDM Platform Installation Guide

EnrichVersion
6.1
EnrichProdName
Talend MDM Platform
task
Installation and Upgrade
EnrichPlatform
Talend Identity Management
Talend Administration Center
Talend Artifact Repository
Talend Activity Monitoring Console
Talend MDM Server
Talend Project Audit
Talend Studio
Talend ESB
Talend SAP RFC Server
Talend DQ Portal
Talend JobServer
Talend CommandLine
Talend Log Server
Talend Installer
Talend Repository Manager
Talend Runtime
Talend MDM Web UI

The mdm.conf file stored in the <$INSTALLDIR>\conf directory contains all the configuration information for MDM Server. You can edit some of the information in this file to change the behavior of MDM Server in certain cases.

Editing the mdm.conf file

You can edit the file mdm.conf to customize the configuration for the MDM server according to your needs.

The parameters and their default values available in the file are listed below:

Settings

Parameters and Default Values

Usage

System settings

admin.user=admin

admin.password=talend

Specifies the credentials for the default administrator users of the MDM server.

system.data.auto.init=true

Indicates whether the MDM server will automatically initialize the system data during startup.

system.data.auto.upgrade=true

Indicates whether the MDM server will automatically upgrade the system data.

system.data.force.upgrade=false

Indicates whether the migration tasks will be executed even when the new system Version Number is equal to or less than the current system Version Number.

system.locale.default=en

Specifies the default system locale.

max.export.browserecord=1000

Indicates the maximum number of records to be exported on the Talend MDM Web User Interface.

max_cache_size=5000

Indicates the maximum size of the cache.

cluster_override=false

Indicates whether to override the existing content in the database for the system container when starting the MDM server.

RDBMS Settings

db.autoPrepare=true

Indicates to the MDM server whether it should try to create a database on its own or not.

db.datasources=${mdm.root}/conf/datasources.xml

Points to a file that provides the database connection information.

db.default.datasource=H2-Default

Indicates to the MDM server which default datasource specified in db.datasources should be used.

Subscription Engine

subscription.engine.autostart=true

Indicates whether JMS (Java Message Service) in the system will be started automatically.

system.cluster.storage.index.replication=true

Indicates whether to apply index replication per storage.

mdm.routing.engine.broker.url = vm://localhost

Specifies the connection URL for the JMS service.

routing.engine.max.execution.time.millis=300000

Indicates the maximum milliseconds a routing order can take to execute. The value of "0" indicates the routing order never expires.

For example, the value of "300000" is equal to 5 minutes.

mdm.routing.engine.consumers=5-10

Indicates the number of simultaneous routing order consumers that can be concurrently processed.

Its value supports a number range. For example, "5-10" means that at least 5 consumers will be present, with a maximum of 10 if all previous consumers are busy.

mdm.routing.engine.broker.sessionCacheSize=1

Indicates the number of cached JMS sessions per session acknowledgement type (auto, client, dups_ok, transacted).

If needed, you can increase this number in a high-concurrency environment.

Bonita user synchronization

scheduler.enabled=true

Indicates whether to enable the periodic batch job for synchronization with the Bonita server.

scheduler.retryCount=10

Specifies the number of retries when the synchronization job fails.

scheduler.retryInterval.seconds=60

Specifies the interval of time in seconds between each retry attempt.

scheduler.period.seconds=3600

Specifies the period of the synchronization job.

scheduler.initialDelay.seconds=10

Specifies the delay time allowed for the initial synchronization job after the system startup.

scheduler.shutdownTimeout.seconds=30

Indicates the time allowed for the system to gracefully shut down the synchronization job when the job is completed.

realtime.synchronize.enabled=true

Indicates whether to enable realtime synchronization.

Bonita technical user/password

technical.user=install

technical.password=install

Specifies credentials for Bonita technical users.

Note

Bonita technical users are used by MDM to connect to the Bonita BPM server and then perform operations such as deploying workflows and synchronizing workflow users. For more information about how to configure the connection between the MDM server and the Bonita BPM server, see Installing the Bonita BPM server manually.

Improving performance when loading data from the Staging Area

The mdm.conf file, which is stored in the <$INSTALLDIR>\conf directory, includes several properties which can be edited to improve performance.

Property

Type

Description

staging.validation.updatereport

boolean

When you run the validation process that loads data from the Staging Area to Talend MDM, by default this process generates update reports that record inserts in the Journal and fire any relevant Triggers.

To instruct MDM Server not to generate update reports when loading data from the Staging Area, set this property to false.

staging.validation.pool

int

By default, MDM Server assigns two threads to the validation process that loads data from the Staging Area to Talend MDM.

If the machine running MDM Server has some spare CPU, edit the value of this property to increase the number of threads that can be used.

staging.validation.commit

int

By default, when loading data from the Staging Area to Talend MDM, Talend MDM commits records to the master database every 1000 validated objects.

To improve performance, increase this value to reduce the number of commits made to the database.

staging.validation.buffer.threshold

int

A buffer is used to transfer records from the Staging Area to the master database. By default, the buffer holds a maximum of 1000 records; once this threshold is reached, the action of reading from the Staging Area will be paused and a check will be made every second to see if the number of records in the buffer has decreased.

Since reading from the Staging Area is always faster than writing to the master database, reduce the value of the buffer size if you encounter memory issues.