The table shows FairCom’s default mapping of each protocol to a TCP/IP port protocol. You can use services.json to configure how a FairCom server maps ports to protocols. You can assign any port to any protocol, and you can assign different ports to the same protocol. You can disable any configured port and service or remove them.
When FairCom provides multiple services over the same protocol, they are listed together in the same row.
Default mapping of each protocol to a TCP/IP port and one or more services
| Service | Default port | Protocol | Description |
|---|---|---|---|
|
JSON Action APIs Browser Apps |
8080 | HTTP & WebSocket | FairCom's app server listens to this TCP/IP port to process HTTP and WebSocket requests. It is not secured by TLS. |
|
JSON Action APIs Browser Apps |
8443 | Secure HTTP & WebSocket |
FairCom's app server listens to this TCP/IP port to process HTTP and WebSocket requests. It is secured by TLS. The HTTP header returned by all JSON actions sets the content type to application/json ( |
| MQTT | 1883 | MQTT |
FairCom's MQTT broker listens to this TCP/IP port to process MQTT messages. It is not secured by TLS. All MQTT brokers default to this port. If you have installed another MQTT broker, MQTT messages will go to it, and FairCom's broker will likely get a port conflict error. |
| MQTTS | 8883 | Secure MQTT | FairCom's MQTT broker listens to this TCP/IP port to process MQTT messages. It is secured by TLS. |
| MQTTWS | 1884 | MQTT over WebSocket | FairCom's MQTT broker listens to this TCP/IP port to process MQTT messages over the WebSocket protocol. It is not secured by TLS. |
| MQTTWSS | 8884 | MQTT over Secure WebSocket | FairCom's MQTT broker listens to this TCP/IP port to process MQTT messages over the WebSocket protocol. It is secured by TLS. |
|
ISAM API CTDB API |
5597 | TCP/IP | FairCom's ISAM server listens to this TCP/IP port to process ISAM and CTDB function calls over FairCom’s wire protocol. It is optionally secured by TLS using the configuration file, ctsrvr.cfg. |
|
SQL API JDBC ODBC Direct SQL for C/C++ |
6597 | TCP/IP | FairCom's SQL server listens to this TCP/IP port to process SQL requests over FairCom’s SQL wire protocol. It is optionally secured by TLS using the configuration file, ctsrvr.cfg. |
|
SQL API ISAM CTDB JDBC ODBC Direct SQL for C/C++ |
FAIRCOMS or FCEDGEMQ |
Shared Memory |
FairCom's ISAM and SQL servers listen to a shared memory channel to process ISAM, CTDB, and SQL calls. Shared memory only works when the calling application runs on the same computer as the FairCom server. Because shared memory is faster, client libraries for FairCom ISAM, CTDB, and SQL APIs automatically use Shared Memory instead of TCP/IP when the client and server are on the same computer. The Shared Memory channel name is " |
- FairCom's JSON Action APIs support most server features, including creating databases, tables, indexes, inserting/updating/deleting records, querying data using JSON and SQL, sending and receiving MQTT messages, configuring the server, managing accounts and access rights, configuring data connectors to retrieve and push data to devices and software, transforming inserted data automatically, running server-side JavaScript code, managing data change streaming, and so forth.
- FairCom's connectors, such as OPC UA and Modbus, are not included in the table because they do not listen for incoming requests; instead, they connect to other servers to retrieve or push data.
- You can use services.json to configure the FairCom server to provide the same service over multiple ports, such as listening for JSON Action API calls over multiple ports.
- Shared Memory is not a TCP/IP protocol. Thus, it is not configured in
services.json. Instead, it is configured inctsrvr.cfg. - Since FairCom's ISAM and SQL protocols may use shared memory or TCP/IP, they are configured in
ctsrvr.cfg.