Deploying a Replication-Enabled Project

After you enable your project for replication, deploy the generated distributions using the standard deployment process. Refer to the Linux installation manual for detailed deployment steps.

Replication requires the repository to write events to a journal, even if the source environment is not clustered. The installation manual includes instructions for configuring the journal.

After deploying both the source and target distributions to their respective environments, perform a full synchronization. This step is required only during the initial deployment. For future upgrades, a full sync is not necessary unless the upgrade introduces new content that must be replicated.

Full synchronization ensures that the UUIDs of JCR nodes on the source and target match. Matching UUIDs are required for replication to function correctly. The replication addon version must also be identical on both the source and target. In general, the project versions must match to maintain compatible node type definitions (CNDs).

Disabling the Replication Source at Startup

Starting with Bloomreach Content versions 16.3.0 and 15.7.2, you can start source nodes with replication disabled. This is useful when you copy a database from production to a lower environment. In this scenario, starting the lower environment with replication enabled could cause it to read production target configurations and attempt to replicate data, which is not desired.

To start a replication source cluster node with replication disabled, set the following system property:

replication.disabled.on.source.at.startup=true
copy