Hello,
I've been working with James on this one.
OK so we have this working beautifully now! We threw up the docs on
the Wiki:
http://www.magnolia.info/wiki/Wiki.jsp?page=TomcatVirtualHosts
It works both with Apache and without. Couldn't get JkMount /
magnolia* to work to serve both tomcat and apache, but that is ok.
Since we updated the old Apache 1.3.x docs, we also linked that to
the Magnolia 2.1 page (and changed the text to show the diff between
Tomcat + Apache 1.3 and Tomcat + Apache 2.0).
Hope this helps.
//c
--
Chems Touati
Macintosh Specialist
Student Computing Labs, Marriott Library
University of Utah
801.585.9811
[EMAIL PROTECTED]
On Apr 27, 2006, at 12:15 AM, David Smith wrote:
Questions answered:
- What is a worker? A defined connection between one tomcat server
and one apache server. Essentially tells apache on what ip and
port it can find a tomcat service that speaks the AJP-13 protocol.
I know what the Tomcat docs call it, and I think that means I only
need one unless I have Magnolia running on 2 different servers and
I want to make them accessible on the same server.
Correct.
- What should the name of a worker be?
Anything you want as long as it's alphanumeric. Try to avoid
punctuation in a worker's name. I'm sure there are some
punctuation marks allowed, but can't remember which ones exactly.
- Is there anyway to remove the context from the path using mod_jk
and virtual hosts? For example, can I change....:
Rewriting the path is overall a problematic task -- your better off
avoiding it. I would define two hosts in tomcat, each with it's
own webapps directory. Then rename your magnoliaPublic and
magnoliaAuthor webapps both to ROOT, storing one in one of the
webapps directories and the other in the other webapps directory.
Unfortunately you'll need two workers -- one for each host when
configured in this manner.
On the other hand as long as you aren't in need of the modules
apache offers (php, perl, etc.,...), you could simply dump apache
in favor of direct access to tomcat. Tomcat 5.5.x is nearly as
fast as apache httpd and the mod-jk middleman will only slow things
down.
--David
James Reynolds wrote:
I have spent the last few days (days!!) trying to get Apache and
mod_jk to work with Tomcat. I've finally gotten it to work, but
it doesn't do what I want. I've updated the wiki page with
everything I know (and some things I don't).
http://www.magnolia.info/wiki/Wiki.jsp?page=RunningMagnoliaWithApache
My questions are:
- What is a worker? I know what the Tomcat docs call it, and I
think that means I only need one unless I have Magnolia running on
2 different servers and I want to make them accessible on the same
server.
- What should the name of a worker be?
- Is there anyway to remove the context from the path using mod_jk
and virtual hosts? For example, can I change:
www.example.com/magnoliaPublic
www.example.com/magnoliaAuthor
to
www.example.com (public)
author.example.com (author)
That is what I really want and what I've done so far isn't getting
me that.
--
Thanks,
James Reynolds - University of Utah - Student Computing Labs -
801-585-9811
james(a)scl.utah.edu - james(a)magnusviri.com - http://
james.magnusviri.com
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
