Install replication manager

Extract the package onto your server file system.

The package contains centralized replication components (the Replication Manager controller, database, and browser‑based graphical tools).

Edit the config/ctagent.json configuration files on the FairCom DB, FairCom Edge, and/or FairCom RTG server nodes to point to the Replication Manager.

Ensure replication is enabled for each database server node by updating the licenses on the server nodes.

Once the Replication Manager package is downloaded, unzip the package.

Observe the directory:

Enable replication by inserting the following lines into the ctsrvr.cfg file:

; Plugins
PLUGIN cthttpd;./web/cthttpd.dll
PLUGIN ctagent;./agent/ctAgent.dll

These lines enable the plugin that handles web communication (services.json) and the agent that performs the replication (ctagent).

Use the ctagent.json and services.json files to configure the replication plugin:

ctagent.json

{
	"embedded": true,
	"log_file": "agentLog.txt",
	"memphis_server_name": "MEMPHIS",
	"memphis_sql_port": 7000,
	"memphis_host": "localhost",
	"memphis_database": "MEMPHIS",
	"ctree_check_mask": "*.dat;*.idx;*.fdd;*.fsd",
	"inactive_timeout": 600
}

services.json

{
	"listening_http_port": 8080,
	"listening_https_port": 8443,
	"ssl_certificate": "./web/fccert.pem",
	"document_root": "./web/apps",
	
	"applications": [
		"ctree;ctREST.dll",
		"AceMonitor;ctMonitor.dll",
		"SQLExplorer;ctSQLExplorer.dll",
		"ISAMExplorer;ctISAMExplorer.dll",
		"ReplicationManager;ctReplicationManager.dll"
	]
}

Optionally enable diagnostic logging by adding the following lines to ctreplagent.cfg:

diagnostics logship
diagnostics logread

The replication agent supports optional diagnostic logging for its log ship and log read threads. When diagnostic logging is enabled, these threads write messages to ctreplagent.log to indicate the offset that the log ship thread has written to the copy of the log files, and the log read thread is reading. The offset=[a,b,c] values in the log read message are (a) the requested log read offset, (b) the last byte actually read, and (c) the last requested byte to read. (b) and (c) are equal if the full amount was read (that is, bytesread is equal to size). We expect these log read offset values to always be less than the log ship's current write log position. These example messages show an expected situation: the last byte read by the log read thread is 0x789ab, which is equal to the last byte written by the log ship thread as shown in the "write to log copy position" message.

In the ReplicationManager folder, launch Replication Manager by executing memphis (Linux) or Memphis.exe (Windows).

Open your other c-tree servers (faircom.exe, ctreesql.exe, ctreeEdge.exe, or ctsrvr.exe).

In a web browser, enter a URL using this format https://hostname-of-your-server:8440/ReplicationManager/ — for example, https://localhost:8440/ReplicationManager/.

Observe the login page for Replication Manager with the username and password fields automatically filled in — for example, User: "admin", Password: "ADMIN".

Once logged in, observe the interface described in this section.