|
|
Subject: Re: "mounting" helma app behind apache - msg#00007
Hello Walter,
VividVisions, Walter Krivanek schrieb:
> I think you'll have to set "baseUri" in app.properties.
> http://helma.org/docs/guide/properties/listall#baseURI
Thanks, links are fixed now but there are still issues:
Config is now:
> > <VirtualHost helma.test.home:80>
> > ServerName helma.test.home
> > ...
> >
> > <Location /helma>
> > ProxyPass http://localhost:8080/ #thats jetty's http listener
> > </Location>
reference installation accesses helma directly over
http://localhost:8080, the only difference wrt server.properties is
"baseURI = /helma" for the "behind apache" version.
Problems with "behind apache" and baseURI = /helma:
- links for static content are incorrect, e.g. /static/helmaheader.png
is not found.
- accessing /manage over http://helma.test.home/manage doesn't work, I'm
just getting the welcome-page no matter what URL the browser asks for.
Haven't tested other apps for now.
So either there are still some knobs and levers I haven't touched (to
many over here ;)) or this setup simply doesn't work and you need one
<VirtualHost> for each helma instance, thats basically what I need to know.
We had some stability issues with mod_jk in the past, but I'm certainly
willing to try it again if it solves the "need one vhost per helma
instance" problem. On a sidenode, mod_jk doesn't seem to be available
for apache-2.2 (used here) and my tests with mod_proxy_ajp and
helma-1.5.2 showed some protocol incompatibilities wrt AJP13, so this is
a no-go ATM...
thanks
Paul
Thread at a glance:
Previous Message by Date:
Re: "mounting" helma app behind apache
Hi Paul,
A pretty much only use the mod_jk connector to put helma behind apache
and it seems to work very well.
Its probably a bit more complicated then the method your using but
theres a very good howto on this at:
http://helma.org/docs/howtos/mod_jk/
If you are using linux, you might find that your distro already has
mod_jk prepackaged (I'm on RHES/FC 4 and they have it as an rpm).
Though its not too difficult to compile it yourself (I've done that
before on an older server).
Also I think the instructions in the link above are for apache 1.3 and I
use apache 2, so if you do too, you dont need the 'AddModule mod_jk.c'
line in the httpd.conf but you do need to have config parameters
surronded in an IfModule tag like so:
<IfModule mod_jk.c>
# Configure mod_jk
JkWorkersFile /usr/local/helma-1.5.x/workers.properties
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel error
# mount on default host
JkMount /forms/* helma
</IfModule>
Hope that helps,
Maks.
________________________________
From: helma-user-bounces@xxxxxxxxx [mailto:helma-user-bounces@xxxxxxxxx]
On Behalf Of paul
Sent: Friday, 10 November 2006 9:27 AM
To: helma-user@xxxxxxxxx
Subject: [Helma-user] "mounting" helma app behind apache
Hi all,
I hope this is not an RTFM....
What I'd like to do is to "mount" multiple helma applications somewhere
in the PATH of my domain:
<VirtualHost foo.test.home:80>
ServerName foo.test.home
...
<Location />
ProxyPass http://localhost:8080/ #thats jetty's http listener
</Location>
this *seems* to work OK though I'm not entirely sure 'cause I was unable
to access the "manage" app. However:
<Location /helma>
ProxyPass http://localhost:8080/
</Location>
lets me access helma from http://foo.test.home/helma but css breaks and
links don't work... I tried to set in apps.properties:
manage.mountpoint = /helma/manage
...
welcome.mountpoint = /helma
which results in:
HTTP ERROR: 404 %2F%2F+Not+Found
RequestURI=//
Powered by Jetty://
Question is basically how to make this work. I'm not bound to mod_proxy
in any way so any method is fine. I just feel I'm still missing the big
picture how this is supposed to work. Any advice, pointers to
docs/howtos are much appreciated.
thanks
Paul
_______________________________________________
Helma-user mailing list
Helma-user@xxxxxxxxx
http://helma.org/mailman/listinfo/helma-user
Next Message by Date:
Re: helma startup script on FreeBSD
Just to follow up on this, in case others having the same problem getting helma to automatically starting up on freebsd. I recently has the "privileg" of visiting where the actually server is located. Trust me, it was not by choice. I witness the startup process on the monitor, and I notice that when the startup scripts hit the helma startup.sh, it complained "java not found", everything all the sudden just make sense.I just added the following line in the helma/start.sh (it is actually commented out)JAVA_HOME=/usr/localof course you should set it to the proper location where java is installed.And now it works. Below is my simple script for helma auto startup on freebsd 6.1. /usr/local/etc/rc.d/helma.sh#!/bin/sh##echo "Starting Helma"daemon '/helma/start.sh'exit 0On Oct 18, 2006, at 6:35 AM, Chris Zumbrunn wrote:On Oct 18, 2006, at 12:22 , Julian Tree wrote:daemon su -m userName -c '/helma/start.sh'hmm, I tried that. Some how it doesn't seem to work. If i call it on the command line, then it works, but not when I put it in the /etc/rc.confI'm doing this in jails and I have one jail where I couldn't get it to work either. It just didn't do anything and failed quietly. I have no idea why. ChrisOn Oct 18, 2006, at 5:43 AM, Chris Zumbrunn wrote:On Oct 18, 2006, at 11:31 , Julian Tree wrote: Is anyone using Helma on FreeBSD? Anyone has a start up script on FreeBSD to share? I modified one of the linux start up script on the mailing list, but it is not working on freebsd. I have to manually restart helma everything system reboots. I just have entries like below in my /etc/rc.conf file and don't go through a startup script:daemon su -m userName -c '/path/to/helma/start.sh'Chris_______________________________________________Helma-user mailing listHelma-user@xxxxxxxxxhttp://helma.org/mailman/listinfo/helma-user Julian Tree _______________________________________________Helma-user mailing listHelma-user@xxxxxxxxxhttp://helma.org/mailman/listinfo/helma-user _______________________________________________Helma-user mailing listHelma-user@xxxxxxxxxhttp://helma.org/mailman/listinfo/helma-user Julian Tree _______________________________________________
Helma-user mailing list
Helma-user@xxxxxxxxx
http://helma.org/mailman/listinfo/helma-user
Previous Message by Thread:
Re: "mounting" helma app behind apache
Hi,
I think you'll have to set "baseUri" in app.properties.
http://helma.org/docs/guide/properties/listall#baseURI
Another Apache HowTo:
http://helma.org/docs/howtos/mod_jk/
Best,
Walter
Am 9. Nov 2006 um 23:26 schrieb paul:
> Hi all,
>
> I hope this is not an RTFM....
> What I'd like to do is to "mount" multiple helma applications
> somewhere
> in the PATH of my domain:
>
> <VirtualHost foo.test.home:80>
> ServerName foo.test.home
> ...
>
> <Location />
> ProxyPass http://localhost:8080/ #thats jetty's http listener
> </Location>
>
> this *seems* to work OK though I'm not entirely sure 'cause I was
> unable
> to access the "manage" app. However:
>
> <Location /helma>
> ProxyPass http://localhost:8080/
> </Location>
>
> lets me access helma from http://foo.test.home/helma but css breaks
> and
> links don't work... I tried to set in apps.properties:
>
> manage.mountpoint = /helma/manage
> ...
> welcome.mountpoint = /helma
>
> which results in:
> HTTP ERROR: 404 %2F%2F+Not+Found
> RequestURI=//
> Powered by Jetty://
>
>
> Question is basically how to make this work. I'm not bound to
> mod_proxy
> in any way so any method is fine. I just feel I'm still missing the
> big
> picture how this is supposed to work. Any advice, pointers to
> docs/howtos are much appreciated.
>
> thanks
> Paul
>
> _______________________________________________
> Helma-user mailing list
> Helma-user@xxxxxxxxx
> http://helma.org/mailman/listinfo/helma-user
>
Next Message by Thread:
Re: "mounting" helma app behind apache
Hi Paul,
A pretty much only use the mod_jk connector to put helma behind apache
and it seems to work very well.
Its probably a bit more complicated then the method your using but
theres a very good howto on this at:
http://helma.org/docs/howtos/mod_jk/
If you are using linux, you might find that your distro already has
mod_jk prepackaged (I'm on RHES/FC 4 and they have it as an rpm).
Though its not too difficult to compile it yourself (I've done that
before on an older server).
Also I think the instructions in the link above are for apache 1.3 and I
use apache 2, so if you do too, you dont need the 'AddModule mod_jk.c'
line in the httpd.conf but you do need to have config parameters
surronded in an IfModule tag like so:
<IfModule mod_jk.c>
# Configure mod_jk
JkWorkersFile /usr/local/helma-1.5.x/workers.properties
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel error
# mount on default host
JkMount /forms/* helma
</IfModule>
Hope that helps,
Maks.
________________________________
From: helma-user-bounces@xxxxxxxxx [mailto:helma-user-bounces@xxxxxxxxx]
On Behalf Of paul
Sent: Friday, 10 November 2006 9:27 AM
To: helma-user@xxxxxxxxx
Subject: [Helma-user] "mounting" helma app behind apache
Hi all,
I hope this is not an RTFM....
What I'd like to do is to "mount" multiple helma applications somewhere
in the PATH of my domain:
<VirtualHost foo.test.home:80>
ServerName foo.test.home
...
<Location />
ProxyPass http://localhost:8080/ #thats jetty's http listener
</Location>
this *seems* to work OK though I'm not entirely sure 'cause I was unable
to access the "manage" app. However:
<Location /helma>
ProxyPass http://localhost:8080/
</Location>
lets me access helma from http://foo.test.home/helma but css breaks and
links don't work... I tried to set in apps.properties:
manage.mountpoint = /helma/manage
...
welcome.mountpoint = /helma
which results in:
HTTP ERROR: 404 %2F%2F+Not+Found
RequestURI=//
Powered by Jetty://
Question is basically how to make this work. I'm not bound to mod_proxy
in any way so any method is fine. I just feel I'm still missing the big
picture how this is supposed to work. Any advice, pointers to
docs/howtos are much appreciated.
thanks
Paul
_______________________________________________
Helma-user mailing list
Helma-user@xxxxxxxxx
http://helma.org/mailman/listinfo/helma-user
|
|