Consider the following excerpt from mod_wl_ohs.conf:
<IfModule weblogic_module>
WebLogicCluster 192.168.13.1:7001, 192.168.13.2:7001,192.168.13.2:7001
</IfModule>
<Location /welcome>
SetHandler weblogic-handler
</Location>
Assuming that this is a valid is a valid configuration, which two conclusions can you make?
A.
A web application name “welcome” is configured to use session replication.
B.
A web application that uses the paths “welcome” is targeted to the cluster.
C.
The proxy server will ignore any requests that contain the name “welcome.”
D.
The proxy server is listening on the host name “welcome.”
E.
A cluster exists that consists of at least two managed servers.
F.
All cluster members are running on the same machine.
Explanation:
B: To proxy requests by path, use the Location block and the SetHandler statement.
When to use <Location>
Use <Location> to apply directives to content that lives outside the filesystem. For content that
lives in the filesystem, use <Directory> and <Files>. An exception is <Location />, which is an easy
way to apply a configuration to the entire server.
For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No
scheme, hostname, port, or query string may be included. For proxy requests, the URL to be
matched is of the form scheme://servername/path, and you must include the prefix.
E: Add an IfModule block that defines one of the following:
For a non-clustered WebLogic Server instance:
The WebLogicHost and WebLogicPort parameters.
For a cluster of WebLogic Servers instances:
The WebLogicCluster parameter.
If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the
WebLogicCluster parameter.
For example:
<IfModule mod_weblogic.c> WebLogicCluster
w1s1.com:7001,w1s2.com:7001,w1s3.com:7001</IfModule>
Note #1: The <IfModule test>…</IfModule> section is used to mark directives that are conditional
on the presence of a specific module. The directives within an <IfModule> section are only
processed if the test is true. If test is false, everything between the start and end markers is
ignored.
The test in the <IfModule> section directive can be one of two forms:
module name!module name
Note #2:
<Location> Directive
Description:Applies the enclosed directives only to matching URLs
Syntax:<Location URL-path|URL> … </Location>
Context:server config, virtual host
Status:Core
Module:core
The <Location> directive limits the scope of the enclosed directives by URL. It is similar to the
<Directory> directive, and starts a subsection which is terminated with a </Location> directive.
<Location> sections are processed in the order they appear in the configuration file, after the
<Directory> sections and .htaccess files are read, and after the <Files> sections.
<Location> sections operate completely outside the filesystem. This has several consequences.
Most importantly, <Location> directives should not be used to control access to filesystem
locations. Since several different URLs may map to the same filesystem location, such access
controls may by circumvented.
Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Using Web Server PlugIns with WebLogic Server > Installing and Configuring the Apache HTTP Server Plug-In
B,E