Product Documentation

Installing FairCom Products

Previous Topic

Next Topic

Operational Environment

The FairCom DB Server for Windows is named ctreeace.exe (or ctsrvr.exe). FairCom DB Servers prior to, and including, V11.0 were distributed with support for the following communication protocols:





TCP/IP (using an IPv6 socket)


Shared Memory


TCP/IP (Data Camouflage support - Deprecated)


Note: FairCom DB V11.5 and later support TLS/SSL - See Transport Layer Security Secures Data in Transit between Network FairCom DB Clients and Servers

The FairCom Server for Windows defaults to the TCP/IP protocol. To activate any other protocol, use the COMM_PROTOCOL keyword in a ctsrvr.cfg file, discussed in Advanced Configuration Options. Use the name shown in the table above under COMM_PROTOCOL Keyword as the token following the COMM_PROTOCOL keyword in ctsrvr.cfg.

Note: The COMM_PROTOCOL option specifies the protocol used for ISAM connections. By default, local SQL connections use shared memory unless the SQL_OPTION NO_SHARED_MEMORY keyword is specified. See the COMM_PROTOCOL for more information about the communication protocol for SQL connections.

The COMM_PROTOCOL keyword disables the default protocol, so if you want to load the default and another protocol, each must have a COMM_PROTOCOL entry in ctsrvr.cfg. For example, to load all supported communication protocols for the FairCom Server on Windows, add the following lines to ctsrvr.cfg:




Note: If COMM_PROTOCOL is specified for one protocol, all protocols to be used must be specified. If no COMM_PROTOCOL is specified, the FairCom Server uses the default, F_TCPIP.

The shared memory protocol eliminates the overhead of the TCP/IP protocol stack resulting in very fast communications. The only drawback is the client and server must reside in the same physical memory space. For client server applications running on the same machine, this can result in communications performance increases of almost 500% over TCP/IP in some instances.