WebSocket Port Configuration for Standalone Deployment

This document introduces how to configure WebSocket ports in a standalone environment.

Note:

The FineDataLink project supports the container WebSocket solution. You are advised to check if the container WebSocket solution can be used first.

No user operation, manual configuration, or additional port opening is required. The system automatically uses the WebSocket built into the web container for connection, and the WebSocket connection shares the same port with HTTP.

Modifying Field Values

You (the super admin) can modify the WebSocket port through the FINE_CONF_ENTITY Visualization Configuration plugin. The settings take effect after you restart the server.

Note:

1. For details about how to modify field values in tables of FineDB databases, see FINE_CONF_ENTITY Visualization Configuration.

2. If you upgrade FineDataLink from versions before V4.0.6 to V4.0.6 or later versions, the WebSocket port/forwarding port remains the same as in the previous version.

Notes for setting the port number:

1. The port number of the WebSocket port/forwarding port supports multiple values.

2. The port number ranges from 1024 to 65535. If there are multiple values, separate them with commas (,). Example: [Port 1, Port 2, Port 3].

3. You are advised to set WebSocket Port to multiple values for port backup to prevent  port conflicts when multiple projects are deployed on one server.

4. Do not set the port number to 3389 (the port used for remote server connection).

5. Do not set the WebSocket port and WebSocket forwarding port to the same port number.

6. If there are trailing spaces in WebSocketConfig.port and WebSocketConfig.requestPort, the configuration will not take effect.

7. The WebSocketConfig.port and WebSocketConfig.requestPort parameters are case-sensitive. Wrong capitalization will prevent the configuration from taking effect.

Opening Ports

• If the firewall is enabled, you can either disable it or open the specific port.

• If the cloud server has a security group or similar network access control mechanisms, you need to set the ports to be accessible externally.

Restarting the Project

Restart the FineDataLink project.

To restart the project, you need to kill the processes running under the project, wait two minutes for ports to be released, and then restart the project. Otherwise, the restarting may fail.

Effect Display

The server will listen for connections in the following order: WebSocket port -> WebSocket forwarding port. If you are using the default ports, the server will try the following ports in sequence: 58888 -> 59888 -> 58889.

• If a port is successfully bound, the system will stop trying other ports.

• If none of the ports can be bound to the system server, the system will enter the deployment wizard page to guide you through modifying the listening port list, and related functions may be affected during this time.

• In this case, reconfigure the WebSocket port and WebSocket forwarding port until an available port is found.