HyperServer Server Farm Mode-2
In this mode there is one master HyperServer with several slave HyperServer instances which form a HyperServer server farm cluster. Difference from Mode-0 is that new sessions are redirected to the slave servers by redirecting the application URL to the slave servers.
Please see Cluster Operation Modes for more details.
Standalone Server and Windows Service
In this mode configuration is similar to configuration we've already discussed in the previous section Standard HyperServer Cluster. With a difference that you need to make these configurations for each slave HyperServer instance. No configuration is needed for slave HyperServer instances. In this mode each HyperServer instance will also be the WebSockets server for its own Nodes. This means that all WebSocket connections will be distributed among master HyperServer and slave HyperServer instances. This may make the whole cluster more scalable in this regard because each HyperServer instance will only serve WebSocket requests for its own Nodes.
If you recall from the previous section the only needed setting is to set a proper value for the server_direct_url parameter in master HyperServer CFG file and all of the slave CFG files. Obviously for each server this setting can be different.
[hyper_server]
server_direct_url=http://localhost:8077ISAPI or Apache Module
For this mode we can only recommend Using a Dedicated WebSockets Server when you deploy your HyperServer in form of ISAPI or Apache modules.