Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Migrating Files from a Sub-Branch to Parent Branch
rayvdz
Hi There,
I hope someone may be able to help us with this little problem we seem to be having.
We are using Teamsite version 5.0.1.0 7344 20020326 on NT 4.0.
Our current setup, whether it be right or wrong, is that all of our work is done within a single branch, which we call the BAU (Business As Usual) Branch. This single branch contains all of the assets for all our websites (6 including an Intranet site). This main branch is used for general BAU activity for daily releases to these websites.
We use sub branches to manage major application or content projects, which are deployed to our testing environments (system Test and UAT). When testing is completed on the sub-branch we integrate the changed files into the main BAU parent branch.
The sub-branches, when created, are obviously based off the BAU branch. There are a couple of issues that we are stuggling with here that I would love some advice on. The poblems seem to arise when we try to re-integrate the changed files with the main branch. We use the 'Copy to Area' functionality to copy all changed files to a workarea in the parent branch. From my undestanding, teamsite should be smart enough to only copy the files that have changed and notify me of differences between the sub-branch version and the parent branch. Instead, what is happening is that teamsite is telling us that files other than the ones we have changed are different. Here is an example of the file attributes of files that are supposed to be the same:
The Parent branch file properties:
STAGING: rolcreditcard_nms_1.jsp 514 8/21/02 11:46 LDNRMA00\2514
revision \main\bau\1
The Sub-branch file properites:
proj_r13: rolcreditcard_nms_1.jsprolcreditcard_nms_1.jsp 514 8/21/02 11:46 LDNRMA00\2514LDNRMA00\2514
revision \main\bau\proj_r13\3
This is exactly what appears in the file properities. As you can see the actual file properites ie date and time are exactly the same. so are file name and user but for the file name and user name being repeated.
What I would like to know is.... is this a bug? Should teamsite be working this way?
Help please....
Regards
Raymond van der Zalm
Web Solutions Consultant
Technology Services - eBusiness
Insurance Australia
Find more posts tagged with
Comments
Migrateduser
I believe it's working as advertised. Don't quite remember all of the under the cover ops but you should be able to do a Compare WA/Diff function from your sub-branch WA to a main branch's WA, provided that main branch's WA still have the same snapshot of the edition you branched off of. It'll show all of the modified files and you can copy it over to the main branch's WA. Afterward you can do a GetLatest to see if there's any conflict with the latest in main branch's Staging and merge any conflicts.
- Max
mchwang@yahoo.com
Johnny
Hi There Raymond!
TeamSite may recognise differences exist such extended attributes. Are any process that are occuring in between?
Perhaps there is a workflow task that sets some EA's or even a scheduled task that sets EA's aswell, say for example content retiring?
John Cuiuli
Consultant
Sydney, Australia
Johnny
Duplicate details does seem very strange.
Maybe one of the Interwoven guys have seen this before.
Could be a bug with 5.0.1. I did a search on the support site, but I didnt find anything.
There could some sort of file corruption inside your backing store. Try testing the situation under a test branch (and sub branch) to see if you get the same results. If you dont, you may have a backing store corruption.
If a corruption is suspected you can use the command line tool iwfsk. Please read the admin guide first though!!!
Another option is to migrate your content into a new branch and blow away the old one. To make sure you dont migrate any corrupted info (although it may not - iwfsk is probably better), move it to somewhere outside of the backing store, and back up the EA's aswell (There are scripts available on the support site to do this).
Then move the files into a new branch and apply the EA's.
John Cuiuli
Consultant
Sydney, Australia
rayvdz
Hi Johnny,
Thanks for your reply. Interestingly we have an interwoven engineer helping us out with a few things. Might try to get him to have a look at it.
What you have suggested, may be worth a try though...
Thanks
Raymond van der Zalm
PS great to hear from you again...
rayvdz
Thanks Max,
That is what I thought. A little strange that it is behaving the way it is.
Might log a call to Support!
Cheers
Raymond
Johnny
Interwoven Engineers ehhh...
Brett or Pete?
They are too expensive! ;þ
John Cuiuli
Consultant
Sydney, Australia