Liquid UI - WS Reference Library

3.4 Load Balancing


Implementing load-balancing with Liquid UI 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 a SAP Message Server communicating with multiple SAP Application Servers.

Scenario IV

This scenario incorporates a Liquid UI Message Server and a 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 a 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 the load of a single SAP system (eg. PRD) via a SAP message server. Each of the scenarios is more fully described in the following sections.

Important: When using a load-balancing deployment such as Scenario II or Scenario IV, the same sapproxy.ini file must reside on each individual Liquid UI Server. In addition, Liquid UI Message Server will run only on a Windows Server operating system such as Windows Server 2008 - end-user systems such as Windows 7 are not supported.