The InfoSphere MDM installation application enables you to install or modify the product while generating configuration properties files that you can use to configure the product at a later point in time.
About this task
The standard InfoSphere MDM installation process involves configuring key properties of the deployment at the same time as the installation occurs. However, with the separation feature, you can separate the installation from the
configuration of application properties, the database, user interfaces, and other key properties and variables.
Restriction: The configuration separation capability is only available if you are using the custom installation type. Stand-alone installations with DB2 do not support separating configuration from installation.
When you select the option to separate the configuration from installation, the installation application will generate a number of properties files that track the selections you have made in the IBM Installation Manager session. These
properties files are stored in MDM_INSTALL_HOME/properties. You can manually edit these generated properties files to change the product configuration, and then use scripts to apply the new configuration to an existing instance without having to complete a full reinstallation.
The configuration separation capability can also be used when you modify an installed product to include new components. Once the separation option is selected, you must always follow an IBM Installation Manager Modify session by running the madconfig script to complete the modification.
Procedure
1. Start the Launchpad or IBM Installation Manager to start the custom
installation. Complete the installation application panels to provide the details of your deployment as normal.
2. On the Install Configuration Review panel, under Install Type, select the option to Manually run the scripts to configure InfoSphere MDM components after installation.
3. Click Verify Installation Requirements to run the installation verification checks.
4. Correct any verification check errors, and then click Install to run the
installation. When the installation completes, InfoSphere MDM will be installed and the installation application will have generated some or all of the following properties files, depending on the features that you selected to install, in
MDM_INSTALL_HOME/properties:
db.properties
When the MDM Database feature is installed through IBM Installation Manager, this properties file is created. It contains the configuration details of your database instance.
app.properties
When the MDM Application feature is installed through IBM Installation Manager, this properties file is created. It contains the configuration details of your InfoSphere MDM operational server instance.
<user interface>.properties
Depending on the user interface application components that you selected in IBM Installation Manager, a number of properties files are created. These files contain the configuration details of your InfoSphere MDM user interface application components.
MDM_isInstalled.properties
This property file stores configuration information about what InfoSphere MDM components are installed. This file has a key/value pair for each component that tracks whether each feature is installed (YES) or not (NO).
MDM_Rollback.properties
This property file is used in case of serious errors that cause the installation to be rolled back. It stores details about each InfoSphere MDM component and the state of that feature. This file has a
key/value pair for each component that tracks whether each feature is successfully installed (YES), partially installed (PARTIAL), or not installed (NO).
If the status of any component is PARTIAL due to an error that the installation application encountered, then after the error has been corrected and the installation is rerun, the installation application will roll back only the partially installed component and rerun the
installation for that and any other failed components.
This file also maintains the set of targets that are run while installing each component. These targets help to manage the rollback process.
MDM_Variables.properties
This property file is the default property file created during any InfoSphere MDM installation. The value of the property
user.L2.mdm.feature.listcontains a list of features that were selected in IBM Installation Manager.
5. If a configuration change is required, edit one or more of the properties files in MDM_INSTALL_HOME/propertiesto reflect the needed change.
6. Run the following madconfig script to apply the new configuration defined in the properties files:
v On Microsoft Windows systems, run madconfig.bat Configure_MasterDataManagement v On Linux or UNIX systems, run
madconfig.sh Configure_MasterDataManagement
Tip: If you encounter any issues while running the configuration script, review the log files and take steps to correct the problem, then rerun the script.
The InfoSphere MDM product is reconfigured by the madconfig script based on the values in the properties files.
7. Optional: To remove an entire product configuration that was applied using the Configure_MasterDataManagementmadconfig script, run the following
madconfig script to remove all configuration files.
v On Microsoft Windows systems, run madconfig.bat Uninstall_MDM
v On Linux or UNIX systems, run madconfig.sh Uninstall_MDM
Important: Be careful about running the Uninstall_MDM madconfig script.
Running Uninstall_MDM removes the configuration of all features, and not just the configuration of a particular component.
8. Optional: To remove an individual feature configuration that was applied using the Configure_MasterDataManagement madconfig script:
a. Open IBM Installation Manager and select Modify.
b. Remove the feature on the feature selection panel.
c. Run the madconfig script to configure the new product configuration:
v On Microsoft Windows systems, run madconfig.bat Configure_MasterDataManagement v On Linux or UNIX systems, run
madconfig.sh Configure_MasterDataManagement Related concepts:
“Installing client applications and individual components” on page 149 Related tasks:
“Modifying your installation” on page 163 Configuration separation scenarios:
The scenarios in this topic are a few examples of instances when the configuration separation scripts are useful.
Modifying the installation to add components Scenario
v During the initial IBM Installation Manager session, the MDM Database and MDM Application features were installed and configured.
v At a later time, the installer decides that this InfoSphere MDM instance additionally requires the Business Administration UI application and the Data Stewardship UI application.
Remedy
v Run IBM Installation Manager in Modify mode and complete the panels to add the Business Administration and Data Stewardship features.
v Run the Configure_MasterDataManagement madconfig script.
Result The InfoSphere MDM instance is configured by the script to use the additional user interface applications.
Fixing an installation after a failure leaves a partially installed component Scenario
v During the initial IBM Installation Manager session, the MDM Database and MDM Application features were installed and the Manually run the scripts to configure InfoSphere MDM components after installation option was selected.
v To configure the components, the Configure_MasterDataManagement madconfig script was run.
v While configuring the MDM database, an error occurred and the installation stopped, leaving the MDM Database partially installed.
Remedy
Review the logs and fix the issue, then rerun the Configure_MasterDataManagementmadconfig script.
Result When the script is rerun, the partially installed MDM Database component is uninstalled and then reinstalled with the fresh configuration. The MDM Application is also configured.
Rolling back a failed component installation and reconfiguring the component Scenario
v During the initial IBM Installation Manager session, the MDM Database and MDM Application features were installed and the Manually run the scripts to configure InfoSphere MDM components after installation option was selected.
v To configure the components, the Configure_MasterDataManagement madconfig script was run.
v The MDM Database installed successfully, but an error occurred while installing the MDM Application component and the installation stopped, leaving the MDM Application partially installed.
Remedy
Review the logs and fix the issue, then rerun the Configure_MasterDataManagementmadconfig script.
Result When the script is rerun, the partially installed MDM Application
component is rolled back and then reinstalled with the fresh configuration.
The MDM Database component is left untouched, since it was correctly configured during the first attempt.