Rocket Modern Experience (formerly LegaSuite)

Load-balancing:

To increase overall efficiency, use load-balancing to route each connection to the optimal Web engine. The following list describes the most common load-balancing configurations:

Static load-balancing: If you have a small number of users, start the Web engines and the Web application server in advance. Then to make sure that each connection request is routed to a specific Web engine, specify the address and/or the port of the endpoint in the URL or in the initial web page.

Web server load-balancing: If you have many users, configure the Web server to control which Web engine handles each connection request. For example, Apache Tomcat has a mod proxy balancer that uses a configured pattern to match each connection request with a specific Web engine. For more information, see the following article on the Rocket Community portal: How to Configure Native Websocket Passthrough and Load-Balancing for WebUI in Apache on Windows

External load-balancing: If you have many users, consider using a load-balancer server. Then when the load exceeds a predefined threshold – for example, CPU usage or number of connections – use a software program such as HAproxy to start additional instances of the Web engine.

Pre-requisites for load-balancing:

• Your Administrator will need to configure 'sticky sessions' for the load-balancer. This setting means that a session / connection from a user will always be routed to the same servlet and the same engine.  This is required because the engine will retain information about your session; thus, to be able to continue from where you left it's important to touch the same server with a subsequent call in the session.
• Your chosen load-balancer must support web sockets.

• Performance Considerations - User Base & Topology
• Performance Considerations - Application Design

Further documentation for Rocket Modern Experience Web Edition can be found on our docs portal: https://docs.rocketsoftware.com/