problem of using websphere application server and websphere edge-server together
wil
I have a websphere application server running on the machine
192.168.12.150. When I use a browser to access the URL
http://192.168.12.150/webmail/webmail.jsp, it's working properly and shows
up the jsp page. Now I have another edge server running on a machine
192.168.12.157 as a reverse proxy for 192.168.12.150, and have a proxy
mapping
Proxy /webmail/* http://192.168.12.150/webmail/*
Then when I use the browser to access
http://192.168.12.157/webmail/webmail.jsp, I received a Not Found error
generated by IBM HTTP Server. I checked the log file of the HTTP Server
(running on 150) and find this line in the error log :
[Web Aug 8 17:14:38 2001] [error] [client 192.168.12.157] File does not
exist: /opt/IBMHTTPServer/htdocs/en_US/webmail/webmail.jsp
So actually the HTTP server can receive the request from the edge server
(i.e. the mapping of the edge server is correct) but for whatever reasons,
the HTTP server does not pass this request to the application server for
further processing. Instead it try to locate the file from it's document
root. This seems very strange to me as when I access
http://192.168.12.150/webmail/webmail.jsp, the request can be forwarded to
the App. server.
In the edge server's configuration file, previously I've set
SendRevProxyName to "yes". After some trials, I found that if I set this
directive to "no", seems that the reverse proxy is working properly. While
this seems to solve the problem, I am not quite sure what exactly I am
doing, and am not feeling comfortable with it. Can anyone help explaining
more details about what this SendRevProxyName means? Am I doing the right
thing?
Actually the setting SendRevProxyName=yes was suggested by an expert, and I
believe he has good reasons to do so in reverse proxy. The setting is
running well in my development environment where both application server and
edge server are run on the same PC (bind to different port). But in the
production environment, I have the problem described above!
I appreciate any kind help from you! Thanks a lot!
regards, wil.
Ken Hygh
Go into your virtual host and add 192.168.12.157 to the alias list
Ken