Lead your team forward
OCT 24 / 9AM ET Register nowData Sources Connection
MDM database connections can be defined in one of the following ways:
-
All data sources are defined in MDM Server Application Properties.
-
Infrastractural data sources are defined in MDM Web App Application Properties and project-specific data sources are defined in
mdmRuntime.config
.This is the recommended setup for deployments where the project team does not have access to
application.properties
. Note that when using both configuration files, each connection must be defined only once. -
All data sources are defined in
mdmRuntime.config
. This option is not recommended and is provided for backward compatibility only.
All options support password encryption (see Encrypt Passwords).
If you are upgrading to version 14, an upgrade template is provided. See MDM 14.1.0 Upgrade Notes. |
Data sources in application properties
Defining the data sources in MDM Server Application Properties has the following advantages and drawbacks:
-
Reconnection timeout and interval can be configured.
-
This solution is using Hikari database pool, which means additional Spring configuration parameters are supported.
-
The legacy Admin Center SQL monitoring is not available (for more information about the legacy Admin Center, see MDM Admin Center Extras).
ataccama.one.mdm.datasource.mdc_db.url=jdbc:postgresql://localhost:5432/mdc
ataccama.one.mdm.datasource.mdc_db.waiting.timeout=5m
ataccama.one.mdm.datasource.mdc_db.waiting.interval=5s
ataccama.one.mdm.datasource.mdc_db.username=mdc
ataccama.one.mdm.datasource.mdc_db.password=mdc
log_db.url=jdbc:postgresql://localhost:5432
log_db.waiting.timeout=5m
log_db.waiting.interval=5s
log_db.username=log_db
log_db.password=log_db
eh_db.url=jdbc:postgresql://localhost:5432/eh
eh_db.waiting.timeout=5m
eh_db.waiting.interval=5s
eh_db.username=eh
eh_db.password=eh
Was this page useful?