Parameters

Once you've installed the plug-ins, you will need to configure the Web server to work with WebLogic. This section contains a listing of the directives available for configuring your Web server to work with your WebLogic.

You don't need to use all of the directives listed here, only those that you think would help you. To use a directive, include it in your Web server configuration file and restart the Web server. Note also that any log or debugging information will be written to the log file(s) associated with your Web server, not to the WebLogic server logs.

WebLogicHost

This parameter defines the WebLogic server or cluster to which the HTTP server will be proxying requests. If proxying to a single server, this directive takes the name of the WebLogic server handling nonstatic HTTP requests :

 WebLogicHost NT4-server 

WebLogicPort

This directive is used to tell the HTTP server what port to use when attempting to connect to the server specified with the WebLogicHost directive:

 WebLogicPort 7001 

WLLocalIP

If the HTTP server and the WebLogic server are running on the same host (usually a bad idea; definitely a bad idea on single-CPU machines), this directive tells them the IP address they should use to communicate with one another:

 WLLocalIP 127.0.0.1 

WebLogicCluster

If directing requests to a cluster, use this directive to specify the members of the cluster. The HTTP server will proxy requests to the servers on this list in round- robin order. Both the server name and port number should be specified for each host when using this directive; consequently, this directive takes the place of WebLogicHost and WebLogicPort . If both WebLogicCluster and WebLogicHost directives are present in a single configuration file, the value specified with the WebLogicCluster directive will supersede the WebLogicHost :

 WebLogicCluster NT4-server:7001,       RHat72-server:7001,ThirdServer:7001 

DynamicServerList

This directive takes one of two possible values, ON and OFF. When set to OFF, it will ignore the dynamically generated cluster list and use only those servers specified with the WebLogicCluster parameter on the HTTP server. Generally it should be set to ON.

 DynamicServerList ON 

WlForwardPath

Use this directive to tell the HTTP server which requests are to be forwarded to the WebLogic server. A value of "/" means forward all requests.

 WlForwardPath /dynamic 

PathTrim

Use this directive to tell the HTTP server to remove portions of the URL it received from the client before passing the client request on to the server. For example, say your PathTrim was set to remove the string "/dynamic", as in the following example:

 PathTrim /dynamic 

If the HTTP server received a request from the client containing the URL "http://www.mydomain.com/dynamic/page1", it would modify the URL so that the WebLogic server saw "http://www.mydomain.com/page1". This directive is applied before DefaultFileName and PathPrepend .

DefaultFileName

This directive specifies a default file that will be served by the WebLogic server. It is applied after the PathTrim but before the PathPrepend directives, if they are present.

 DefaultFileName frontpage.html 

PathPrepend

Use this directive to modify the URL received by the HTTP server from the client before passing them on to the WebLogic server. PathPrepend is applied to the URL after any changes made by PathTrim and DefaultFileName .

 PathPrepend /dyn 

TrimExt

Use this directive to specify an extension that will be trimmed from the end of the URL.

 TrimExt .html 

ConnectTimeOutSecs

Use this directive to place an upper limit on the time (in seconds) that an HTTP server will wait when attempting to contact a WebLogic server. For example, to wait 15 seconds, use

 ConnectTimeOutSecs 15 

ConnectRetrySecs

Use this directive to specify the interval (in seconds) that an HTTP server should wait after an unsuccessful attempt to contact a WebLogic server before making another attempt. This number should be less than ConnnectTimeOutSecs .

 ConnectRetrySecs 5 

HungServerRecoverSecs

This directive tells the HTTP server how long to wait for a response from a WebLogic server. At the end of this interval, the HTTP server will begin to consider the unresponsive server dead.

 HunServerRecoverSecs 240 

Idempotent

This directive takes two possible parameters, ON and OFF. If set to ON, the servers will fail over if they do not respond within the time specified by HungServerRecoverSecs . If set to OFF, the plugins won't fail over.

 Idempotent ON 

MaxSkips

This directive specifies the number of times an HTTP server will try to contact a WebLogic server before marking that server as "bad."

 MaxSkips 5 

Debug

Use this directive to specify the type and amount of information that will be sent to a log file. As the name implies, for performance reasons this directive should be set to a low level in production systems. The possible logging levels are:

OFF	No logging.
ON	Logs error messages.
HFC	Error messages plus H eaders F rom C lient.
HTW	H eaders sent T o the W ebLogic server plus error messages.
HFW	Error messages, plus H eaders F rom W ebLogic.
HTC	Error messages plus H eaders T o C lient.
ALL	All of the above are logged.

WLLogFile

This directive is used with the Debug directive. It specifies a file on the local machine to which information will be logged.

 WLLogFile /var/log/weblogic.log 

ErrorPage

Use this directive to specify an error page (other than the default, presumably) that is displayed to the client when the HTTP server is unable to contact the WebLogic server.

 ErrorPage /usr/local/apache/htdocs/whoops.html 

CookieName

This directive specifies the name of the WebLogic server session cookie. It should match the value set in the WebLogic server session descriptor.

 CookieName 

MaxPostSize

This directive specifies, in bytes, the maximum size of data posted with the POST method. A value of -1 means unlimited. This directive is generally used to stop denial-of-service attacks that overload the server with posted data.

 MaxPostSize 2048 

KeepAliveEnabled

This directive enables connection pooling between the WebLogic server and the HTTP server. Usually this will improve performance.

 KeepAliveEnabled true 

KeepAliveSecs

This directive is used to limit the amount of time an inactive connection from an HTTP server to a WebLogic server will be permitted. The value should match the corresponding value set in the HTTP tab of the Servers folder.

 KeepAliveSecs 30 

WLProxySSL

This directive can be set either ON or OFF. It should be set to ON when you wish to pass client requests for SSL communication through the HTTP plug-in to the WebLogic server.

 WLProxySSL ON 

SecureProxy

When you want to use SSL for all communication between WebLogic and the HTTP proxy, set this directive to ON. SSL communication is more secure but does incur a certain amount of overhead and will hurt overall performance. It is probably not necessary to enable this feature for traffic that takes place behind a firewall.

 SecureProxy OFF 

TrustedCAFile

This directive specifies the location of the file containing the certificate for the trusted certificate authorities.

 TrustedCAFile /some/local/file 

RequireSSLHostMatch

There are two possible values, true and false. If set to true, the proxy will require that the name of the host to which it is connecting match the Subject Distinguished Name field in the digital certificate of the WebLogic server to which it is connecting.

 RequireSSLHostMatch true