Obsolete Pages{{Obsolete}}
The official documentation is at: http://docs.alfresco.com
High AvailabilityReplicationContent Store
Clustered servers have to share content across the instances by replicating the content. This article discusses some of the available options, as well as the design of future or desired components.
While the org.alfresco.repo.content.replication.ReplicatingContentStore (see Content_Store_Configuration) will replicate new content added to the store it will not automatically perform an exhaustive traversal of existing content in the primary content store and push it to the secondary stores. For this task you'll need to configure the org.alfresco.repo.content.replication.ContentStoreReplicator:
<bean id='contentStoreReplicator'
class='org.alfresco.repo.content.replication.ContentStoreReplicator'
depends-on='localDriveContentStore, networkContentStore' >
<property name='sourceStore'>
<ref bean='localDriveContentStore' />
</property>
<property name='targetStore'>
<ref bean='networkContentStore' />
</property>
</bean>
which tells sets up the replicator to copy content from the localDriveContentStore to the networkContentStore, but we still need a trigger to start the job:
<bean id='contentStoreBackupTrigger' class='org.alfresco.util.CronTriggerBean'>
<property name='jobDetail'>
<bean class='org.springframework.scheduling.quartz.JobDetailBean'>
<property name='jobClass'>
<value>org.alfresco.repo.content.replication.ContentStoreReplicator$ContentStoreReplicatorJob</value>
</property>
<property name='jobDataAsMap'>
<map>
<entry key='contentStoreReplicator'>
<ref bean='contentStoreReplicator' />
</entry>
</map>
</property>
</bean>
</property>
<property name='scheduler'>
<ref bean='schedulerFactory' />
</property>
<property name='cronExpression'>
<value>0 0 03 * * ?</value>
</property>
</bean>
In some cluster configurations, the option to share content directly via a filesystem(s) doesn't exist. If the machines are all live within the cluster, then it is not possible to push the content from one server to another using rsynch or some other delayed mechanism. Instead, the content must be pulled onto the server that requires it. Alfresco servers already have a DownloadContentServlet that is able to access content using NodeRef and path based references.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.