TCE Web Socket Listener

If TCE applications are to be operable via a browser, the TCE Web Socket Listener must be set up on a server.

The TCE Web Socket Listener communicates with a TCE application that runs in a browser via HTML 5 Web Sockets. It is thus the remote point of the data packets sent via HTML 5 Web socket. Data packets are sent over a specific port. To circumvent the limitations of the firewall, the data packets can also be sent via the http port 80 or https port 443. But it is also possible to specify another port. If data packets are to be sent over port 80 or port 443, the computer accepting the data packets must not run competing services that also listen to incoming communication through that port. Therefore, in this case, IIS (Internet Information Service) or similar applications must not bind to port 80 or port 443.

If the connection is to be made via HTTPS, a certificate must be available on the receiving server in the certificate store, whose display name corresponds to the CertDisplayName entry specified in the registry. Please note that calling the server via https requires a changed entry (wss: / instead of ws: /).