ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (15.4.0) 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

MDM 15.1.0 Upgrade Notes

Due to backward compatibility issues in this version, we recommend upgrading to version 15.3 or higher instead.

Database hints changes for PostgreSQL

Applies only to PostgreSQL database users. If you use database hints (see Database Hints), you need to make the following changes to the configuration file (for example, vldb-commands.xml):

  • Remove the inlistBeforeCommand element.

  • Remove l.id_list = ? from the template element.

These elements are no longer supported.

Authoring behavior issue fixed

Applies only to Migration Authored Master Records plan. After upgrading, make sure that all entities in the plan have authoring enabled.

contributedConfig.xml file

Applies to cloud deployments.

Make sure that you have the contributedConfig.xml file in the runtime folder.

Data Sources configuration

The MDM data sources are now defined in different files depending on whether they are infrastructural or project-specific. See Data Sources Connection for details.

We recommend defining your data sources in the following way:

  • Define the following infrastructural data sources in MDM Server application.properties (for more information, see MDM Server Application Properties, section Data source configuration):

    • mdc_db

    • eh_db

    • log_db

    • it_db

    • mda_cache

    • esb_db

    • external

  • Define project-specific data sources depending on your deployment model:

    • For self-managed deployments, use mdm.runtimeConfig.

    • For cloud deployments, use runtime/datasources.xml.

Runtime properties changes

Applies to self-managed deployments.

New MDM Server application properties were added.

After the upgrade:

  1. Configure the ataccama.one.mdm.config.config-folder property. See MDM Server Application Properties, section MDM solution configuration.

  2. Make sure the default ataccama.one.mdm.config.runtime-folder value corresponds to the actual runtime folder location. For more information, see MDM Server Application Properties, section MDM solution configuration.

  3. Make sure the runtime.properties file is located in one of these folders:

    • etc folder in the ataccama.one.mdm.config.config-folder (recommended)

    • ataccama.one.mdm.config.runtime-folder

The Java option -Druntime.properties=…​ previously used to specify the location of the runtime.properties file is no longer supported.

Health check changes

After the upgrade, make sure that the ataccama.authentication.keycloak.admin.enable MDM Web App application property is set to 'true' or not defined. Otherwise, the MDM Web App will fail to start.

History plugin refactoring issue

The history plugin (see History Plugin) has been refactored, and all settings are now managed in the MDM Server application.properties file. Due to the broken compatibility (see Ataccama 15.2.0 Release Notes, section Known Issues), the history plugin configuration defined in the nme-config.xml file is ignored in the current version. The issue will be resolved in 15.3.0.

To ensure the plugin is enabled, make sure the following properties are defined with the specified values in the application.properties file:

ataccama.one.mdm.config.historyConfigFile=nme-history.gen.xml
ataccama.one.mdm.nme.history.persistence.class=com.ataccama.nme.persistence.vldb.VldbPersistenceFactory
ataccama.one.mdm.nme.history.storage-directory=../storage/history
ataccama.one.mdm.nme.history.persistence.dataSource=mdc_db
ataccama.one.mdm.nme.history.persistence.prefix=H_
If you skip this step, no new historical data will be saved until the properties are defined in the application.properties file.

To change the default configuration, add the relevant properties to the application.properties file and specify the values. To know more, see MDM Server Application Properties, section History plugin configuration.

To disable the history plugin, add the property ataccama.one.mdm.config.historyConfigFile with an empty value:

ataccama.one.mdm.config.historyConfigFile=
It is not possible to disable the history plugin using the checkbox in ONE. The MDM Server fails to start with the empty nme-history.gen.xml file.

Configuration changelog

This section provides the information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.

The following table lists the configuration files that were added, changed, or removed.

Added files Changed files Removed files

contributedConfig.xml - applies to cloud deployments

  • MDM Server application.properties

  • MDM Web App application.properties

  • runtime.properties - location change, see Runtime properties changes

  • mdm.runtimeConfig

  • nme-config.xml

/

The following table lists the changes in the files: added, changed, and removed properties.

Configuration file Added properties Changed properties Removed properties

MDM Server application.properties

  • Git operations (to learn more, see MDM Server Application Properties, section Git operations):

    • ataccama.one.mdm.server.git.enabled

    • ataccama.one.mdm.server.git.repository

    • ataccama.one.mdm.server.git.protocol

    • ataccama.one.mdm.server.git.branch

    • ataccama.one.mdm.server.git.tag

    • ataccama.one.mdm.server.git.destination

    • ataccama.one.mdm.server.git.timeout

    • ataccama.one.mdm.server.git.sshKey

    • ataccama.one.mdm.performance.datasource

    • ataccama.one.mdm.server.git.username

    • ataccama.one.mdm.server.git.password

  • Runtime properties changes - applies to self-managed deployment

    • ataccama.one.mdm.config.config-folder - the default value is ., needs to be adjusted, see MDM Server Application Properties, section MDM solution configuration.

    • ataccama.one.mdm.config.runtime-folder - the default value is ${ataccama.one.mdm.config.config-folder}/../runtime, see MDM Server Application Properties, section MDM solution configuration.

  • History plugin configuration (see History plugin refactoring issue)

ataccama.one.mdm.config.historyConfigFile=nme-history.gen.xml ataccama.one.mdm.nme.history.persistence.class=com.ataccama.nme.persistence.vldb.VldbPersistenceFactory ataccama.one.mdm.nme.history.storage-directory=../storage/history ataccama.one.mdm.nme.history.persistence.dataSource=mdc_db ataccama.one.mdm.nme.history.persistence.prefix=H_

These data sources should be defined here:

  • mdc_db

  • eh_db

  • log_db

  • it_db

  • mda_cache

  • esb_db

  • external

For more information, see MDM Server Application Properties, section Data source configuration.

  • ataccama.one.mdm.db.logging.enabled

MDM Web App application.properties

/

mdm.runtimeConfig

/

Applies to self-managed deployments: project-specific data sources should be defined here. For more information, see MDM Server Application Properties, section Data source configuration.

/

nme-config.xml

/

/

The following properties in the history plugin configuration will be ignored in the current version.

<persistenceLayer class="com.ataccama.nme.persistence.vldb.VldbPersistenceFactory"> </persistenceLayer> <dataSource>mdc_db</dataSource> <prefix>H_</prefix> <configFile>nme-history.gen.xml</configFile> <storageDirectory>../storage/history</storageDirectory>

Was this page useful?