upgrading from 5.5.2 to 6.5

hello folks,
i am about to upgrade our system from 5.5.2 to 6.5 on windows.
i have a list of wht i need to do to make it work.
it s major upgrade and i dont want it to be painful. i just want to see if anybody had this experience before? and if he/she had any hard time with anything while upgrading?
is there something that s very important that i need to pay attention to?
any suggestions or advice before we start?
any input is very appreciated.
thank you.

Find more posts tagged with

Comments

nipper

Check the docs. IIRC, you need SP4 (or something like that) on 5.5.2 to upgrade to 6.5.

You will also want to consider running iwmigrate. That will convert your backingstore. That is optional, but is highly recommended.

Take your time, it is not that horribly difficult.

Andy

Nicholas

It is un-predictable, what problems could be arise, it entirely depends on how you are approaching. As suggested (by Andy), reading docs etc would help you to understand. Also things are depend on what type/size/conf you have on your existing implementation. You might raise specific questions, could give more relevant answers.

Hope this help

Thanks Nicholas

Frederik

We upgraded 5.5.2 to 6.5 on Solaris in 2006Q2. Took us some 2-3 months to prepare (we tried to be thorough), we faced at least a handful of documented & undocumented issues and problems.

perl version change, different char encoding behaviour in scripts (for everything except ASCII content)
custom menu items - different inputs
no way to install TS6.5 by commandline, without user interaction
workflows - file path of selected files start without (or with) a forward slash, unlike before
problems when opening the 5.5.2 store in 6.5 (some in 5.5.2 deleted files were showing up again)
you really should iwmigrate or restart from scratch your backing store
converting some iw.cfg configs (menu items...) to UITK
discovering the event subsystem database growth rate idiocy (disable it or use separate RDBMS)
templating: hidden containers no longer hidden
iwov_xslt tag broken (due to perl change)
you need to upgrade OD also (if you're on OD5.x) - at least the sender.
distribution of the new visualformat to our locked down winxp workstations.
... and probably a bunch of other issues that don't come to mind right away

test, test, test!

I believe I posted at the time about all these problems, and so have others. So search if you need info on the above, and upgrading in general.

CRB

thank you very much for the answers, yeah as you said, it s huge upgrade so i m sure it will take time, and alot of documentation and testing to get it working.
if anybody things about any other issues, is welcome to add them.
again thanks alot.

dtheimer

I would suggest upgrading a development/test Environment first and conduct a series of custom commands, workflows, etc. to expose any issues before going right to product with a difficult process to back out- common sense but from your posting it is not clear your path. And since you are asking the question I am guessing you have not made a first attempt.

If you are on Windows watch your OS version to your TeamSite version - many times the TeamSite version has issues with changes in made in the Windows OS.

Steps I would follow:
1. Read
2. Plan
3. Test
4. Execute
5. Start planing for an upgarde to 6.7.1

CRB

yeah i havent started yet. just in the process of planning