![]() |
|
Pramati WebGate plugin can be configured to balance load among several backend nodes. One advantage of configuring load balancing at the plugin level is that it would avoid an extra hop to the Load balancer node and the load balancing takes place right at the plug-in level.
To learn more about concepts of load balancing, read Request Dispatcher Architecture.
To enable load balancing of the WebGate plugin, unzip the downloadable archive at a convenient location on the machine on which it should be configured. Let this directory be <webgate_home>. This section takes a look at how to configure the WebGate plugin to balance load. The load balancing feature can be enabled at the plugin level by enabling the EnhancedLBEnabled property.
Here’s a sample pramatiplugin.props with descriptions of each properties inline:
Table 1: Definition of properties for a plugin.props file
| Property Name | Description |
| EnhancedLBEnabled | To enable/disable the enhanced LoadBalancer which maintains Session stickiness, balances load in a round robin fashion and performs failover by resending the request to another node. It can also detect a restarted node. If enabled, the configuration property WebgateHost from pramatiplugin.props will not be read. The nodes information will be picked up from the web-lbconfig.xml file. |
| PluginInstallationHome | The plugin installation directory. The web-lbconfig.xml file needed to configure the enhanced LB and the LB.jar will be picked up from this directory. Make sure that this path is in the system path. |
| EnhancedLBContexts | If EnhancedLBEnabled is enabled, then a list of contexts which need to be redirected to the back-end Pramati Servers is specified here. For example, EnhancedLBContexts /admin. Use '@' for all contexts. |
Note: The web-lbconfig.xml file (in the <webgate_home> directory) should be configured to provide information about various backend nodes and their port numbers.
Related Topics:
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |