Technical data

10 Proxying Requests to a WebLogic Cluster
10-4 Administration Guide
4. In the Administration Console, assign the servlet as the default Web Application
for the Managed Server on your proxy server machine. For instructions, see
“Designating a Default Web Application” on page 8-6.
5. In the Administration Console, deploy the servlet to the Managed Server on your
proxy server machine. For instructions, see “Deploying Web Application
Components” on page 7-3.
Sample Deployment Descriptors
The subsections that follow contain sample deployments descriptor files (web.xml)
for use with the new and deprecated versions of
HttpClusterServlet.
Each sample
web.xml defines a set of parameters that specify the location and
behavior of the HTTP Cluster Servlet.
In both versions of the servlet:
n The DOCTYPE stanza specifies the DTD used by WebLogic Server to validate
web.xml.
n The servlet stanza:
l Specifies the location of the proxy plug-in servlet class. The file is located in
the
weblogic.jar in your WL_HOME/server/lib directory. You do not
have to specify the servlet’s full directory path in
web.xml because
weblogic.jar is put in your CLASSPATH when you start WebLogic
Server.
l Identifies the host name and list port of each Managed Servers in the cluster,
using the
WebLogicCluster parameter in the SP02 and later version, and
the
defaultServers parameter for deprecated version.
n The three servlet-mapping stanzas specify that the servlet will proxy URLs
that end in '/', 'htm', 'html', or 'jsp' to the cluster.