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

6.7.1 sp1 upgrade

tsatt

Hi All,

We are currently running TS6.5sp3 on solaris 8 and planning to upgrade to TS6.7.1sp1 on solaris 10. We do not use LDAP so far but want to use it. After going through here and there, below are the steps and question that I have.

0. Install and configure solaris 10 OS to be used as LDAP client
1. Load all users from old 6.5sp3 TeamSite server into LDAP
2. Copy the old backing store to the SAN device (we are using SAN)
3. Install TeamSite 6.7.1 on the new server and specify the location of the 6.5sp3 backing store during installation.
4. Stop Teamsite.
5. Configure iw.cfg to use ldap. (or would this be done automatically during installation)
6. Start TeamSite
7. Run iwaccessmigrate command to migrate all the roles. (or will it be run automatically during installation)
8. Stop TeamSite
9. Update the config files submit.cfg, autoprivate.cfg, templating.cfg, available_templates.cfg with the old info.
10. Start TeamSite
11. Install Workflow modeller
12. Install TeamSite search on new TeamSite server
13. Clean-up and re-index the backing store using iwmigrate (do we need to run it even though we were using 6.5sp3
14. Test all the functionality
15. Install 6.7.1 sp1

Questions:
Do we need to run iwidmap to map users or is that taken care during the installation as the users are present in LDAP?
Do we need to copy the uid files?
Do we need to run iwusermigrate command?
Do we need to run the migrate_non_root script or chmod/chown commands or that is taken care automatically as the backing store path was provided during setup?
Apart from the steps mentioned above are there any additional major steps that we are ignoring?

I will appreciate any advice, updates to my plan above.

Thanks

Find more posts tagged with

Comments

kg_brian

11. Install Workflow modeller

workflow modeler is just a client piece of software, you can wait till everything else is done... then install it on whatever PCs need to do development. Wouldn't really consider it part of the upgrade process...

Are you sure you want to migrate, and then upgrade to SP1? Why not put SP1 on the new server first, then migrate? Not sure if some of the tools are 6.7.1 only, but SP first seems more logical...

tsatt

I am not sure if I understood you right Smiley Sad

Are you saying to do a fresh install, complete all the configurations and make it work first and then activate the new backing store?

I thought it was not possible to install a service pack before installing a proper version I mean to install 6.7.1 sp1 I need to have 6.7.1 first?

Also since we need to migrate to solaris 10 from solaris 8 we would have to do a fresh install. is that correct?

Thanks

Adam Stoller

I am not sure if I understood you right Are you saying to do a fresh install, complete all the configurations and make it work first and then activate the new backing store?

I thought it was not possible to install a service pack before installing a proper version I mean to install 6.7.1 sp1 I need to have 6.7.1 first?

Also since we need to migrate to solaris 10 from solaris 8 we would have to do a fresh install. is that correct?

Thanks

Yes - you need to install 6.7.1, then 6.7.1 SP1, and then (probably) 6.7.1 SP1 Patch 1 (# 73875).

Yes - new server - fresh install.

Generally speaking - I do the base install and then fix the iw.cfg the way I want it before I do the reboot. Reboot and install the SP. Reboot again and do the patch and reboot again (I'm not sure if the 2nd and 3rd reboots are necessary on Solaris - they seemed to be needed when I did this on Windows last week).

I also prefer to use the existing store as a temporary 2nd backing store and do an iwmigrate from there into the brand new 6.7.1 SP1 + Patch default store.

Since you're doing a fresh install - iwusermigrate and iwaccessmigrate will not be run automatically. Once you're done with all the installs - copy the conf/roles/*.uid files to your new server and then run iwusermigrate to create them as TS users (then either manually go through them in the GUI or carefully edit the tsusers.xml file and set up their email addresses, preferred UI, etc.)

For setting up the access / roles stuff - you'll probably want to play around with the iwaccess CLT and build a script around it to traverse your branch hierarchy and set default roles (e.g.: editor or author) for all users of the groups associated with the branches (you can do this by group rather than by individual user - which is nice) - and then you can go through the GUI or create a distinct script to set up the special roles (e.g.: admin, etc.) for the select individuals on select branches.

There's probably more to it than that, but the above is off the top of my head.

tsatt

Thanks Fish

If we want to use LDAP, do we still need to copy the uid files to TeamSite? With LDAP, Is it better to maintain the user roles and group information in the LDAP or just the authentication info and configure the rest with TeamSite GUI.

Also would you like to add something to my original post?

Thanks for the info about the patch. I did not know that there is a patch available other than Service pack 1

Adam Stoller

Thanks Fish

If we want to use LDAP, do we still need to copy the uid files to TeamSite? With LDAP, Is it better to maintain the user roles and group information in the LDAP or just the authentication info and configure the rest with TeamSite GUI.

Also would you like to add something to my original post?

Thanks for the info about the patch. I did not know that there is a patch available other than Service pack 1

So you want to use the Non-OS User feature - I don't know anything about that with regard to user migration. Your best bet is to read through the documentation and contact Support.

Phanie

So you want to use the Non-OS User feature - I don't know anything about that with regard to user migration. Your best bet is to read through the documentation and contact Support.

hi tsatt, do you have any articles apart from the regular documentation suggesting setting up Non-OS user feature. did support suggest you anything.

Also can anyone please mention any issues that one could come across during this process or point me to the necessary artciles. we are planning to have non-os users in our setup.

--
Phanie

kajjubee

"Yes - you need to install 6.7.1, then 6.7.1 SP1, and then (probably) 6.7.1 SP1 Patch 1 (# 73875)."

Fish, I didn't find this patch (73875) listed under patches. Can you tell me where I can find it?

Thanks,
K

Phanie

"Yes - you need to install 6.7.1, then 6.7.1 SP1, and then (probably) 6.7.1 SP1 Patch 1 (# 73875)."

Thanks,
K

Mr K, to whom was your post for, I guess everyone was discussing abt non-os users in this one. Anyways there was a conversation previously in this forum regarding Patch 1, care to do a little bit searching ...

http://devnet.interwoven.com/forums_vb/showthread.php?t=23110&forumid=1
1 or search for patch 1 it would give you results

Adam Stoller

"Yes - you need to install 6.7.1, then 6.7.1 SP1, and then (probably) 6.7.1 SP1 Patch 1 (# 73875)."

Fish, I didn't find this patch (73875) listed under patches. Can you tell me where I can find it?

Thanks,
K

You have to go through the Products download section. For some reason they didn't put it under patches - go figure.

kajjubee

Thanks Fish.

Phanie, if you read carefully, that post was for Fish. And the topic is TS 6.7.1 SP1 upgrade so I thought it was relevant here.... Anyway, thanks for your help as well.

Cheers,
K