Technical data

Configuring the Apache HTTP Server Plug-In
Administration Guide 11-13
</Location>
An alternate way of proxying by path to multiple clusters would be:
MatchExpression /x
WebLogicCluster=server1:port,server2:port,server3:port,server4:
port|PathTrim=/x
MatchExpression /y
WebLogicCluster=server1:port,server2:port,server3:port,server4:
port|PathTrim=/y
MatchExpression /z
WebLogicCluster=server1:port,server2:port,server3:port,server4:
port|PathTrim=/z
Where the general syntax is
MatchExpression exp name=value|name=value
where exp=Mime type(*.jsp) or exp=/x(path)
and the next argument in the list is a pipe(|) delimited list of name=value such as
WebLogicHost, WebLogicPort, WebLogicCluster, PathTrim, PathPrepend..
6. Define any additional parameters for the Apache HTTP Server Plug-In.
The Apache HTTP Server Plug-In recognizes the parameters listed in “General
Parameters for Web Server Plug-Ins” on page -2. To modify the behavior of
your Apache HTTP Server Plug-In, define these parameters either:
l In a Location block, for parameters that apply to proxying by path, or
l In an IfModule block, for parameters that apply to proxying by MIME type.
Notes on Editing the httpd.conf File
n As an alternative to the procedure in “Editing the httpd.conf File” on page
11-11, you can define parameters in a separate file called
weblogic.conf file
that is included in the
IfModule block. Using this included file may help
modularize your configuration. For example:
<IfModule mod_weblogic.c>
# Config file for WebLogic Server that defines the parameters