There are two things you need to do to use it as a proxy. jBoss needs to listen on a different port (I don't know how to change that) and you need to configure the HTTP server to run on port 5001 and then send request off to jBoss. For the purpose of this example, let's assume you make jBoss listen on port 5010.
This will make you configuration look like this:
LoadModule proxy_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_http_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_connect_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
LoadModule proxy_ftp_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
Listen 5001
HotBackup Off
CgiConvMode %%MIXED/MIXED%%
HostNameLookups off
UseCanonicalName On
TimeOut 30000
KeepAlive Off
DocumentRoot /www/apachedft/htdocs
AddLanguage en .en
LogFormat "%h %l %u %t \"%r\" %>s %b %D \"%{Referer}i\" \"%{User-Agent}i\"" combined
CustomLog logs/accesslog combined
ErrorLog logs/errorlog
LogMaint logs/errorlog 14 0
ProxyReverse On
ProxyPass /
http://localhost:5010/
ProxyPreserveHost On
# Deny most requests for any file
<Directory />
order allow,deny
deny from all
Options -Indexes -ExecCGI -includes
AllowOverride Limit Options
</Directory>
# Allow requests for files in document root
<Directory /www/apachedft/htdocs>
order allow,deny
allow from all
</Directory>
Besides the directives I mentioned yesterday, you'll see that I also added a LogMaint directive. This caused the error logs to be deleted once they are more than 14 days old. You can do the same thing for the access log if you want.
What I would do before changing ports is leave the port on the Listen directive at 8081 and on the ProxyPass directive at 5001. This will let you test out the proxy configuration without impacting your users. Once you've tested it, you can then make the changes to the ports.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: Thursday, March 05, 2009 10:18 AM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] log all traffic go to our web app server
Thanks Matt,
Yes the server seems to be up and running. The config file looks like
below:
Listen 8081
HotBackup Off
CgiConvMode %%MIXED/MIXED%%
HostNameLookups off
UseCanonicalName On
TimeOut 30000
KeepAlive Off
DocumentRoot /www/apachedft/htdocs
AddLanguage en .en
# Deny most requests for any file
<Directory />
order allow,deny
deny from all
Options -Indexes -ExecCGI -includes
AllowOverride Limit Options
</Directory>
# Allow requests for files in document root
<Directory /www/apachedft/htdocs>
order allow,deny
allow from all
</Directory>
Our web apps server is listening on port 5001. Can you show me how to
do proxy thing that you have mentioned?
thanks
"Haas, Matt (CL Tech Sv)" <matt.haas@xxxxxxxxxxx> wrote in message
news:<mailman.7520.1236265694.26163.web400@xxxxxxxxxxxx>...
WAS has its own plug-in so unless jBoss has something similar that works
on i (or you it works with Tomcat's plug-in), you likely don't have an
HTTP server in front of it.
Checking if you have an HTTP server running is easy. Type WRKACTJOB
SBS(QHTTPSVR) and see if anything shows up. If it is there, there may be
jobs with several different names in it. ADMIN and ADMIN2 are related to
the admin GUI that runs on port 2001. There may be an instance called
APACHEDFT running or it may be called something else. You can ignore any
jobs that start with a Q (those will usually show up around the ADMIN
and ADMIN2 jobs).
If you look at the job log for the job with function PGM-QZHBMAIN,
you'll see something like this:
CALL PGM(QHTTPSVR/QZHBMAIN) PARM('-S' 'TLCCTEST' '-uiMin' '10' '-uiMax'
'4
0' '-cEAMap' '*CCSID' '-cAEMap' '*CCSID' '-uiCCSID' '819' '-apache' '-d'
'
/www/tlcctest' '-f' 'conf/httpd.conf' '-AutoStartY')
On the last line, the first and third parameters are the path to the
HTTP server's configuration file. You have to put those pieces together
to get the full path (it would be /www/tlcctest/conf/httpd.com using the
above example. If you use EDTF, you can see the configuration file.
You can also use the admin GUI to view the configuration but I find it
much faster to look at it this way.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Lim Hock-Chai
Sent: Thursday, March 05, 2009 9:31 AM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] log all traffic go to our web app server
Thanks Matt/Nathan,
I really do not know much about web server or web programming. Our web
server is currently encountering a lot of issue with it going down. The
cause seems to cause of spike of heap memory on the server job. When
the this happen the Garbage Collect when do the Stop the world GC which
cause the server going into a long pause.
So,... I really does not even know how to check if our JBOSS is
configure to work with Apache HTTP plug in. Will dig into it. Thanks
for all the help.
"Nathan Andelin" <nandelin@xxxxxxxxx> wrote in message
news:<mailman.7454.1236211139.26163.web400@xxxxxxxxxxxx>...
From: Lim Hock-Chai
We uses JBOSS.
I'm not familiar with JBOSS, but my understanding is that WAS is
generally configured to work with an Apache HTTP plug-in, which forwards
.jsp URLs (for example) to WAS. In that case, you could query the HTTP
server logs.
Does JBOSS run stand-alone? Actually, it would surprise me if it
didn't have a built-in logging feature, too
Nathan.
midrange.com
