Skip to main content

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.

The password is encrypted upon the startup of the MDM server. For more information about how to change the default password, see Managing the passwords in configuration files.

system.data.auto.init=true

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

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 UI.

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.
Availability-noteDeprecated

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.
Availability-noteDeprecated

Bonita technical user/password

technical.user=install

technical.password=install

Specifies credentials for Bonita technical users.

The password is encrypted upon the startup of the MDM server. For more information about how to change the default password, see Managing the passwords in configuration files.

Information noteNote: 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 community server manually (deprecated).

IAM settings

tac.domain=@company.com

Defines a domain used to translate usernames to emails for backward compatibility when migrating Jobs and workflows to a 7.0 MDM server.

oidc.url

Defines the URL to your Talend Identity and Access Management, href="http://localhost:9080/oidc" for example.

oidc.userauth.url

Defines the URL to your Talend Identity and Access Management user authentication, href="http://localhost:9080/oidc" for example.

oidc.client.id

Defines the Talend Identity and Access Management OIDC client identifier.

oidc.client.secret

Defines the Talend Identity and Access Management OIDC password.

scim.url

Defines the URL to your Talend Identity and Access Management SCIM,href="http://localhost:9080/scim" for example.
scim.username Defines the username for the user in the SCIM.
scim.password Defines the password for the user in the SCIM.

Mandatory:

security.basic.enabled=false
security.oidc.client.expectedIssuer=${oidc.url}
security.oidc.client.keyUri=${oidc.url}/jwk/keys
security.oidc.client.endSessionEndpoint=${oidc.userauth.url}/idp/logout
security.oauth2.client.clientId=${oidc.client.id}
security.oauth2.client.clientSecret=${oidc.client.secret}
security.oauth2.client.scope=openid refreshToken
security.oauth2.client.access-token-uri=${oidc.url}/oauth2/token
security.oauth2.client.user-authorization-uri=${oidc.userauth.url}/idp/authorize?consent=none
iam.license.keepAliveEndpoint=${oidc.url}/api/v1/licenses/keepAlive

Optional:

security.oidc.client.notBeforeTimeTolerance=60
security.oidc.client.claimIssueAtTolerance=60
security.oidc.client.claimIssueAtExpiration=3600
security.oidc.client.claimExpirationTolerance=60
security.oidc.client.maxAuthenticationTime=7200
security.oidc.client.tokenExpirationLeeway=30
 Defines the Single Sign-On security configuration.
Fuzzy search setting lucene.fuzzy.search=true

Indicates whether Lucene fuzzy search is enabled for searching data records. By default, this parameter is not added in the file and Lucene fuzzy search is enabled. You can add this parameter and set its value to false to disable Lucene fuzzy search.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here