Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
TS 5.5.2 to 6.5
jajtiii
We are having a major problem with the upgrade and I hope to get some assistance here.
(we already hired Interwoven Consultants, but their plan is not working and they do not seem willing to assist further, and I have submitted a Support issue, but no word yet and I need something asap (typical, eh?))
The problem revolves around the OS. We currently are running on Solaris 2.8. We are obtaining new Sun blades for the upgrade, which are all 2.9 (and not compatible with 2.8).
The problem is that we continue to get errors when trying to port our current modules to the 2.9 box. (port modules then run 5.5.2 SP 4 to make kernal changes.) It appears that TeamSite not only makes kernal changes when installed, but it goes out and makes configuration changes to all modules based on the OS version.
Since this failed, we decided to try to instead install 5.5.2 on the Solaris 2.9 boxes and go from scratch...unfortunately, 5.5.2 does not appear to be supported on 2.9 (no bin files for that version of Solaris).
This seems to mean that we cannot do an actual upgrade, but might instead have to build all of our boxes from complete scratch again.
If anyone at all has a suggestion, I would be very happy to hear it.
thanks,
jones
Find more posts tagged with
Comments
Adam Stoller
If you're switching/upgrading OS's at the same time you're trying to upgrade TeamSite - I'd very much recommend doing a clean installation on a separate box rather than trying to upgrade everything on a single box.
Aside from kernel modificiations - you also have to use a different version of the iwserver binary - and that binary needs to be configured using a CLT (the name of which escapes me at this moment) - so it's definitely more complicated than "just an upgrade".
The good news is that once you get the new box set up and installed - you can copy/move the entire 5.5.2 backing store onto the new server and TS6 will read it (once this has been done, you can *not* move the backing store back to the 5.5.2 server) -- this is generally much easier than trying to run iwconvert / iwmigrate
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
jajtiii
Thanks for your thoughts on this.
After further consideration, our team is going to take that exact approach.