Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD 4.5.2 to 6.0?
vikramk
I don't think I've seen this one covered, whats the best strategy to updating from OD 4.5.2 to 6.0.2? Can we jump from there without going via 5.6?
This would be on both W2k and Solaris
Find more posts tagged with
Comments
Migrateduser
You can do that, but it's a manual effort to convert your config files to the XML format.
OD 5.6 includes a tool called iwodcfg2xml that assists with config file conversion. (I'm sure there are DevNet threads on the use of this tool.) You might want to install OD 5.6 somewhere to get access to the tool, since it's not included in OD 6. The generated config files won't take advantage of new OD 6 features, but if they run in 5.6, they should run in 6.x.
Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
vikramk
Thanks Todd
Does 5.6 convert the config files automatically when it's installed if it detects 4.5.2? Or do we have to run the convertor manually anyway, to pass in paths etc
We do have 5.6 around so we have access to iwodcfg2xml but it may make sense to go to OD6.
If anyone has done this jump, let me know!
Vik
nipper
IIRC, the converter does notrun automajically, you run it from Unix/DOS command line. So
you *SHOULD* be able to copy them to a place where you can run the sciript.
However I do not know what files are needed, if it is only the config files you are OK,
otherwise it wil not work.
HTH
Andy
Adam Stoller
I suggest reading
this post/thread
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
legendproblem.rptdesign
vikramk
Very useful, I think we are looking at running 5.6 in parallel with 4.5.2.
Then to gradually turn off 4.5.2 as we have over 1200+ servers to migrate
Then we can start on getting 6.0 in...
Vik
Adam Stoller
You might as well look at using OD 6.0.2 rather than 5.6 - although 5.5.1 and possible 5.6 had a feature to allow you to fall-back to running an older version [4.x] of the software if still installed / and configured appropriately - you'd need to check the manuals carefully for that.
In either case, OD 5 and OD 6 use different installation directory structures than 4.x and also use different ports for the default of the deployments (I believe 4.x is 1701 and 5.x and 6.x is 20014) - as long as you use different ports you can have both 4.x and 5.x and/or 6.x on the same server without any problems.
It's generally recommended that you upgrade base servers first and the upgrade the target receiver nodes - however this doesn't really make since in the case of 4.x because there was no base server in that version of the product. So for that case you still need to keep the 4.x client-side utilities on your source server along with the new base server software and then you can start converting target servers over time.
I think you'll need to do a fair amount of reading and diagramming before you actually try to do any real implementation here ... make sure you truly understand what you are doing and how you are going to accomplish it otherwise you could end up with a very bad mess.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com