Product: TIBCO Spotfire®
How to roll back Spotfire server hotfix?
If there is a need to roll back the applied Spotfire server hotfix for any reason, it is possible to revert it back to the version prior to applying the hotfix without any additional downloads.
Note: This approach is recommended to use only when the current applied hotfix does not contain any database scripts as this method does not help revert the database hotfixes.
The Spotfire Server installation directory contains a directory called "hotfixes" (under C:\tibco\tss\${version} ), which contains a folder for each Spotfire Server hotfix that has been applied on the server (such as HF-001, HF-003, etc.).
Each of these hotfix folders has a structure like the following:
hotfixes
HF-003
backup
tomcat
tools
The backup folder contains a snapshot of the prior hotfix Spotfire Server was on. If the Spotfire Server was on HF-005, and it is upgraded to HF-006, then a new folder called HF-006 would be created in the hotfixes folder. This would contain a backup copy for HF-005.
Here are the steps to roll back the server hotfix-
1) Stop the Spotfire Server.
2)Go to the {TSS_Installation}\${version}\hotfixes folder, and find the relevant hotfix that Spotfire Server needs to be rolled back to. For example, if you want to roll back to HF-003, go to the folder HF-004.
3)Go to {TSS_Installation}\${version} and make a backup of the tomcat,tools folders.
4)From {TSS_Installation}\hotfixes\${version}\backup\tomcat copy the "lib" and "webapps" folders overwrite the ones in the {TSS_Installation}\{version}\tomcat folder.
6)From {TSS_Installation}\hotfixes\${version}\backup\tools copy and overwrite the tss-tools.jar in the {TSS_Installation}\{version}\tools folder.
5)Start the Spotfire Server service.
6).Verify that Spotfire Server is now running on the rolled back hotfix by logging onto the Server Administration Console - Diagnostics tab - Spotfire Server Version.
Note:TSS_Installation is the directory where Spotfire server is installed.eg :- The default location is C:\tibco\tss
Comments
0 comments
Article is closed for comments.