SH Solutions wrote:
Hi
Now I am stuck with configuration.
The online documentation really isnt useful. Sorry. This differs from
tomcat. Anyway, I stored a lot of bookmarks in the last weeks about JK2 from
this list.
Oh, and I forgot, there is also a mod_jk2 Apache directive "JkUri" and "JkUriSet", which should not be needed with this setup. The way I see it, there are two redundant ways to state which URI will be handled by a particular JK2 worker: workers2.properties:uri:... and httpd.conf:JkUri...
What is preferable? I don't know. It would be nice to keep all VHost directives in one place, so from that point of view, you would setup channels and workers in workers2.porperties and setup URI mappings in httpd.conf (or in separate VHost config file fragments, like most new RPMs do).
On the other hand, you might want to keep all JK2 directives in one place, which would lead you to place even URI mappings in workers2.properties, like in my example.
In any case, it looks like a tie to me. "workers2.properties" must hold workers and channels. "httpd.conf" is the one aware of VHosts and full paths. JK2 is a bridge between those domains. URI mappings can easily be placed in both places and they wouldn't stick out.
And don't forget, if you're playing with VHosts, Tomcat must also be setup for them. See "<Host ...>" element of "server.xml".
Nix.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
