> [...]
> <VirtualHost IPNUMBER>
> ServerName www.user.DOMAIN
> DocumentRoot /home/USER/www/htdocs
> <IfModule mod_jserv.c>
> ApJServDefaultPort PORT
> ApJServMount /servlets ajpv11://localhost:PORT/USER
> ApJServProperties /home/USER/www/conf/jserv.properties
^^^^^^^^^^^^^^^^^
Is the above correct? I've tried specifying separate
ApJServProperties for different virtual hosts and httpd
failed to start complaining that this directive cannot be
used within VirtualHost.
> </IfModule>
> <Location /servlets/*>
> allow from all
> </Location>
> </VirtualHost>
> [...]
--
Pawel Pesz
InsERT.net, Wroclaw, Poland
mailto:[EMAIL PROTECTED]
http://www.insert.net.pl
>
>where IPNUMBER is replaced with the hosting machine's IP number and DOMAIN
>is replaced with your domain name, e.g., ornl.gov for the original poster.
>Then USER is replaced with the user name and PORT is replaced with the port
>which JServ will used, e.g., 8008, 8009, etc., where each user is assigned
>a unique port number.
>
>In each user's /home/USER/www/conf/jserv.properties the port property would
>be set to the corresponding port for that user. Something like
>
>port=USER
>...
>zones=USER
>USER.properties=/home/USER/www/conf/jserv.USER.properties
>
>Now, the only remaining thing to do is add a script that launches the JVM
>for each user. The simplest is to let each user startup their own jserv by
>placing a jserv startup script in (say) /usr/local/bin/jserv, for instance:
>
>#!/bin/bash
>properties=$HOME/www/conf/jserv.properties
>log=$HOME/www/log/jserv.log
>CLASSPATH=$CLASSPATH:/usr/local/jserv/lib/Apache-JServ.jar
>CLASSPATH=$CLASSPATH:/usr/local/java/jsdk/lib/jsdk.jar
>CLASSPATH=$CLASSPATH:...additional shared classes...
>java org.apache.jserv.JServ $properties 2>> $log
>
>Yet another approach is to have completely separate web servers running for
>each user on a non-privileged port. This is probably the ideal solution
>because:
>
>1. You have, in one single step, decentralized the administration.
>
>2. You don't have to figure out how to run jserv in manual mode for each
>user and all the mess described above.
>
>Point (1) is the most useful because when a developer has changed something
>and JServ/Apache are not behaving he can just do "apachectl restart" and
>doesn't have to restart everyone's server or bug the sysadmin. Actually,
>this is how I test things before integrating them into my runtime system.
>Basically, you just build apache with a --prefix for $HOME/user/apache
>instead of the default /usr/local/apache, then you change the PORT from 80
>to the user's assigned port, e.g., 4000 or 8000, or 1345, or whatever above
>1023. Then you just follow the regular config instructions for JServ/Apache
>except you store all the files under the user's home directory and remember
>to use a unique port number for each user's Apache/JServ communication.
>
>-- Ari Halberstadt mailto:[EMAIL PROTECTED] <http://www.magiccookie.com/>
>PGP public key available at <http://www.magiccookie.com/pgpkey.txt>
>
>
>
>
>----------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://www.working-dogs.com/>
>Problems?: [EMAIL PROTECTED]
>
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
