nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite 5.5.2 to 6.1 upgrade experiences

NathansDIS

Hello-

We are getting ready to upgrade our Teamsite 5.5.2 SP5 server to teamsite 6.1. This server is running on Windows 2000 SP4 and we are also running OpenDeploy 5.6 and DataDeploy 5.6 on this server as well.

Does anyone have any success or horror stories to share regarding this(or similar) upgrade scenario? We are currently working up a task list for this upgrade and are looking for known gotchas and/or omissions in the documentation. Thanks in advance for your input.

-Nathan

WA DIS

Find more posts tagged with

Comments

Adam Stoller

Is this a development server or a production server?
If it's a production server - have you tried migrating any/all of your 5.5.2 customizations to a development 6.1 server?

If not - STOP - do NOT upgrade a production server from 5.5.2 to 6.1 without having gone through a trial run on a development server first.

You'll want to make sure all your custom menu items work as desired in CCPro
You may want to create variants of these items for use within CCStd
If you currently remove certain OOTB menu items in WDP, you'll have to do a bit more work to make that happen in CCPro / CCStd

You'll want to make sure all your CGI code (custom menu items, cgitask scripts, cgi-callouts) work as-is. Things to look out for:
1. any code that accessed information from $cgi->{form}{...}
2. any code that assumes that you are provided an archive-rooted vpath (e.g. /default/main/...) - because this will now be a server-rooted vpath (e.g. //ts-server/default/main) and you will have to adjust your code accordingly.
3. cgi-callouts on metadata capture form that assume they will have a handle on the file being tagged (AFAIK - this is now unsupported - there's a FR for this though)

You'll also want to make sure any FormAPI code you have still functions correctly (I've got a case open now for a problem I'm having - but it *might* be an environment issue rather than a product issue)

That's the basiscs - then you get to finesse work like changing your DCTs to conform to the new datacapture6.0.dtd, additional configuration in the templating.cfg to adjust what shows up on the rendered DCT form, playing around with stylesheets and such, etc.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

NathansDIS

Thx for the info Fish-

The first server is our customer's dev server but from an administrative standpoint it is a production server. If I was going to create a lab server and install the software we are running, is there a known process we can use to copy the configuration and content from our production server to this lab server for upgrade testing?

I assume we would want to have the server be a member of the same domain. Would we want to mirror the local groups on the lab server to match those on the production server?

Thx, nathan

Edited by NathansDIS on 04/09/04 12:26 PM (server time).

mstevens

I performed an upgrade from 5.5.2 to 6.1 on our dev server . We were at TS SP3 so our migration path included the installation of SP4. The installation itself went off with out a hitch. But I did have to spend sometime updating different config files. Such as custom menu items which are no longer handled in iw.cfg. One thing I did notice, the branch value in available_templates.cfg no long works?

Migrateduser

Nathan,

If the TS5.5.2 services are still running when you run the TS6.1 installer, the installer will change the TS services startup type to "manual" and prompt you to reboot the system. However, the 6.1 installer doesn't check for OD and DD services. So you need to change the OD and DD services to "manual" before you run the 6.1 installer. The bottom line is that all the Interwoven services should be stopped during the 6.1 upgrade.

Adam Stoller

I haven't seen any problems with the branch_list section of the available_templates.cfg

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

You can either try to replicate the existing environment entirely on a DEV server and then upgrade it and deal with all the customization issues - or you can create a vanilla 6.1 DEV environment and work on transferring your customizations from your PROD system to the DEV system. In either case you'll want to keep good notes on what you did.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

to add to fish's comments.

one of the most annoying things is the need to put regexes on appropriate categories in templating.cfg.

but - if you use a wrapper for custom menu items that will ned to be working from CC PRO, everything *should* work - but as fish says - you are *strongly* advised to try everything on a test server

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU