Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
TeamSite 6.1 Full Install vs. Upgrade
rapid
W2K.
We plan to upgrade to TeamSite 6.1, SP1 (from TeamSite 5.5.2, SP3) and are doing all the pre-upgrade planning and test.
I wanted to hear any opinion\recommendation on whether to do a Clean Install(uninstall teamsite 5.5.2 completely) vs. Upgrade from 5.5.2.
Of course, we will do the uninstall in the correct order. We have an inventory of our custom files, config files, etc which we will check and apply again. The path for perl modules has changed which we will need to account.We have a backup server to handle the content store copy.
Have i missed anything?
Thanks.
Find more posts tagged with
Comments
lhdavis
I think the safest bet would be to go the upgrade to 5.5.2 SP4 or SP5, then to TS 6.1 (I think you can go there directly but check the manual). You should still backup all of your customizations and config files. I think this approach would be the best bet for your backing store (and your sanity). Plus it's the "supported" path if something goes wrong with the upgrade.
I would definitely suggest loading TeamSite 6.1, SP1 on a DEV server somewhere and testing all of your custom scripts rigorously (not sure if this is part of your current plan or not). I have found that along with the perl path changes some of the TeamSite modules have changed as well (see WFTask.pm, AddFiles subroutine for example).
Besides that, the UI change is significant, especially if you've gotten used to plain ol' WebDeskPro. Good luck!
Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov
gzevin
we have upgraded our server (on Solaris, though).
as Luke said, do test all your templates/workflows/custom scripts... and forget about CC Standard, unless you have just a handful of files
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU
rapid
Thanks for the advice.
Yes, we have the entire Dev server testing as part of our plan.
Also, we don't plan to use CCS anytime soon.
Actually, we tried it on 2 Dev servers and this is what we found...
Full Install:
---------------------------
Had problems with 6.0L. But is now working fine with 6.1 SP1. still testing.
Of course, we had to copy back all our custom stuff,etc. But i have
documented this.
---------------------------
Upgrade from 5.5.2 to 6.1:
---------------------------
Seemed to work fine till 6.1, SP1.
Had an issue when generating... Got the error....
Command iw.formspub.generate not found in the command descriptors
Was trying different things (rebuilding applications,etc). I read that someone had tried reinstalling SP1 and errors got resolved. So, we tried to uninstall SP1 but were getting errors while uninstalling.
Finally, had to rebuild the server.
i know this problem may be unrelated to full install\upgrade.
A consultant from Interwoven had recommended a clean install. Especially since we
have also previously upgraded from 5.0.1 to 5.5.2 before and his reasoning was to clean out old stuff.
So, right now, we are leaning towards a clean install.
Of course, this does not matter as much as making sure all current stuff is working.
Will decide after a bit more testing.
Maybe i should have mentioned this before. But did not want to bias anybody's opinion. ;-)
mogoo
rapid-
Did you end up having to do a clean reinstall or did you find a fix?
We just upgraded from 5.5 (dev server), and we're getting the same generating error:
"Command iw.formspub.generate not found in the command descriptors"
...plus we can't save forms...
"Command iw.formspub.save_valid_form not found in the command descriptors"
Any ideas?
rapid
We tried different things including uninstallling the SP but did not work.
I would suggest contacting support and ask them for a fix.
For us, rebuilding the server(uninstalling everything and reinstalling) is working till now.
Thanks.
Rishi Athalye
TeamSite 5.5.2>>6.1 on W2K
NathansDIS
We did an inplace upgrade from TS 5.5.2 SP5 to TS 6.1 on Windows 2000. We did have to modify some of our workflows and templates to get them to work with the new perl version(mostly internationalization code.) I also found that paths in available_templates.cfg are case sensitive in 6.1 where they were not in 5.5.2. Just a couple things to look out for.
-Nathan
Washington DIS
RonaldV
Hi,
did anybody have any other experiences (good or bad) on the upgrade of TS552 to T6.x?
I'm very curious what I can expect from the upgrade.
Thanks, Ronald
TS552 sp4, Win2k
TS552, Win2k
OD560