Multiple server instances
Run multiple FairCom server instances on one computer
Important
Separate instances of the FairCom server cannot share any files, server names, licenses, or ports.
Each instance must be individually licensed with its own license file.
Each instance must be installed in a separate folder so that each has a unique set of server, configuration, and data files.
Each instance must have a unique server name.
Each instance must have unique communications ports.
Each server UUID must, in fact, be unique.
Give the FairCom server a unique name
On most FairCom products, the default server name is
FAIRCOMS
.On FairCom MQ, the default server name is
FCEDGEMQ
.
Navigate to and open the
ctsrvr.cfg
file.Update the
SERVER_NAME
value to the server name of your choice.; Server Name SERVER_NAME FAIRCOMS
Save your changes to the
ctsrvr.cfg
file.
Configure each server with unique ports
See Configure ports to change the ports you are using for each instance of the FairCom server.
Note
Port conflicts are the most common problem with running multiple instances of FairCom on the same computer. The FairCom server has many ports that are changed in several different configuration files. Be sure to change all ports that you are using and to use ports that are not in use; otherwise, port conflicts can prevent you from communicating with the FairCom server.
Assign a unique UUID
Delete the metadata.json
file located in the <faircom>/data
folder.
When you start the FairCom server it will be assigned a unique UUID.
Note
When a server starts up, if it does not already have a UUID, one is assigned that uniquely identifies it.
The UUID is stored by default in the <faircom>/data
folder in a file called metadata.json
. Deleting metadata.json
and restarting the server resets the server UUID by creating a new one.
Caution
If you duplicate a server folder or copy the data folder from one server to another without deleting the metadata.json
file, this will result in a duplicate UUID, causing unpredictable results. In particular, if you are using the Replication Manager, the two servers will be seen as the same server.
To remove a duplicate server UUID, delete metadata.json
in the data folder of one of the servers, then restart the server to reset the UUID.