Upgrading the Teamsite 6.1 to 6.7 in Solaris...

Hi all,

Can somebody help in providing the step by step process for upgrading the 6.1 to 6.7 (also Opendeploy 6.0) and the pre-cautionary measures that needs to be taken care.

Since this is the first time i am going to setup the environment. I may ask silly questions. Pls bear with me... Thanks....

Solaris Version :
SunOS hkgwscms01 5.8 Generic_117350-25 sun4u sparc SUNW,Ultra-80

Find more posts tagged with

Comments

Adam Stoller

Hi all,

Can somebody help in providing the step by step process for upgrading the 6.1 to 6.7 (also Opendeploy 6.0) and the pre-cautionary measures that needs to be taken care.

Since this is the first time i am going to setup the environment. I may ask silly questions. Pls bear with me... Thanks....

Solaris Version :
SunOS hkgwscms01 5.8 Generic_117350-25 sun4u sparc SUNW,Ultra-80

I believe, for TS, most of the steps are covered in the Installation Guide under "Upgrade" related sections.

Upgrading OD is, I believe, more straight-forward as I don't believe that there's been a significant amount of changes to the base functionality that would require extra explicit steps to be performed - however, I would start with the installation guide there too.

sara_team

Hi Fish,

Thanks for ur reply...

Yeah.... there are some points in documentation. I am expecting some real practical experience. some precautionary measures or regualar problems or kind of backout plans....

kk_aa_rf

Some of the issues that we have encountered and the steps we have taken to resolve:
- TeamSite 6.7.1 is officially supported on Solaris 10. So please upgrade the os version to 5.10 and apply the latest patch.
- Teamsite should be installed in GLOBAL zone. After upgrading the OS run
zonename from the command prompt to verify what zone you are in.
Refer to
http://www.sun.com/software/solaris/howtoguides/containersLowRes.jsp to know more about zones.

- PAM doesn't work too well with 6.7.1. We used direct LDAP access
- iwaccessmigrate does not update the tsuser.xml. you have to run iwusermigrate for that
- you may have to do a chown of your stores to iwts if you are doing a non root install.
- If you have OpenDeploy/DataDeploy installed, you have to update deploy.cfg to add TeamSite version.
- Make sure that you do not change ownership of any directories/files unless it is really needed.
- If you have ui customizations, you have to create a new file userops_custom.xml for the custom menus and links to be displayed. This file is in the directory ./local/config/lib/content_center/customer_src/etc/conf/customer.
- There is a bug with TinyMCE editor that prevents is working well if it is used in a replicant.

Other things to consider:
1. Do the upgrade in a development or test server first.
2. Regression test all your DCTs & workflows and deployment.

sara_team

Thanks for ur information.....

Anyways am going to upgrade only on Solaris 8. (no other go....)

So i cannot use Teamsite 6.7.1 now. Are the given steps is also applicable for TS 6.7 in solaris 8?

What are the files needs to be back up?
Whether the owner ship for iwstore should be iwts or the existing one is enough?
And what are the other thing should i keep in mind while upgrading?
If the upgradation fails, how can i roll it back to the existing one?

Sara

eehall

If you are using Data Deploy, I believe you will run into some issues that can be resolved by upgrading to OD 6.1.1

Frederik

- There is a bug with TinyMCE editor that prevents is working well if it is used in a replicant.

Can anyone elaborate on this? Problem description? Conditions that trigger the problem? Many thx.