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

Content from older versions of TeamSite

shahzamaj

Will DCR content from TS6.5 work fine with TS6.7.2 or TS7.2 ?

If not, then is it possible to update existing DCRs to be compatible for newer versions ? How to update existing DCR for the newer version of TS ? Is there a tool available from TS or is it to be done manually ?

Can someone please explain the process ?

Thanks

Find more posts tagged with

Comments

Rick Poulin

FormsPublisher hasn't changed (noticeably) since 6.5. There should be no problem with your upgrade unless you've made some customizations to your DCTs that rely on JavaScript DOM hacks or similar things that circumvent the API published by IWOV.

Expanding on your question, the bigger story is migrating your content store. To my knowledge, the store format is the same so you should be able to lift & shift the store to a new server (or patch directly on top of your server, but I wouldn't recommend that without testing it elsewhere and/or backing up your install and store) -- but I haven't explicitly migrated a 6.5 store to 7.2 myself yet.

shahzamaj

So how do we migrate the content from TS6.5 to TS7.2 ?

Only by using migration tool iwmigrate ? We can not simply copy it from one version to other. Is there any other way of migrating content ?

To my knowledge, the store format is the same so you should be able to lift & shift the store to a new server

Now by this statement you mean, install the newer version of TS and fit content store on it, right ?

What do you mean by lift and fit ? How do I copy or shift entire content store on to newer version ? I have never done this, so have naive questions.

Thanks

nipper

The store will work as is. You may want to run iwmigrate because of performance improvements. There is a script you can run that will look at the backingstore and tell you if you will benefit from the upgrade, check the release notes.

new_report.rptdesign

Rick Poulin

By "lift and shift" I meant have ServerA be your current TS 6.5 box and ServerB be a new TS 7.2 box. Optionally run iwfsshrink on ServerA to minimize the size of what you're copying. Then shut down IW services on both servers, copy the iw-store folder from ServerA on top of the one in ServerB, then restart IW services (and then run iwfsck). If you're concerned with upgrading the store (for performance reasons as stated by nipper), then before the copy, rename your store to something that won't be there on the new box, and only copy that folder from within the iw-store directory. Then you can activate the store on ServerB using iwstoreadm and run iwmigrate on it (and restore the original name of the store if you want).

The alternative is to backup your current ServerA, then upgrade your box using the IW installer, and then run iwmigrate and iwfsck and iwfsshrink. Simpler process but much more risky if you only have the one production TeamSite server and nowhere to test this first.

vpatel

FormsPublisher hasn't changed (noticeably) since 6.5. There should be no problem with your upgrade unless you've made some customizations to your DCTs that rely on JavaScript DOM hacks or similar things that circumvent the API published by IWOV.

Expanding on your question, the bigger story is migrating your content store. To my knowledge, the store format is the same so you should be able to lift & shift the store to a new server (or patch directly on top of your server, but I wouldn't recommend that without testing it elsewhere and/or backing up your install and store) -- but I haven't explicitly migrated a 6.5 store to 7.2 myself yet.

I would disagree somewhat with the FormsPub changes from 6.5 to 7.2. Your DCTs will continue to work for the most part - as long as there aren't any out-of-the-ordinary customizations. You should refer to the release notes for changes related to standard FormAPI methods -- there were some methods that were deprecated in favor of newer ones when they standardized FormsPub and TagUI on the same DCF framework. Additionally, if you are using TPLs (not XSL PTs and wanting to take advantage of some of the newer functionality -- make sure you evaluate what the impact is of doing so. Bottom line is that 100% as-is to as-is move (from entire TS perspective) would work for FormsPub (again given you dont have any out-of-the-ordinary customization) but in order to take advantage of new features (XSL PTs, DCT Search n Replace, Tabs, Container Collapsing, updated FormAPI, etc.) you'll be looking at some relevant changes.

For the actual content store, like Nipper said iwmigrate is NOT required (rather optional).

HTH!