IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Agent configuration and environment variables > Configuration files preserved during an upgrade
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Preserving user custom settings
This section explains how user custom settings are preserved.
During an upgrade many product files are replaced with newer versions. Other files are merged with existing files to produce the updated version. Still other files are generated by the installation process using values you provide. For more information see, Product behavior with custom configuration settings.
The following general rules apply to how user custom settings are preserved:
- User-defined constructs are kept. For example, situations, policies, queries, and workspaces are always preserved automatically on upgrade.
- Values you can change through a supported product interface are preserved.
- Values that you changed manually (for example, because of a technote or as directed by IBM software support) are probably preserved. Any value that you changed manually that was restored to a default value during an upgrade is recoverable from the backups made during the upgrade process.
The configuration process works with two basic types of files:
- K??CMA.ini, k*env (initialization) files are used to collect the inputs from the installation process. This input information is the set of responses to installation questions that are captured as keyword-value pairs. This information is laid down with default values and basic information about the installed components.
- K??ENV, *.config (configuration) files are generated from the values in the initialization files and the values entered during configuration.
The initialization files are source files and the configuration files are output files. Although the source files are modified by the configuration tools and sometimes by hand, the configuration output files are rarely modified. Configuration files are generated files, therefore anything changed manually in configuration files is lost during the reconfiguration of that component.
To recover a manual customization after upgrading, perform the following steps:
- Compare the new version of the K??CMA.ini or K??ENV file with the version saved in the itm_home\backup\backups\date_and_time_of_upgrade directory.
- Compare the new version of the *.ini file with the version saved in the same directory as *.ini.bak.
- Change the installer-supplied defaults to the hand-edited values found in the backup file. Make any changes required to carry your hand-edited custom settings forward, and save the new file.
Parent topic:
Configuration files preserved during an upgrade