Databases Reference
In-Depth Information
Before, the test request was handled by the Apache:
[webadmin@web01]$ curl http://web01
<html><body><h1>It works!</h1></body></html>
Now the request is proxied to WebLogic. The following result is displayed when the Server
instances of the cluster are down:
[webadmin@web01]$ curl http://web01
<HTML><HEAD><TITLE>Weblogic Bridge Message</TITLE></HEAD>
<BODY><H2>Failure of server APACHE bridge:</H2><P><hr>No backend server
available for connection: timed out after 10 seconds or idempotent set to
OFF or method not idempotent.<hr> </BODY></HTML>
After starting the WebLogic Managed Servers of the cluster, the same request now returns a
HTTP 404 - NOT FOUND code, because no applications are deployed in the cluster yet:
[webadmin@web01]$ curl http://web01
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 404--Not Found</TITLE>
</HEAD>
_ code snipped _
There's more...
A single Web Tier with the WebLogic plug-in can be used to balance the requests to other
WebLogic domains and clusters.
Proxying requests to other WebLogic clusters
It's possible to segregate the incoming HTTP requests with a specific context path to a
different WebLogic cluster using the same Apache configuration.
The following is an example of the configuration in
httpd-weblogic.conf
:
LoadModule weblogic_module lib/mod_wl.so
<IfModule mod_weblogic.c>
Debug ALL
WLLogFile /tmp/wl-proxy.log
</IfModule>
<Location /app01>
SetHandler weblogic-handler
Search WWH ::
Custom Search