topic Re: Transfer (Replication) in 3.4 in Alfresco Archive

Transfer (Replication) in 3.4

loftux — Fri, 29 Oct 2010 11:30:09 GMT

I wanted to try out the Transfer / Replication in 3.4.b (I'm testing a build from HEAD).And it all looked so easy when presented at Devcon in Paris…I can't really find any documentation of the steps needed to get this going.Server A (target)So, in share-config-custom.xml, I put all the repository ID

Re: Transfer (Replication) in 3.4

mrogers — Fri, 29 Oct 2010 12:58:41 GMT

That should be sufficient.

Have you created "testtarget" in the default group folder? I've found with share that I tend to create a folder too high up.

Did you see and fill in the metadata for the hostname, port etc.

Re: Transfer (Replication) in 3.4

loftux — Fri, 29 Oct 2010 13:31:58 GMT

I did create a new "testtarget" and changed to use this new target (called servera) instead for the replication job. This time it worked. They both have the same information on about host, username etc. Only difference was that the first one I initially created using Alfresco Explorer. That form does not have username/password. Found that out, and entered them using Share.

I tried again to create a target via explorer, adding username/passwd in Share, this time it worked. So guess it was a non-repeatable error.

Only thing I'm missing now is to be able to specify target parent node, say if I want to replicate from one source site to several target sites. Requirement is to have separated Data Rooms (ie Sites). I guess I can do that by replicate from my one source site to the corresponding site on the target server. Once on the target server, I can use rules and aspects to make it available in different sites. But have to investigate further what are my best options here.

Re: Transfer (Replication) in 3.4

mrogers — Fri, 29 Oct 2010 13:47:36 GMT

There's no way to specify "where" on the target the transferred nodes go. The transfer system tries to maintain the same paths and node refs. And it is a one to one relationship between source and destination.

Actually that is not fully true since Web Quick Start and the transfer unit tests have some hackery that allows you to transfer from one folder to another on the same repo, however that's very much a "back door" which relies on over-riding the transfer service implementation.