RTView Enterprise 5.2

1. Download the new deliverable and extract it in a new directory on the same system as your old deliverable.
2. In the new deliverable, make a backup copy of the projects directory.
3. In the new deliverable, make a backup copy of the bin directory.
4. If you have a permanent license, copy the following file from the old installation to the new installation:
– rtvapm/rtview/lib/KEYS
5. If you modified the scripts under RTViewCentral\bin in the old installation, copy RTViewCentral\bin from the old installation to the new installation.
6. If you modified any files under projects/custom in the old installation:
• The following files under projects\custom were changed between 5.1 and 5.2. If you modified them in your old installation, reapply the changes to the new versions of the files:
– projects/custom/src/make_classes.bat
– projects/custom/src/make_classes.sh
• Copy any other java files you modified from projects/custom/src/com/sl/rtvapm/custom in the old installation to the new.
• Execute make_classes.bat or make_classes.sh in an initialized command prompt to rebuild your custom classes against the new release.
7. The following files under projects/rtview-server were changed between 5.1 and 5.2. If you modified them in your old installation, reapply the changes to the new versions of these files. Note that the custom_setup scripts now point to the central.properties under RTVAPM_HOME/appmon/conf instead of the local directory. Do not change this path and do not modify RTVAPM_HOME/appmon/conf/central.properties. If you made changes to the local central.properties file in your previous installation, they will be addressed in a later step.
– custom_setup.bat
– custom_setup.sh
– update_wars.bat
– update_wars.sh
– central.properties (this file has been removed)
8. Copy all files not mentioned in the previous step under projects/rtview-server from old to new.
9. If you enabled authentication of the rtvquery servlet in your previous installation (for LDAP or HTTP authentication), modify the update_wars script to set SECURE to -secure so that the script will generate a secure rtvquery war file.
10. Execute projects/rtview-server/update_wars in an initialized command prompt and copy the generated jars to RTViewCentral/apache-tomcat-*-sl/webapps or your application server.
11. The following files under projects/rtview-manager were changed between 5.1 and 5.2. If you modified them in your old installation, reapply the changes to the new versions of these files:
– custom_setup.bat (new)
– custom_setup.sh (new)
– rtvservers.dat
– update_wars.bat
– update_wars.sh
12. The following files under projects/rtview-manager were changed between 5.1 and 5.2. These are modified via the configuration application. Any changes you made to the rtview-manager via the configuration application in the previous release will be addressed in a later step.
– project.properties
– project.properties.json
13. Copy all files not mentioned in the previous 2 steps under projects/rtview-manager from old to new.
14. If you enabled authentication of the rtvquery servlet in your previous installation (for LDAP or HTTP authentication), modify the update_wars script to set SECURE to -secure so that the script will generate a secure rtvquery war file.
15. Execute projects/rtview-manager/update_wars in an initialized command prompt and copy the generated jars to RTViewCentral/apache-tomcat-*-sl/webapps or your application server.
16. If using HSQLDB, copy projects/DATA and projects/rtview-manager/DATA from the old installation to the new installation.
17. Add new CacheMetric column to your alert database as described in the release note for TN24246.
18. If your previous installation included LDAP integration
• Copy RTViewCentral/apache-tomcat-*-sl/lib/ldapUser.jar from the old installation to the new installation
• Copy RTViewCentral/apache-tomcat-*-sl/conf/server.xml from the old installation to the new installation
• Copy RTViewCentral/apache-tomcat-*-sl/conf/Catalina.properties from the old installation to the new installation
19. If you modified rtvapm/common/conf/sl.log4j.properties in your old installation, copy the sl.log4j.properties file from your old installation to projects/sl.log4j.properties. All future changes to the logging configuration should be made in projects/sl.log4j.properties.
20. Start up the new installation using the start_servers script under bin.
21. If you made changes to central.properties file in your previous installation:
• Open the configuration application at http://localhost:10070/rtvadmin.
• Use rtvadmin/rtvadmin for the login.
• Click on the Central Server, then click on the CUSTOM PROPERTIES tab.
• Add all properties that you changed in the central.properties in the previous version.
• Click SAVE at the top, then click Restart Servers to save and apply your changes.
22. If you made changes to the rtview-manager using the configuration application in your previous installation:
• Open the configuration application at http://localhost:3070/rtvadmin.
• Use rtvadmin/rtvadmin for the login.
• Click SAVE at the top, the Restart Servers to save and apply your changes.
• Click on the RTView Manager server and reapply all changes you made in the previous version.
23. In the previous release, the RTView Manager was accessible at http://localhost:3070/rtview-manager-classic or http://localhost:8068/rtview-manager-classic. This has been replaced by the new HTML user interface which is available at http://localhost:3070/rtview-manager or http://localhost:8068/rtview-manager.

Return to Download, Install, Register and Upgrade RTViewCentral.