Apache Plugin in linux for WLS6.0 sp1 and (?sp2?)

Question

This message is a little long,
The following message is arranged in 4 parts where:
1. Conclusion and Sugestions.
2. Tests Environment
3. Simple plugin environment
4. Virtual Hosting with apache
Any comment and help will be welcome
Conclusion
The plug-in has not been tested and documented and therefore does not
work in the described environment. The plugin parameter needs to be :
1. Syntaxly rewieved. The parameters not starting with
WebLogic.... (like PathTrim, PathPrepend, ConnectTimeoutSecs,
ConnectRetrySecs, Debug, DebugConfigInfo, StatPath, ErrorPage,
HungServerRecoverSecs, Idempotent, CookieName,
DefaultFileName, MaxPostSize, MatchExpression, FileCaching,
SecureProxy, TrustedCAFile, RequireSSLHostMatch,
SSLHostMatchOID) are confusing and couyld be bug/problem
generators when adding other non BEA modules in apache. I
would suggest to have all the parameter starting with a common
root like WebLogic or Wls or something else deterministic
2. Better documented. The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Test Environment
The tests described below has been done with the following system
environment.
Operating System:
RedHat 7.0 + glibc updates + network uodates, kernel level 2.2.17-14
RedHat 7.1 + updates, kernel 2.4.2-2
Java Level:
On the RedHat 7.0 system the default Java JVM provided in the BEA
distribution
On the RedHat 7.1 system the Sun JDK 1.3.1 for Linux
Apache: 1.3.19
DNS: one system called cordoba.paris.inetpc.com with 3 cnames added
(w1cordoba, w2cordoba, w3cordoba)
The Weblogic installtion is coming from a single reference system.
This system runs under RedHat 6.2 + latest update levels. The WebLogic
tree directory has been deployed in both systems and the JVM set in the
proper manner. Despite the well known problem with the default webapp
Wls 6.0 works fine and as expected. Default ports are used (7001).
The apache environment works fine too. In a single apache environment
and with the virtual hosting supporting the 3 cnames (w1cordoba,
w2cordoba, w3cordoba)
In both systems the behavior and and problems are equal.
Simple plugin environment
A single default web app runs under wls6.0. calling the wls60 thru the
URI: "http://cordoba:7001" works fines and the Welcome.html default page
is properly displayed. Similar tests have been done with a jsp page and
works fine too.
The httpd.conf file has been set has described in the documentation and
as follow:
LoadModule weblogic_module modules/mod_wl.so
WebLogicHost cordoba
WebLogicPort 7001
Debug ON
DebugConfigInfo ON
<location /wls>
SetHandler weblogic-handler
PathTrin /wls
</location>
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:
Sun Jun 3 16:34:19 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:34:19 2001 The request string is '/wls'
Sun Jun 3 16:34:19 2001 INFO: SSL is not configured
Sun Jun 3 16:34:19 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:34:19 2001 INFO: New NON-SSL URL
Sun Jun 3 16:34:19 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:34:19 2001 Connected to cordoba:7001
Sun Jun 3 16:34:19 2001 INFO: sysSend 343
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 parsed all headers OK
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 r->status=302 returning 0
Sun Jun 3 16:36:08 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:36:08 2001 The request string is '/wls'
Sun Jun 3 16:36:08 2001 INFO: SSL is not configured
Sun Jun 3 16:36:08 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:36:08 2001 INFO: New NON-SSL URL
Sun Jun 3 16:36:08 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:36:08 2001 Connected to cordoba:7001
Sun Jun 3 16:36:08 2001 INFO: sysSend 343
Sun Jun 3 16:36:08 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:36:08 2001 parsed all headers OK
Sun Jun 3 16:36:08 2001 r->status=302 returning 0
Virtual Hosting with Apache
These tests aim to validate a production environment where an entry cell
of apache servers will serve static pages and route dynamic requests to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute by
location or a full reroute has done the same results than stated in
"Simple plugin environment".
[att1.html]

Answer 1

Hi
I am trying to configure the following pattern:
->https->apache->SSL->weblogic
using the apache plugin that you provided from the distribution.
There is no way to let it work.
the apache site trying to connect to weblogic is a virtual host, follows the config
file.
Checking the DEbugDebug config monitor it I discover that SecureProxy it is OFF
istead of ON and checking the debug file I've got this message:
INFO: ssl is not activated..
It means that despite of SecureProxy set to ON, it is still working in clear.
I have the same behaviour using 6.0, SP1, SP2 and 6.1
(If there more documentation about it in 6.1, please let me know where!)
Please, anyone can send me documentation about it or help me???
# <-- Start XXXXX Virtual Host
<VirtualHost XXXXXX>
SSLEngine on
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateKeyFile XXXX
SSLCertificateFile XXXXX
<Location />
AddHandler weblogic-handler .jsp
</Location>
<IfModule mod_weblogic.c>
SecureProxy ON
RequireSSLHostMatch false
TrustedCAFile /ssl/certs/ca.pem
Debug ALL
DebugConfigInfo ON
WebLogicHost XXXXX
WebLogicPort XXXXX
ErrorPage /pm/private/frame_044_error_500.htm
MatchExpression *.jsp
</IfModule>
</VirtualHost>
# <-- End XXXXX Virtual Host
"Jong Lee" <[email protected]> wrote:
>
1. Syntaxly rewieved.
Worth considering for the next major release.
2. Better documented.
Yes, 6.1 release is doing a much better job of documentation!
The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. If apxs is used to update the module, end user should not need
to worry about adding/changing these two lines.
But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin
is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Again, better on 6.1 docs.
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
"DefaultFileName Welcome.html" should be used in your httpd.conf
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:on 6.1, if relative URI is used in sendRedirect(), PathTrim and
PathPrepend should be taken care automatically. i.e:
in httpd.conf:
PathTrim /weblogic
PathPrepend /abc
in a jsp page:
response.sendRedirect("HelloWorld.jsp");
The plugin and wls will be smart enough to set Location header
to the following:
Location: http://apache_host:apache_port/weblogic/HelloWorld.jsp
Then the plugin will trim the /weblogic and prepend /abc to it
i.e:
http://wls_host:wls_port/abc/HelloWorld.jsp
Virtual Hosting with Apache
These tests aim to validate a production environment where an entrycell
of apache servers will serve static pages and route dynamic requests
to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute
by
location or a full reroute has done the same results than stated in
"Simple plugin environment".Absolutely. in 6.1 you can specify different weblogic hosts per
vhost. Even you can use MatchExresspion or <Location> to define
different parameters per mime type and path:
i.e:
MatchExpression *.jsp WebLogicHost=www.bea.com|WebLogicPort=7001|DefaultFileName=/Welcome.html
MatchExpression *.html WebLogicCluster=weblogic1:7001,weblogic2:7002|Debug=ALL
<Location /weblogic>
WebLogicHost thankyou.com
</Location>
Where Location takes the precedence.
Anyway, 6.1 apache plugin should be a much better modules.
We also support apache2.0(beta) in 6.1. Unfortunately,
the apache2.0 binaries were unable to be included in the 6.1
beta installer. There might be a separate down-load for that.
Thank you for your great suggestions/comments.
thanks
Jong