topic Re: Replicate content using Replication Job and edit it on destination server??? in Alfresco Archive

Replicate content using Replication Job and edit it on destination server???

nenad982 — Wed, 09 Apr 2014 12:29:48 GMT

Hi all,is it possible to replicated document library from Share site from one server to another using Replication Jobs and after that to edit replicated content on destination server directly?So I would like to replicate content from one server to another, to "disconnect those servers" afterwords an

Re: Replicate content using Replication Job and edit it on destination server???

mitpatoliya — Mon, 14 Apr 2014 05:27:51 GMT

Yes It is possible to replicate document library from Share site from one server to another using Replication Jobs.
And as per the documentation from alfresco it is the source repository which gets locked up during job not the target repository so you should be able to add content to target repository after replication.

Re: Replicate content using Replication Job and edit it on destination server???

nenad982 — Mon, 14 Apr 2014 09:03:00 GMT

Hi mitpatoliya,

thanks for your answer.
It is not problem for me in which state is content during job execution. I have "problem" with default behavior of the content after job finishes. You are right I can add content on target server, edit it and delete it, but I can not edit, change metadata, delete content that was replicated from source server.

So my goal is to replicate content from source to destination and after that to use that content on destination (target) server normally (to edit it, delete it…). I don't want users to have experience that this content was replicated from another server at all, is that possible with replication jobs?

Thanks…

Re: Replicate content using Replication Job and edit it on destination server???

aaditvmajmudar — Mon, 14 Apr 2014 11:33:37 GMT

Yes, before start replication from source server to target server, you need to change one property in replication.properties(/alfresco/subsystems/Replication) file.

replication.transfer.readonly=false

By making this property as false, your target server will have replicated content as normal content (with all available actions).

Hope this helps.

Thanks,

If this post helps, please comment as "mark comment as useful".