IBM InfoSphere Master Data Management, Version 11.3

Working with configuration data

The individual dwl-config.xml files at the module level are combined into a master configuration definition file at deployment time. Similarly, the dwl-config.xsd files are combined into a master configuration definition schema file. Once deployed, use the Configuration and Management Console to change the value of any of the configuration elements.

This is described in the topic on Understanding configuration definitions and schemas.

The following diagram shows the deployment for the base InfoSphere® MDM modules:

InfoSphere MDM module base deployment configuration

If you create your own module to extend InfoSphere MDM, including your own dwl-config.xml and dwl-config.xsd files, deploy them so that they are combined into the master configuration definition file and master configuration definition schema file.

The following diagram shows an example of deployment with extensions:

Illustration of the InfoSphere MDM module deployment configuration with extensions

InfoSphere MDM provides several options to deploy and remove the configuration data. You can use the Management Console to perform any of these options:

Deploying the application configuration – Uses the EAR file as the input and combines the dwl-config.xml and dwl-config.xsd in each of the modules found in the EAR file. This option uses the default value for each of the configuration element. Use this option if you want to load the entire master configuration definition with the default values.
Removing the application configuration – Removes the entire deployed master configuration definition. Use this option if you want to remove the entire deployment.
Note: Any value that you have specified for any configuration elements will be lost.
Partially deploy the application configuration – Uses a JAR file (that is, a module) as the input and adds nodes to the deployed master configuration definition based on the way the context is defined in the dwl-config.xml and dwl-config.xsd in the JAR file. If you have specified any values for configuration elements in any existing nodes, the values will not be affected. Use this option if you want to add to the master configuration definition.
To use this option, you must also ensure that the META-INF/MANIFEST.MF inside the JAR file contains the following entries:
```
Manifest-Version: 1.0
Created-By: MDM (IBM Corporation)
Application-Name: <SameAsDefinedInTableAppSoftware>
Application-Version: <SameAsDefinedInTableAppSoftware>
```
Note: You must restart the server to make this option take effect.
Partially remove the application configuration – Uses the JAR file (that is, a module) as the input and removes the configuration elements under the module from the deployed master configuration definition. If you have specified any values for configuration elements in the remaining nodes, the values will not be affected. Use this option if you want to remove portion of the master configuration definition.
To use this option, you must also ensure that the META-INF/MANIFEST.MF inside the JAR file contains the following entries:
```
Manifest-Version: 1.0
Created-By: MDM (IBM Corporation)
Application-Name: <SameAsDefinedInTableAppSoftware>
Application-Version: <SameAsDefinedInTableAppSoftware>
```

Last updated: 27 June 2014