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 to TS 6.7.1 SP1

ttriemst

Hi all,

I am upgrading from TS 6.5.xx to version TS 6.7.1 SP1 (on solaris 10), and I wanted try and get some feedback from the DevNet community. I have had a few conversations with the technical sales engineer from Interwoven, and was told that there were no changes to the backing store and that I should be able to "mount" the drive where my iw-store is located. I have read through the release notes, and it does not seem like there are to many changes (other then workflows) that I should be worried about. I was curious if anyone has moved to version 6.7.1 SP1 and ran into any gotcha's that wer not planned for or if it was as simple as it seems? I currently have about a dozen simple Template and Workflows, which I am not all the worried about. If I need to re-create them, it would not take long.

Thanks and any input would be great.

Find more posts tagged with

Comments

nipper

For the most part, everything is backwards compatible. I had a couple issues with the new flex roles and limiting access to DCRs based on role, but that was easily resolved.

That being said, there are some new functions/features that you may want to take advantage of, and if you do, it may require some work.

The backingstore itself had no trouble when I went from 6.5 to 6.7.1

Adam Stoller

Hi all,

I am upgrading from TS 6.5.xx to version TS 6.7.1 SP1 (on solaris 10), and I wanted try and get some feedback from the DevNet community. I have had a few conversations with the technical sales engineer from Interwoven, and was told that there were no changes to the backing store and that I should be able to "mount" the drive where my iw-store is located. I have read through the release notes, and it does not seem like there are to many changes (other then workflows) that I should be worried about. I was curious if anyone has moved to version 6.7.1 SP1 and ran into any gotcha's that wer not planned for or if it was as simple as it seems? I currently have about a dozen simple Template and Workflows, which I am not all the worried about. If I need to re-create them, it would not take long.

Thanks and any input would be great.

The highlighted statement is, I believe, erroneous - in that once a backing store has been processed by a 6.7.1 server it can no longer be processed by a 6.5 server - so if you're going to mount your 6.5 store on the 6.7.1 server as a temporary secondary store for iwmigrate purposes - you should mount a copy not the actual store.

That being said, the FlexRoles will have an effect on your existing customizations if you did anything involving roles (custom menu items, workflow drop-down lists for selecting users of a certain role, etc.) - It's not that difficult to do, but it does involve changes to code and/or configuration files.

You also have to get used to the paradigm shift of having users log in with a static role throughout the server - instead (other than Master's) a user's role(s) is based on what branch they're in (e.g.: a user can have admin rights in one branch, editor rights in another, author in yet another, and no rights in any other branch). To handle it properly you should plan it out carefully so you know how you want to distribute the roles and users.

6.7.1 also offers advances in the management of TS-Groups - which were introduced in 6.5.

RonaldV

Hi,

the conversion-script of the user-roles/user-groups towards the new role-model CAN give your normal editor-users admin-privileges for the branches they have access to.

This seems like an unwanted effect to me. Anyway it's best to read the (complex) documentation in this area.

Good luck, Ronald

Migrateduser

Hi All,

I hate to say but we are still on v5.5.2 and planning for upgrading to v6.7.1. I got more or less ready with the plan except the backing store.

Any one tried with it. From the KB articles it appears we need to first upgrade to v6.5 and then to 6.7.1 and we cant do a straight upgrade. I had a couple of discussions with Interwoven and it led me to the same conclusion. Could you share your thoughts please.

Thanks,

nipper

This is ugly at best. You have 2 choices, either multiple upgrades (I don't remember that you could go from 5.5.2 to 6.5, but if the docs say so), or you can do a fresh install and migrate code and content over.

The latter is much easier and IMHO a better solution. The question is how much history do you have and do you need ? That is a business decision that needs to be made. If you can import only a handful of editions per branch, then it is a good solution. If you need all 5000 editions, then no.

Migrateduser

Thanks a lot, We can convince business on the history. However by going the fresh server install way, will we be able to migrate over the content using iwmigrate tool or any other method. Thats where I read that we need to do step migrate 552 ->652->671

Migrateduser

Thanks for ur message, I know its ugly :-(

nipper

One other big advantage with the fresh install is that 5.X backingstores can often have hidden issues. Basically there may be some low level corruption that is unknown to you. Often that is not a huge issue, but if you do a fresh install then you get rid of those.

Andy

Migrateduser

On the same token, any one have a VOC or Concerns format from the business.

Migrateduser

Andy,

I did not still understood with fresh install how do we move the old backing store. Are you suggesting to write own scipts or iwmigrate tool can do for us. Little dumb here :-)

Phanie

Hi Vengo, there was an article recently on upgrading which Adam & all contributed to the post. Mostly all your queries should be/ rather discussed in that post. Link http://devnet.interwoven.com/forums_vb/showthread.php?t=23750&forumid=11
or search for "teamsite 6.7.1 upgrade questions"

--
Phanie