How do I Configure Apache HTTP Server and WebGateWith Pramati?

A general practice often seen in development environments is to have a Web server cater to the static pages and use the application server to deal with dynamic content. Pramati Server allows developers to integrate a number of third party products with its Server through a plug-in called WebGate.

In this section, we will look at how to configure Pramati Server WebGate, a plug-in for Apache. WebGate is available for Apache HTTP Servers as well as Microsoft IIS. The plug-in is provided by Pramati and can be downloaded from the Pramati website. Apart from the normal behavior shown by the plug-in (that is, redirecting pages to other back-end servers), the plugin can also be configured to perform Load Balancing.

Apache is one of the most widely used Web servers available for both Windows and Unix. The WebGate plug-in allows requests to be proxied from an Apache Server to Pramati Server. WebGate enhances an existing Apache installation by providing a method to transparently access Pramati servlet engine.

How do I Configure WebGate?

The pramatiplugin.props file contains configuration parameters required for serving dynamic content from the Server. It is located in the directory <APACHE_ROOT>/conf/. The parameters stored as key pairs are:

Table 1: Parameters stored as key pairs

Parameter Description

Logging This parameter can take three values - None, Medium, or Verbose. The default log level is medium. Log files are not generated if this value is None. For log level none, no log file will be created.

MaxLogFileSizeInMB Maximum size of each log file. If given less than 1, only one log is maintained.

NoOfLogFiles Number of old log files to be generated/kept after the size of the current log file exceeds its maximum size. <logfile> is the latest and the previous versions are renamed as <logfile>1, <logfile>2, <logfile>3,... and so on.

LogFileName The logFile to which WebGate will write the logs. Here, the file name should be given relative to <APACHE_ROOT> directory. The default log file is <APACHE_ROOT>/logs/pramatiplugin.log. To override the default log file, the file path relative to <APACHE_ROOT>/ should be provided. The string <APACHE_ROOT>/ is attached by default the new logfilename.

AddClientHeaders This option enables forwarding of client headers, useful to identify the IP headers. Add X-Forwarded-For Header.

WebGateHost This is a comma-separated list of machine names on which the Pramati Server is running. For example, Host:port.

MaxSockPool The maximum number of sockets used by the plug-in to connect Pramati Web Server. The default is 10.

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. Default is false.

PluginInstallationHome The plugin installation directory. The directory from which web-config.xml is picked up.
Note: This directory should also contain the required jars. Apart from these, the web-config.xml file would be needed to configure enhanced Load Balancing. Also, if tracing is used, the plugin-home directory should contain the trace.props file.

How do I use Connection Pooling of Pramati Server?

Instead of creating a new socket from the plug-in to the Web container of Pramati Server, a specified number of sockets can be created at start up and reused. This number is set in the pramatiplugin.props as MaxSockPool. See table above.

Related Topics:

Parameter	Description

Logging	This parameter can take three values - None, Medium, or Verbose. The default log level is medium. Log files are not generated if this value is None. For log level none, no log file will be created.
MaxLogFileSizeInMB	Maximum size of each log file. If given less than 1, only one log is maintained.
NoOfLogFiles	Number of old log files to be generated/kept after the size of the current log file exceeds its maximum size. `<logfile>` is the latest and the previous versions are renamed as `<logfile>1, <logfile>2, <logfile>3,`... and so on.
LogFileName	The logFile to which WebGate will write the logs. Here, the file name should be given relative to `<APACHE_ROOT>` directory. The default log file is `<APACHE_ROOT>/logs/pramatiplugin.log`. To override the default log file, the file path relative to `<APACHE_ROOT>/` should be provided. The string `<APACHE_ROOT>/` is attached by default the new logfilename.
AddClientHeaders	This option enables forwarding of client headers, useful to identify the IP headers. Add X-Forwarded-For Header.
WebGateHost	This is a comma-separated list of machine names on which the Pramati Server is running. For example, Host:port.
MaxSockPool	The maximum number of sockets used by the plug-in to connect Pramati Web Server. The default is 10.
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. Default is false.
PluginInstallationHome	The plugin installation directory. The directory from which `web-config.xml` is picked up. Note: This directory should also contain the required jars. Apart from these, the `web-config.xml` file would be needed to configure enhanced Load Balancing. Also, if tracing is used, the plugin-home directory should contain the `trace.props` file.


© Pramati Technologies 2007	Runs on Pramati Server \| Feedback \| Legal