Home → Installation and System Configuration →

6x upgrades

• Edit

steelej

28 Nov, 2011 04:20 PM

The last three upgrades or maybe more (I'm currently upgrading to 6.10.6) have required full installs rather than the simpler upgrading of the current installation. Is this now the norm?

1. 1 Posted by Lee Roberson (F... on 28 Nov, 2011 05:12 PM

   

   Just curious -- why did they require full installs?

   We usually use the ROOT.war option, just delete everything in webapps and drop the new ROOT.war in there and start Cascade up. That's how we've (almost) always done it, with the exception of upgrades to components outside of the Cascade application itself (like Tomcat upgrades and JVM upgrades that come in the bundled install).

   • Edit

2. 2 Posted by steelej on 28 Nov, 2011 05:14 PM

   

   I use the windows.exe. It no longer offers the option to upgrade, just the full-install.

   • Edit

3. 3 Posted by steelej on 28 Nov, 2011 05:16 PM

   

   Here's a screen capture. There should be a box to click on upgrade current installation.

   • capture.jpg 34.3 KB
   • Edit

4. 4 Posted by Lee Roberson (F... on 28 Nov, 2011 05:18 PM

   

   Maybe because they fixed some Windows service bugs and want people to re-install to get them. Notably, the issue with the JVM not starting with UTF-8 character sets enabled (causing jumbled WYSIWYGs when special characters are used) and setting new, better default memory limits. Maybe they will have an official answer though.

   Knowing you're on Windows helps though -- if you have a test server I suggest trying the method I mentioned above for upgrades, it's quick and very easy.

   • Edit

5. 5 Posted by steelej on 28 Nov, 2011 05:19 PM

   

   I may give it a go. Thanks.

   • Edit

6. 6 Posted by Lee Roberson (F... on 28 Nov, 2011 05:23 PM

   

   It's a legit complaint, I'm on the other side of it -- I should have mentioned this drawback: The downside of ROOT.war upgrading is they can't force me to re-install, so I actually don't get updates to those outside files and need to know when something changes so I can do a full re-install from the actual installer. That has only happened recently in the last few versions with the image resizer and these service changes. My resizer was broken when I upgraded the version that included it because the code for it was in Cascade but the right JVM version was not installed to my server. Support helped me figure out that was why it wasn't working though.

   • Edit

7. 7 Posted by Joel on 28 Nov, 2011 05:24 PM

   

   Lee is correct in his statement, as we started packing Tomcat 6 within our installers which effectively forces an upgrade to Tomcat 6. As for when the "upgrade" option will return to the installers, unfortunately I cannot say.

   Thanks!

   • Edit

8. 8 Posted by steelej on 28 Nov, 2011 05:26 PM

   

   Thanks.

   • Edit

9. steelej closed this discussion on 28 Nov, 2011 05:26 PM.