Solution Package for Solace v5.1.x

The Solution Package for Solace file structure has been refactored. Review the release note for TN23877 for a list of all changes.

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 RTViewSolaceMonitor\bin in the old installation, reapply those changes to the scripts under SolacePubSubMonitor. Do not copy the scripts from the old installation to the new installation as they have all changed to work with the new directory structure.

6. If you modified any files under projects\custom in your 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 following 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.

• update_wars.bat

• update_wars.sh

8. Copy all files not mentioned in the previous step under projects/rtview-server from the old installation to the new installation.

9. Execute projects/rtview-server/update_wars in an initialized command prompt and copy the generated jars to SolacePubSubMonitor/apache-tomcat-*-sl/webapps or your application server.

10. 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:

• update_wars.bat

• update_wars.sh

11. 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

12. Copy all files not mentioned in the previous 2 steps under projects/rtview-manager from old to new.

13. Execute projects/rtview-manager/update_wars in an initialized command prompt and copy the generated jars to SolacePubSubMonitor/apache-tomcat-*-sl/webapps or your application server.

14. In the previous installation, projects/rtvservers.dat was used for both projects/rtview-server and projects/rtview-manager. In the new installation, this has been split into projects/rtview-server/rtvservers.dat and projects/-rtview-manager/rtvservers.dat. If you modified the projects/rtvservers.dat in your previous installation, apply the Solace monitor changes to projects/rtview-server/rtvservers.dat and the RTView Manager changes to projects/rtview-manager/rtvservers.dat.

15. If you are using the Solace Event Module:

• Copy rtvapm\solmon\soleventmodule\conf\soleventmodule.properties from your old installation to your new installation to keep your old configuration. This configuration has been moved to the Solace DATA COLLECTION tab of the Configuration application. The next time you run the Configuration Application and save your properties files, the properties will be automatically transferred to rtview-server/project.properties*. After that, the soleventmodule.properties file will no longer be used and all further configuration changes to the Solace Event Module must be done through the Configuration Application.

• Copy the rtvapm\solmon\soleventmodule\config\log4j2.properties file in your old installation to projects\rtview-server\soleventmod.log4j2.properties in the new installation. All further changes to the Solace Event Module logging configuration should be done in projects\rtview-server\soleventmod.log4j2.properties.

16. If using HSQLDB, copy projects/DATA in your old installation to projects/DATA and projects/rtview-manager/DATA in your new installation.

17. Add new CacheMetric column to your alert database as described in the release note for TN24246.

18. Alter the Solace history database tables as described in the release note for TN24464.

19. If your previous installation included LDAP integration

• Copy apache-tomcat-*-sl/lib/ldapUser.jar from the old installation to the new installation.

• Copy apache-tomcat-*-sl/conf/server.xml from the old installation to the new installation.

• Copy apache-tomcat-*-sl/conf/Catalina.properties from the old installation to the new installation.

20. 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 changes to the logging configuration should be made in projects/sl.log4j.properties.

21. Start up the new installation using the start_servers script under bin.

22. If you entered secure connection properties in the RTView Configuration Application CUSTOM PROPERTIES tab, they will continue to work with no changes. However, it is recommended that you remove those properties from the CUSTOM PROPERTIES and enter them in the Solace CONNECTIONS tab for easier editing in the future. The truststore information can be entered on the SECURITY tab.

23. 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), then Restart Servers to save and apply your changes.

• Click on the RTView Manager server and reapply all changes you made in the previous version.

24. 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.