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

Migration from TS6.5(Win2000) to TS6.7.2(Solaris 10)

chitresh

We are planning to migrate to TS6.7.2(Soalris 10 Platform) from TS6.5(Win 2000).Can we migrate the whole content store and the content OR do we need to do content entry on the new store?

Find more posts tagged with

Comments

Adam Stoller

We are planning to migrate to TS6.7.2(Soalris 10 Platform) from TS6.5(Win 2000).Can we migrate the whole content store and the content OR do we need to do content entry on the new store?

Interwoven has never provided a means of fully migrating the content store between Windows and Unix platforms - you would need to perform the content migration manually (or programmatically using manual mechanisms) yourself. As such, it generally becomes simpler / easier to do a "surface copy" of the staging area of each branch rather than try to figure out how to unravel each version of each file in each edition and attempt to preserve submit comments and somehow provide indications of who created the version / when it was created.

Have fun...

nipper

As Adam said you cannot copy backingstores over. Never happen. Do you have editions on the current backingstore ? How much history do you require ? I did a DOS -> Linux conversion recently.

If you chose any option other than copy staging area, then this can take a very long time. A customer asked me to do that recently. I explained the script I would need to write (something to walk down thousands of hidden editions, grab the changes, copy them over, submit, go to next). This would be quite a significant task (I estimated 6 weeks for 6 branches). As a consultant paid by the hour, this could be quite nice. As a customer paying for it, that made the decision quite easy. I copied the Staging areas.

Still there will be a significant amount of work, depending on how WFs, templates, deployment, CGIs, Formapi & call servers are written. There can be as little as minor changes required or very significant changes. When people use Y: instead of $iwmnt in Perl scripts, you have a lot of tedious work to do.

HTH

ANdy

RonaldV

Hi,

I was just wandering: wouldn't it be enough to run the iwidmap clt (to convert the old Win-uid's to the new Ux-uid)?

Or is there more involved in the conversion?

Ronald

nipper

Hi,

I was just wandering: wouldn't it be enough to run the iwidmap clt (to convert the old Win-uid's to the new Ux-uid)?

Or is there more involved in the conversion?

Ronald

Won't work. The backing stores are not compatible. So you have nothing to idmap.