IBM InfoSphere Master Data Management, Version 11.3

Using the Configuration and Management components

The Configuration and Management components support the operational configuration and management of applications. They enable administrative users to deploy, fine-tune, and manage applications within their runtime environment.

The Configuration and Management components allow you to configure and manage both standalone and enterprise applications. Currently, these components are only available for InfoSphere® MDM and InfoSphere MDM Event Manager enterprise applications, not for the InfoSphere MDM Batch Controller application.

Understanding configuration
To recognize the different sets of requirements that apply to application configuration before and after the application has been deployed in the operational environment, configuration is divided up into two categories: static and dynamic.
Learning the Configuration and Management architectural overview
The focal point of the Configuration and Management components is the Configuration and Management database that stores the application configuration. Applications read their configuration from the Configuration and Management database through the application configuration client. Administrators use the Management Console to view and change the configuration stored in the Configuration and Management database through the Management Agent.
Understanding the stand-alone enterprise application
In this topology, the Management Agent communicates with the management EJB (MEJB) running on the same application server on which the application runs.
Understanding Java EE clustered enterprise application
In this topology, the application is clustered using the clustering capabilities of the Java EE application server. The Management Agent communicates with the management EJB on the managing node of the application server; that is, the deployment manager for WebSphere® Application Server Network Deployment Edition.
Understanding custom clustered enterprise application
In this topology, the application is clustered in custom ways. The enterprise application is deployed multiple times and it does not appear as a clustered application to the Java™ EE application server.
Understanding configuration definitions and schemas
Configuration definitions are XML documents that contain all the configuration items and their values, as defined during the development process.
Understanding Configuration and Management database structure
The application configuration is represented in two ways: as an XML hierarchical structure; and as a flat map structure.
Using the Application Configuration Client
Applications can use the Application Configuration Client to access the configuration at runtime. This client provides read-only access to the Configuration and Management database using a configuration repository adapter. The adapter itself is pluggable and can be replaced to access different types of configuration repositories. InfoSphere MDM provides a database-based Configuration and Management database and its corresponding repository adapter.
Understanding the Configuration class
The Configuration class provides applications with read-only access to the Configuration and Management database. The Configuration class is a singleton whose sole instance can be obtained through the getConfiguration() method.
Understanding configuration methods
The Configuration and Management components support several configuration methods.
Understanding the ConfigContext class and public Node getConfigItemsMap() method
Be familiar with the class and method for the Configuration and Management components. The method retrieves information from the context.
Adding configuration nodes and items to the Configuration and Management component
If your deployment of InfoSphere MDM requires custom configuration nodes and items, you can add them to the Configuration and Management component to help you to manage them.
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.
Importing and exporting custom configuration elements
You can use the Export Configuration and Import Configuration options to export and import custom configuration elements.
Removing custom configuration elements that were added through the configelement table
Custom configuration parameters that are directly inserted to the configelement table of the Configuration and Management database cannot be removed using the Partially remove the application configuration option of the Management Console.
Broadcasting configuration changes
The JMX notification model is used to broadcast configuration data changes when there is a refresh change to a dynamic configuration item. If the broadcast change occurs before a refresh, put the change in preRefresh; if the broadcast change occurs after the refresh, put the change in postRefresh.
Elements in the Configuration and Management component
The Configuration and Management component manages several configuration elements. This topic provides details of those configuration elements.

Parent topic: Platform and core feature overview

Related concepts:

Configuration and Management components

Last updated: 27 June 2014