On Thu, Aug 19, 2010 at 11:27:04AM +0600, Altaf Mahmud wrote:
> I finally installed it in both Ubuntu and Debian (Lenny). Instead of
> creating symbolic links, adding following lines in <Host> section of
> server.xml file has worked for me:
> 
>     <!-- DEFINE A CONTEXT PATH FOR DSpace JSP User Interface -->
>     <Context path="/jspui" docBase="/home/dspace/webapps/
> jspui" debug="0" reloadable="true" cachingAllowed="false"
> allowLinking="true"/>
>     <!-- DEFINE A CONTEXT PATH FOR DSpace XML User Interface -->
>     <Context path="/xmlui" docBase="/home/dspace/webapps/xmlui" debug="0"
> reloadable="true" cachingAllowed="false" allowLinking="true"/>

Placing Context elements in server.xml will work.  However, if you
ever ask for help on the Tomcat users list and mention that you are
doing this, the first thing everybody will say is "stop doing that".

Instead you can place the Context element by itself in a Context
fragment file in $CATALINA_BASE/config/Catalina/HOSTNAME/PATH.xml
(where HOSTNAME is the name of the surrounding Host element --
probably 'localhost' -- and PATH is what was in the Context's 'path'
(minus any leading slash, and with interior slashes replaced by '#').
For example, the fragment file for the jspui context above would be
named 'jspui.xml'.

Do not include the 'path' attribute in a Context fragment file; the
name of the file supplies the path.  To express the root context, name
the file 'ROOT.xml'.

When supplying contexts this way, you don't have to worry about
damaging other parts of server.xml inadvertently and you don't have to
restart Tomcat every time you update a Context.  In fact a convenient
way to restart such a webapp is to simply change the last-write date
on the Context fragment -- suitably configured, Tomcat will notice
this in a few seconds and reload that app.

The docBase of any Context fragment file needs to be outside of any
Host's appBase.  Otherwise Tomcat will feel free to delete your
fragment under circumstances which I haven't fully worked out.  Tomcat
creates Context fragments itself, for webapps within the appBase, and
destroys them from time to time.

> The http://localhost:8080/jspui is now looking good, I should think about it
> before since this method worked well in Windows :) Now, I guess those
> symbolic links may have to be created in somewhere else instead of
> /usr/share/tomcat6/webapps, since index.html file is in ROOT folder. The
> manual needs some changes regarding this about where to find the exact
> location for symbolic links.

I would recommend using the Context's docBase attribute rather than
symlinking, as Tomcat is very wary of symlinks and has to be coaxed to
follow them.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Balance your desire for bells and whistles with the reality that only a 
little more than 2 percent of world population has broadband.
        -- Ledford and Tyler, _Google Analytics 2.0_

Attachment: pgpJ5884RF85c.pgp
Description: PGP signature

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to