migrating workareas from 5.5 to 6.0

read my parallel subject about iwmigrate Smiley Happy

if you don't care about modified files, etc, I'd tar'ed and copied the workeareas and reattached the EAs

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

srvijayanandh

Right,

Me too thought of taring it & uploading to the 6 server. But i was not clear how to set up the EAs?

Should i write a script to fetch them from old server & then attach them to the workarea thts copied.

thanks,
Vijay

I am attaching 2 files -

to save EA - saveattr.ipl workarea(s) > file
to set EAs - setattr.ipl file

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

another file attached

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

srvijayanandh

Thanks a lot Greg

What ever happened to the iwcpwa script that was part of the 5.5.2 migration package?
I seem to recall that it wasn't perfect, but I don't remember what it did / didn't do.
I'd suggest tracking that down and at least using it as a base for developing an improved script...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

IMO, that script is strange. it does not retain permisions in some of the cases, as admitted in the docs... and it's not good enough for me

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Hi,
I did a iwmigrate successfully between two 5.x teamsites. I am trying to use saveattr.ipl but does not do anything ? May be I am using it wrongly ?

./saveattr.ipl /iwmnt/other/main/ELMS/WORKAREA/temp_workarea > /tmp/other_exttr.txt

please help,
Thanks,

When I did iwmigrate, it successufully created temp_workarea. I need to copy the workareas from sourceTS to destinationTS. Having trouble to use iwcpwa as both the TS are 5.5.2 version. Please suggest.

Thanks,

The saveattr.ipl script [most likely] is written to be used in a two-phase process.
1) the way you've run it - to capture the EAs from the various files in the first store and create a 'script' to be used to on the target side.
2) depending on how the script is written, either you supply the output from the first run on the command line of the second run, or the second run is the actual running of the output from the first run. This is to *set* the EAs on the various files on the target side.

If you can show up the first 3-5 lines of /tmp/other_exttr.txt - it will be pretty easy to tell you what the 2nd step will look like.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

I'm not sure if iwcpwa really cares about both versions being 5.5.2 - but if it does - it's not too difficult to write a script to capture all the workarea information from one server and have it output a script to be run on the target server to create all the workareas with the correct attributes. The same, or a different script, can be used to create a tar (or zip) file of all the modified files (since the last edition converted) which can then be extracted on the other side.

It's not too hard to write Perl scripts for doing this kind of thing.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Hi,
Thanks for the info. But /tmp/other_exttr is coming as a 0 byte file. saveattr.ipl looks like it will save the EAs to a file. Also iwcpwa seems to be for pre 5.5
It gives a message (Error, you cannot use a 5.5.X TeamSite server as the source)

Well, if you look at the code used for iwcpwa - you can probably write your own script based on it that should do exactly what you want.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Hi,
Just checked iwcpwa is a binary utility. How to get as ASCII file.

Hmm - my bad - I thought it was a Perl script.
You can basically create a script that captures all the relevant information and tar's up the contents and then manually transfer it to the other server and untar and apply the EAs - or, if you're using OD6 you might be able to just do it as a deployment with the EAs being carried over for you.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

saveattr.ipl - is the first part of the process. setattr.ipl - the second one.

always worked for me...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Hi Greg,
How do you run the saveattr.ipl, and setattr.ipl . Can you give me example command.

Thanks,

<iw-home>/bin/iwperl  <iw-home>/custom/bin/saveattr.ipl /default/main/mybranch/WORKAREA  > blah.attr


<iw-home>/bin/iwperl  <iw-home>/custom/bin/setattr.ipl  blah.attr

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Hi Greg,
It works fine. Actually two things I noticed. It only captures attributes for the files that have extended attributes(Which is fine as iwextattr is meant for that).
Secondly we need to give complete path to the WORKAREA. I was trying to give the branch level.

Now, my problem is we have many branches, sub-branches and multiple workareas in each subbranch. How do I capture in a single file. or should I go for branch.attr as output file.

Thanks,

Hi Greg,

Thanks a lot, It works fine. Actually two things I noticed. It only captures attributes for the files that have extended attributes(Which is fine as iwextattr is meant for that).
Secondly we need to give complete path to the WORKAREA. I was trying to give the branch level.

Now, my problem is we have many branches, sub-branches and multiple workareas in each subbranch. How do I capture in a single file. or should I go for branch.attr as output file.

Thanks,

You can capture the attributes in STAGING, but you then need to adjust the output of the first run to apply the EAs to files in a specific workarea - and then when you submit that workarea you can do a Get Latest in other workareas to pick up the changes.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com