Solaris version for TS 5.5.2

Whats the recommended version for Teamsite 5.5.2 installation ? Is it 2.9 ?

Our current installation is running on Solaris 2.7 but our customer wants have it installed on Sol 2.9 when the system goes into production. Because of this we have to redo our staging server setup by first installing Sol. 2.9 and reinstalling TS and doing the setup/configuration again as its a requirement from our customer that the testing and production enviroments should be idenical in every respect.

One solution in mind is that we simply upgrade the OS from 2.7 to 2.9 through a upgrade script.

My questions:
First of all, does it really matter from TS perspective if the OS is Sol. 2.7 or Sol. 2.9 ? Is there any difference from Teamsite perspective ? Please note that Teamsite Templating & Opendeploy Admin and base servers are also installed on the same box.
Is the upgrade to 2.9 from an upgrade script same as installing 2.9 from scratch ?
If we actually opt for an OS upgrade script, will l this upgrade effect the TS server in any way ?

Thanks in advance for your input.

Find more posts tagged with

Comments

Adam Stoller

To the best of my knowledge (and a quick perusal of the TeamSite Administrator's Guide and Release Notes for TeamSite 5.5.2) - Solaris 2.6, 2.7, and 2.8 are officially supported, but Solaris 2.9 is *not* listed as being officially supported.

What does this mean? It means it ***might*** work on 2.9, but that Interwoven has not performed any official QA tests with that configuration.

Keep in mind that the OS version ***does*** matter - because TeamSite uses a virtual file system that operates at the kernel level, and if the change in OS version represents changes to the kernel with respect to TeamSite's virtual file system interaction - it requires code changes, builds, and testing before it can be said to be compatible.

So - unless you hear otherwise from a relaible source - I'd suggest that you do NOT upgrade your TeamSite server to Solaris 2.9 at this time.

--fish
(Interwoven Senior Technical Consultant)

tvaughan

I did an on-the-fly upgrade from 2.7 to 2.8 and the biggest gotchyas were making sure the correct kernel files were copied from your $IWHOME to the appropriate Solaris kernel directory. For example, if you look in your $IWHOME/install/iwinstall script, around line #960 you'll see some if-else statements regarding which wfs kernel file to copy to the /kernel/fs/ directory. All you need to do is go through that iwinstall carefully and make sure you copy the appropriate 2.8 files to the right places.

I did this on 3 separate OS upgrades and I've been working fine for 6 months.

Tom

Migrateduser

Tom, does the server need a reboot after you copy the correct kernel files? Is there any way we can get around with it?

We get the following error when we start TeamSite
ERROR: modload /kernel/fs/wfs returned 28

It's TeamSite 5.5.2 on Solaris 2.8.

Does anybody know what happens when TeamSite is reinstalled to the same location? Our situation is that we have TeamSite installed on a NAS device, we backed up the required files, OS was upgraded for the box, copied back the files, gave an error, copied kernel files and added wfs 181 to /etc/name_to_sysnum and now it gives the above error. So, would reinstalling TeamSite take a lot of our work and not mess up the existing backing store?

Thanks

tvaughan

Yeah, I'd imagine that a Solaris reboot would be in order. People will tell you that you "shouldn't ever have to bounce Unix", but in my experience, it is usually a good idea after a major op like this -- especially because you'd prefer to know that the machine can come back up after you've done the upgrade, instead of finding out about a problem a month or two after your install procedures are fresh in your mind.

In terms of the backing store, I think you should be able to do a complete overhaul of your TS installation and point your newly installed version at your old backing store. . . just make sure it isn't on a filesystem that gets blown away when you remove your old version.

Tom

Migrateduser

Thanks Tom. A Solaris reboot fixed the problem.

Actually after reboot, ran into another small issue. Everything started except the Web Daemon for UI, the /etc/defaultiwhome file should have been world readable and it wasn't, fixed that and everything started just fine.

I understood the second part of your reply to be:
In terms of the backing store, I think you should be able to do a complete overhaul (install) of your TS installation and point your newly installed version at your old backing store. . . just make sure it (old backing store) isn't on a filesystem that gets blown away when you remove your old version (of Solaris)
Is that correct?

Thanks a lot.