Configure
Configure Replication Manager
The FairCom Replication Manager is distributed in a .zip
or .tar
package — for example, FairCom DB.<platform>.ReplicationManager.<build>
.
Note
If the server has both SERVER_NAME
and SERVER_PORT
configured, it will always use the SERVER_PORT
, so even if it is a local machine connection, it will use TCP-IP instead of shared memory.
Enable replication by inserting the following lines into the
ctsrvr.cfg
file:Note
The lines enable the plugin that handles web communication (
services.json
) and the agent that performs the replication (ctagent
).; Plugins PLUGIN cthttpd;./web/cthttpd.dll PLUGIN ctagent;./agent/ctAgent.dll
Use the
ctagent.json
andservices.json
files to configure the replication plugin:Note
A replication plugin runs in the FairCom server and executes all data replication.
If you are running Replication Manager on the same machine as the FairCom DB engine, you will need to adjust the ports so they do not conflict. Select unused values for
"listening_http_port"
and"listening_https_port"
. The ports available on your machine will depend on your environment. A good starting point is to simply add1
to each of the port numbers listed in the configuration file.If you want to experiment with replication in your lab, you can set up Replication Manager and two FairCom DB servers on the same machine. In that case, all three servers must use unique ports.
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" ] }