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

MDM 16.1.0 Upgrade Notes

MDM Admin Center permission changes

To change runtime parameters, access the server dashboard, or edit the logging configuration in MDM Web App Admin Center, you need one of roles defined in the property ataccama.one.mdm.admin-center.manager.required-roles. By default, this role is MDM_server_admin.

The actual role name might differ in your setup.

If you have one of the roles defined in ataccama.one.mdm.admin-center.read-only.required-roles and ataccama.one.mdm.admin-center.full-access.required-roles, you can only view the screens listed but not edit anything.

Changes to runtime parameters configuration

Starting from 16.1.0, MDM-specific runtime parameters (with nme. prefix) are stored in the MDM database and managed through the MDM Web App Admin Center. Previously, these parameters were defined in the runtime.properties file, typically located in <ataccama.one.mdm.config.config-folder>/etc, or provided to the JVM when starting the MDM server.

After you upgrade to 16.1.0, during the first server startup, a migration process collects the runtime parameters from a number of configuration locations and loads them to the MDM database. This covers:

Command line arguments.
Java system properties (defined in the JVM).
OS environment variables.
runtime.properties file, not including Oracle database hint parameters.
Other valid configuration files (those introduced from version 15.1.0 or later).

After the migration, you can modify the values of runtime parameters in the MDM Web App Admin Center, from the Runtime Parameters tab. For details, including the necessary permissions, see Runtime Parameters.

Other runtime properties that you might have configured for your MDM Server are not affected by this change.

How to prepare for migration

Before you start the MDM server for the first time after upgrading to 16.1.0, make sure your runtime.properties configuration file is optimized for the migration.

Open the runtime.properties configuration file. The file is located in <ataccama.one.mdm.config.config-folder>/etc or <ataccama.one.mdm.config.runtime-folder>.

To verify the actual location, check the values of the ataccama.one.mdm.config.config-folder and ataccama.one.mdm.config.runtime-folder application properties.
Check if the following properties are present in the file. If they are, edit them as instructed here:
1. Remove or comment out the following properties:
  - nme.db.smallDataThreshold
  - nme.tasks.migration.apply-automatically
2. Rename the following property to nme.readonly:
  - nme.vldb.readonly
3. Edit the values as needed. The values added or modified are described in Changed properties.
  - nme.parallel.coordinator.key.strategy
  - nme.vldb.alterTableLevel
  - nme.db.alterTableLevel
If you are using an Oracle database and have database hint parameters configured, replace the parameter names as described in How to prepare Oracle database hint parameters for migration. You can also define these parameters later in the MDM Web App Admin Center once the migration procedure is complete.

If you are not using an Oracle database or in case you are but do not have database hint parameters defined, skip this step.
Save your changes. Depending on your setup, proceed with How to prepare Oracle database hint parameters for migration or skip ahead to Automatic migration.

How to prepare Oracle database hint parameters for migration

This section is only relevant if you are using an Oracle database for your MDM solution.

Before migration, Oracle database hint parameters first need to be renamed to follow the new naming pattern.

Otherwise, they are skipped in the automatic migration and the default values are used instead of your custom ones. If needed, you can change these values later through the MDM Web App Admin Center.

In the runtime.properties file, change the names of the parameters you are using according to the following table.

For ease of use, the table provides both the previous and current parameter names. However, only the new parameter names should be specified in the file.

Table 1. Database persistence hint parameters
Previous parameter name	New parameter name
`DbUnorderedInList.match`	`nme.db.unorderedInList.match`
`DbUnorderedInList.unmatch`	`nme.db.unorderedInList.unmatch`
`DbOrderedInList.match`	`nme.db.orderedInList.match`
`DbOrderedInList.unmatch`	`nme.db.orderedInList.unmatch`
`DbInList.main.hint`	`nme.db.inList.main.hint`

Table 2. VLDB persistence hint parameters
Previous parameter name	New parameter name
`VldbUnorderedInList.match.small`	`nme.vldb.unorderedInList.match.small`
`VldbUnorderedInList.match.large`	`nme.vldb.unorderedInList.match.large`
`VldbUnorderedInList.unmatch`	`nme.vldb.unorderedInList.unmatch`
`VldbOrderedInList.match.small`	`nme.vldb.orderedInList.match.small`
`VldbOrderedInList.match.large`	`nme.vldb.orderedInList.match.large`
`VldbTableAccessor.find.small`	`nme.vldb.tableAccessor.find.small`
`VldbTableAccessor.find.large`	`nme.vldb.tableAccessor.find.large`
`VldbTableAccessor.find.main.small`	`nme.vldb.tableAccessor.find.main.small`
`VldbTableAccessor.find.main.large`	`nme.vldb.tableAccessor.find.main.large`
`VldbTableAccessor.count.accuracy.mode`	`nme.vldb.tableAccessor.count.accuracy.mode`

Automatic migration

Once you have checked the contents of the runtime.properties configuration file and updated the properties as needed, you can now start the MDM Server. This starts the automatic migration process as well.

If the migration finished successfully and there were no other issues during the upgrade, the MDM Server starts as expected and you can log in to the MDM Web App Admin Center.

If the server fails to start and the Admin Center is not available, this can indicate that the migration failed. This can happen, for example, due to validation issues or database availability. In that case, contact Ataccama Support.

To learn about how and when to run the migration from the MDM Web App Admin Center, see MDM Web App Admin Center > Server Dashboard.

Configuration changelog

This section provides 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
/	MDM Server application.properties runtime.parameters	/

Added files

Changed files

Removed files

MDM Server application.properties
runtime.parameters

The following sections list the changes in the files: added, changed, and removed properties.

MDM Server application.properties

Changed properties

Following the updates in Spring Boot 3.4, the actuator endpoint properties have been changed accordingly. In addition to new property names, the properties are now of string data types and can be set to one of the following values:

none - Disables an endpoint.
read-only - Read-only access to endpoint operations.
unrestricted - Full access to endpoint operations.

Rename and configure the properties listed. For details, see Endpoints for monitoring.

If obsolete values are still present in the configuration after the upgrade, the server fails to start.

Obsolete property New property New default value

Obsolete property	New property	New default value
`management.endpoints.enabled-by-default`	`management.endpoints.access.default`	none
`management.endpoint.info.enabled`	`management.endpoint.info.access`	unrestricted
`management.endpoint.health.enabled`	`management.endpoint.health.access`	unrestricted
`management.endpoint.prometheus.enabled`	`management.endpoint.prometheus.access`	unrestricted

management.endpoints.enabled-by-default

management.endpoints.access.default

none

management.endpoint.info.enabled

management.endpoint.info.access

unrestricted

management.endpoint.health.enabled

management.endpoint.health.access

unrestricted

management.endpoint.prometheus.enabled

management.endpoint.prometheus.access

unrestricted

runtime.parameters

After upgrading to 16.1.0, we recommend no longer using this file to store and manage MDM-specific runtime parameters (those starting with an nme. prefix).

Once you successfully complete the initial migration, edit runtime parameters only in the MDM Web App Admin Center.

Changed properties

nme.parallel.coordinator.key.strategy - Renamed allowed values to PLAIN, COMPRESS, SHA256. Previously, the values used to be called none, compress, hash, respectively.
nme.vldb.readonly - Renamed to nme.readonly, the default value is false, see VLDB persistence hint parameters.
nme.vldb.alterTableLevel, nme.db.alterTableLevel - Added a new allowed value addIndexes, which creates missing indexes if a table in the database does not match the model. The default value for both parameters is now addColumns,addIndexes,alterColumnsAlter (see VLDB persistence parameters and Database persistence parameters respectively).
Hint parameters - The names of these properties now follow the same pattern and case as other runtime parameters.

Instead of {PersistenceType}{HintType}.{parameter}, new property names now use the format nme.{persistenceType}.{hintType}.{parameter}. For example, `DbInList.main.hint is now nme.db.inList.main.hint. For a full comparison of property names, see How to prepare Oracle database hint parameters for migration.

See a detailed description of the properties and their default values, see VLDB persistence hint parameters and Database persistence hint parameters.

Removed properties

nme.vldb.readonly - Use nme.readonly instead, the default value is false, see VLDB persistence hint parameters.
nme.db.smallDataThreshold - No longer used.

Was this page useful?