Users upgrading from previous versions who have modified the RTViewCentral/projects/rtview-server/central.properties file should not modify the central.properties file under rtvapm/appmon/conf. Instead, add those properties in the Configuration Application CUSTOM PROPERTIES tab.
If you are collecting Syslog events with Solace Event Module, copy RTViewDataServerSolace/rtvapm/solmon/soleventmodule/config/soleventmodule.properties to your new installation. Additionally, if you made changes in logging, copy RTViewDataServerSolace/rtvapm/solmon/soleventmodule/config/log4j2.properties to your new installation.
The rtview-manager directory is not typically customized in RTViewCentral. However, in the case where this directory was customized, upgrading users should re-apply their changes to the new rtview-manager project and not just override the directory with the old version of the rtview-manager directory.
Users upgrading from previous version who enabled EM Integration, but left Announce this RTView Data Server to the Central Server as false will need to go into the RTView Configuration Application and set it to false again as the default has changed from false to true.
For upward compatibility, if the projects\sl.log4j.properties file is not found, the rtvapm\common\conf\sl.log4j.properties file will be used instead. However, users upgrading from previous versions who have modified the logging settings should apply their logging changes to the sl.log4j.properties file in projects instead of the copy under rtvapm\common\conf in order to make it easier to upgrade to future releases.