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

MDM Engine Configuration File

A typical nme-config.xml file looks as follows:

nme-config.xml

<config>
	<persistenceLayers>
		<persistenceLayer class="com.ataccama.nme.persistence.database.DbPersistenceFactory">
			<dataSource>mdc_db</dataSource>
			<prefix>I_</prefix>
		</persistenceLayer>
	</persistenceLayers>

	<model>
		<models>
			<consolidation>
				<persistenceLayer class="com.ataccama.nme.persistence.vldb.VldbPersistenceFactory">
					<dataSource>mdc_db</dataSource>
					<prefix>C_</prefix>
				</persistenceLayer>
				<configFile>nme-model.gen.xml</configFile>
				<datasets>nme-datasets.gen.xml</datasets>
				<customActions>nme-custom-actions.gen.xml</customActions>
				<eventHandlersConfigFile>nme-event_handler.gen.xml</eventHandlersConfigFile>
				<executionPlanConfigFile>nme-consolidation-plan.xml</executionPlanConfigFile>
    			<enrichmentConfigFile>nme-enrichments.gen.xml</enrichmentConfigFile>
			</consolidation>
		</models>
	</model>

</config>

The paths are relative to the nme-config.xml file.

The main components are:

History plugin configuration

The history plugin is now defined in the application.properties file, see MDM Server Application Properties, section History plugin configuration. Previously available history plugin definition in the nme-config.xml file (see a typical nme-config.xml file configuration in earlier versions) is deprecated but still supported for a transitional period to maintain backward compatibility.

Was this page useful?