Content Server Manual / Version 2304
Table Of ContentsThe Replication Live Server is a complete server installation with its own database instance, like a Master Live Server installation. The Replication Live Server differs from a Master Live Server in the following points:
A Replication Live Server needs a different license file, that defines the server type (live).
For a Replication Live Server you must configure the replicator properties (see Section 3.2.5, “Properties for Replicator Configuration” in Deployment Manual).
The content of a Replication Live Server is updated differently. The Replication Live Server is a replicated image of the Master Live Server. It receives changes from the Master Live Server and updates its database accordingly. In particular, it can track changes after an offline phase. The process responsible for content update is called the replication process or replicator.
The aim of a Replication Live Server is to remove load from the Master Live Server and enable a scalable delivery architecture. So, you can install any number of Replication Live Servers, each with its own database instance. The Content Application Engines (CAE) do not access the Master Live Server anymore but the RLS. Multiple CAE/web server pairs can be attached to one RLS.
Note
Do not modify the content repository of the Replication Live
Server
directly, either through one of the command line tools or
through Site Manager or
Studio.
All modification should be done by the automatic replication process.
While the user admin is granted write rights,
such rights should be exercised only when advised accordingly by CoreMedia support
in exceptional circumstances.
