Preservation of custom configurations during an upgrade

Custom configurations that are overwritten

Upgrades overwrite custom configurations to several files in the data grid and the Liberty server, which are essential to the functioning of the system. When a custom configuration is overwritten, the custom configuration is saved with a file name that indicates that it was overwritten when the fix pack or interim fix was applied.

If you feel that a custom configuration is justified, you must manually reapply that configuration.

Custom configurations to the data grid and the Liberty server in the following files are overwritten by upgrades:

• install_dir\Members\resources\SystemConfigurationDSLoader.properties
• install_dir\Members\resources\SystemConfigurationMFLoader.properties
• install_dir\Members\resources\SystemConfigurationXSLoader.properties
• install_dir\Members\member_type\usr\servers\jvm.options
• install_dir\Members\member_type\usr\servers\bootstrap.properties
• install_dir\*\server.xml

Custom configurations that are not overwritten

Custom configurations to the data grid in the following files are not overwritten by upgrades. You must decide whether to overwrite the custom configurations with the upgrade. See Manual properties file changes after an upgrade.

• install_dir\Members\resources\SystemConfigurationMFEndPointLoader.properties
• install_dir\Members\resources\SystemConfigurationSYSLoader.properties

The upgrade versions of these files are saved with a file name that includes an extension of the interim fix or fix pack identifier. The property values for the existing versions of the files remain in the data grid until you decide whether to change any of those values with the upgrade versions of the files.

A message about these files is displayed after the upgrade.