IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Agent configuration and environment variables > Persistent configuration changes > Linux or UNIX persistent configuration changes
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Making persistent configuration changes
To make persistent configuration changes, create the file xx.environment in the config directory. In this file define variables in the key=value format.
Variables defined in the xx.environment file have override variables from the .config file during agent startup.
- If you add a variable to the xx.environment file and during a later configuration, change a parameter that is also in the xx.environment file, the xx.environment file will override your configuration changes. If you use the more robust way of overriding existing variables as described in Example 2, those configuration changes will be included.
- Future IBM Tivoli Monitoring release levels might change the meaning and defaults of configuration variables. You must be aware of changes made to configuration variables and make appropriate alterations to achieve your intended result.
- In the worst case scenario, an override might prevent the agent from starting or running successfully. This scenario requires a manual login and correction. Therefore you must always thoroughly test the setup.
- Some agents use other installation configuration files. The method outlined in this section works only on Linux or UNIX .ini file configuration.
- You can find values passed to the component process in the itm_home/logs/xx.env file.
- Example 1: Overriding the CTIRA_HOSTNAME to change the host name section of the Managed System Name
- Example 2: Altering an existing variable KDC_FAMILIES
The KDC_FAMILIES environment variable is particularly challenging because much of the data is created from the .ConfigData/kxxenv dialog file.
Parent topic:
Linux or UNIX persistent configuration changes