FairCom Replication JSON RPC API

Configuration

The replication API requires a running Replication Manager Server. You will find this server in the Replication Manager package. Its executable name is called Memphis as a metaphor for a central management hub. Similarly, all methods in the API are prefixed with ctMemphis. "Memphis" is a synonym for "Replication Manager."

See the Replication Manager Guide for steps on configuring and running the Replication Manager Server.

Replication Manager option for connecting by IP Address

The Replication Manager normally communicates back to servers under its control via their hostname. On networks without an internal DNS, it may be necessary for the Replication Manager to communicate with controlled servers via an IP address instead. The DBENGINE_CONN_BY_IP keyword facilitates this feature.

The Replication Manager Server checks for this keyword and updates the DBEngine table.

JSON RPC API

This feature impacts ctMemphisGetDBEngines, ctMemphisPersistDBEngine, ctMemphisGetReplPlansDetails, ctMemphisGetArchivedReplPlansDetails, and ctMemphisGetDBEnginesByGroup web APIs. See the web API documentation (serverAPI.txt) for details.

C++ API

This feature also impacts the FCREPLDBEngine class with the extra Getters and Setters for this information. Please refer to fcReplDBEngine.hpp for details.