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; } } }

Upgrade from TS 6.7.1 SP1 to TS 7.1 on Win Server 2003

punitrb

Hii...
We are planning to upgrade from TS 6.7.1 SP1 to TS 7.1 on Win Server 2003.
Can anyone suggest on the things to check out for and good place to start this from like documentation, etc.

Of course we can have the Interwoven support help us out. But before that we are looking for someone who would have followed this upgrade path.

Also our existing setup uses wft files for workflows which would now have to be built using workflow modeler, how big of an effort that would be, any ideas ?
Thanks

Find more posts tagged with

Comments

nipper

Depends on if this was ever converted. What the the original rev of TS you used ? If this was upgraded from 6.5 you may want to run iwmigrate.

WFT will work on 7.1, converting to WFM is probably a good idea but not a trivial task.

Check the 7.1 doc bundle, there is a who thing on upgrading.

punitrb

Yes we had TS 6.5 earlier. I'll check the TS 7.1 documentation. Thanks for the info.

nipper

run iwhome/private/bin/chkFatDir.ipl

That will tell you if you need to run iwmigrate or not.

Adam Stoller

Hii...
We are planning to upgrade from TS 6.7.1 SP1 to TS 7.1 on Win Server 2003.
Can anyone suggest on the things to check out for and good place to start this from like documentation, etc.

Of course we can have the Interwoven support help us out. But before that we are looking for someone who would have followed this upgrade path.

There are numerous KB articles and Forum posts regarding steps to follow for doing this - though it definitely helps having someone who has knowledge of both versions of the product and [preferably] who has performed this kind of operation before.

Also our existing setup uses wft files for workflows which would now have to be built using workflow modeler, how big of an effort that would be, any ideas ?
Thanks

You only have to "convert" WFTs to WFMs if you want to do so - the existing WFTs should work largely unchanged (there may be some internal and/or external code that needs to be modified based on changes in the product, but that tends to be fairly limited in terms of scope - mostly having to do with the changes in role management).

If you want to convert your WFTs to WFMs - I suggest you go through the process of fully documenting the before / [desired] after results before starting to do so - and I would expect it to take anywhere from 1 to 4 weeks per workflow to convert (time varies based on complexity of workflow, skill of the person doing the conversion, and to what degree you intend to adopt the java paradigm over re-using existing Perl code)