Deploying Your Replication-Enabled Project - BloomReach Experience - Open Source CMS

This article covers a Hippo CMS version 11. There's an updated version available that covers our most recent release.

04-07-2016

Deploying Your Replication-Enabled Project

We discussed how to enable your project for replication. The distributions that you created there can be deployed in the usual way. Follow the installation instruction manual for this. As was mentioned during the discussing of how replication works, even when you don't run a cluster on the source, the repository must be configured to write its events to a journal. You will find instructions on how to set that up in the installation manual mentioned above.

After you have successfully deployed both the source and target distributions of your project to the respective environments you must first of all initiate a full sync. Note that this is only necessary during the first deployment. After subsequent upgrade deployments there should be no need for full syncs anymore, as long as the upgrade did not introduce new, to be replicated content.

The sync will cause the uuids of the JCR nodes on the source and the target to correspond. This is a prerequisite for replication to work properly. Another precondition is that the version of the replication addon is the same on the source and on the target. In fact, in general the version of your project must correspond due to the fact that the node type definitions (CNDs) must be compatible.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?