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
Files that are not preserved on upgrade
This section contains the files that are not preserved when you upgrade the IBM Tivoli Monitoring environment.
If you modified these files or settings, you must make a backup before performing the upgrade. After the upgrade, you must reconstitute your modifications from your backups.
- For the Manage Scripts feature in Tivoli Enterprise Portal
- The Manage Scripts feature in the Tivoli Enterprise Portal has a set of built-in scripts that manage 3270 terminal session navigation. These built-in functions persist after you install IBM Tivoli Monitoring. However, save the custom scripts that you define for the navigation of 3270 terminal sessions. See the IBM Tivoli Monitoring Tivoli Enterprise Portal User's Guide.
- For components running on Windows systems OR Linux or UNIX systems
- The following IBM Tivoli Enterprise Console event synchronization files are not preserved on upgrade:
- In the TEC_CLASSES directory of the rulebase created during IBM Tivoli Enterprise Console event synchronization installation: omegamon.baroc, Sentry.baroc.
- In the TEC_RULES directory of the rulebase created during IBM Tivoli Enterprise Console event synchronization installation: omegamon.rls.
Before these files are replaced, backup copies are made automatically and placed in the same directories as the original files and have the .bac suffix added to their names. You can open these backup files and manually migrate modifications.
The .baroc and .rls files are backed up only if you choose to automatically upgrade the specified rulebase.
- For components running on Windows systems
- The following files are not preserved on upgrade:
- On the Tivoli Enterprise Portal Server, the CNP.bat and applet.html files are built based on the content of the CNPS, CNP, and CNB directories. Except for the -D flags, everything in these files is regenerated.
- The buildpresentation.bat file is generated during installation. Any updates to this file are lost.
- For components running on Linux or UNIX systems
- The following files are not preserved on upgrade:
- ARCH/cq|cj|cw/*, where ARCH is a specific architecture, such as li6263 and one of the following two-letter codes: cq, cj, or cw. These files are overwritten during upgrade. One exception to this rule is the ARCH/cw/jrelevel.js file, the content of which is preserved.
- The autostart scripts. These files are regenerated during the installation and configuration and have different names based on the platform:
- Linux, Solaris: /etc/init.d/ITMAgents*
- HP-UX: /sbin/init.d/ITMAgents*
- AIX: /etc/rc.itm*
- Special exceptions
- On Linux or UNIX systems, several IBM Tivoli Monitoring configuration files exist with values that do not typically persist during an upgrade. However, the values in the following files do persist:
- itm_home/tables/temsname/*.txt, where *.txt refers to all file names that have the text (*.txt) tag, including partition.txt (previously including glb_site.txt).
The glb_site.txt file is not supposed to be preserved. It is a configuration output file and its values are gathered and stored during normal configuration.
- The following files are generated from kbbenv.ini and ms.ini:
- itm_home/tables/temsname/KBBENV
- itm_home/config/hostname_ms_temsname.config
Changes made to these files are saved in the same way that changes made to the source .ini files are saved.
Parent topic:
Configuration files preserved during an upgrade