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
- During the initial IBM® Installation Manager session, the MDM Database and MDM Application features were installed and configured.
- 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
- Run IBM Installation Manager in Modify mode and complete the panels to add the Business Administration and Data Stewardship features.
- Run the
Configure_MasterDataManagementmadconfig 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
- 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.
- To configure the components, the
Configure_MasterDataManagementmadconfig script was run. - 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
- 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.
- To configure the components, the
Configure_MasterDataManagementmadconfig script was run. - 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.