Liquid UI - Documentation - 3.4 Implementing Load Balancing with Server

3.4 Implementing Load Balancing with Server


For scenarios in which there are more than two hundred users, Synactive recommends implementing load-balancing. Load balancing enables you to spread the work among two or more servers, thus reducing the load and optimizing your results. There are four possible scenarios for deploying Liquid UI Server and of these, two incorporate load-balancing. These scenarios are as follows.

Scenario I

This scenario incorporates a single, standalone Liquid UI Server and a single SAP Application server.

Scenario II

This scenario involves a Liquid UI Message Server and a single SAP Application Server.

Scenario III

This scenario includes a single, standalone Liquid UI Server and an SAP Message Server communicating with multiple SAP Application Servers.

Scenario IV

This scenario incorporates a Liquid UI Message Server and an SAP Message Server. The Liquid UI Message Server communicates with multiple Liquid UI Servers and the SAP Message Server similarly communicates with multiple SAP Application Servers.

The two Liquid UI Server scenarios that incorporate load-balancing are those that include either a Liquid UI Message Server or an SAP Message Server. It is important to remember that connecting to one SAP ERP system is not necessarily the same thing as connecting to one SAP ERP message server. Multiple application servers can be defined to distribute a load of a single SAP system (eg. PRD) via an SAP message server. Each of the scenarios is more fully described in the following sections.

 

Note: When using a load-balancing deployment such as Scenario II or Scenario IV, the same sapproxy.ini file must reside on each Liquid UI Server.

 
In addition, Liquid UI Message Server will run only on a Windows Server operating system such as Windows Server 2022.
 

Note: The Liquid UI Message Server does not support - end-user systems such as Windows 7.

 

Third-Party Load Balancers

You can use the Server in conjunction with third-party load balancers. The third-party load balancers known to work with Servers are as follows.

Company 

Hardware Specifications 

Software Specifications

A10 Networks

Physical and SPE appliances
Bare metal
Virtual appliances
Containers

Comes with Hardware components
HAProxy Technologies
Linux System Solutions

Anomalous behavior detection engine
WAF
Bot detection

F5 Networks + NGINX

2 CPU cores2
4 GB RAM
2x1 GbE NIC
500 GB HDD


Comes with Hardware components
Citrix

256 GB Memory
8x 100GE QSFP28 Ethernet Ports
50GE/100GE QSFP28: SR4 - Transceivers Support


Comes with Hardware components
Progress Kemp
32 GB Disk Space
2 x virtual CPUs
2 GB memory

SSL TPS - 10.9%
THROUGHPUT - 17.19%
SSL THROUGHPUT - 18.59%



Can't find the answers you're looking for?