http://ofbiz.116.s1.nabble.com/OFBiz-Users-Weird-multi-instance-configuration-tp135811p135817.html
I think I'll dump mod_jk - this way seems more flexible.
>Rupert,
>
>Just for a little more background - I'll concentrate on
>mod_proxy/mod_rewrite as there seems to be plenty info on mod_jk out
>there - this will hopefully help you on your way...
>
>mod_proxy turns your apache server into a proxy server, allowing you to
>pass requests through to the local/remote application server.
>mod_rewrite allows you to transform the URL coming in to address the
>appropriate appserver.
>
>E.g. you may want all requests coming in for
http://www.mydomain.com to
>go to
http://localhost:8080/mydomain - mod_rewrite transforms the URL
>and mod_proxy passes the request.
>
>So you might end up with httpd.conf entries like this (where x.x.x.x is
>mydomain.com's ip)...
>
>-----------------------
><VirtualHost x.x.x.x>
> ServerAlias www.mydomain.com mydomain.com
> RewriteEngine on
> RewriteRule ^/(.*)$
http://localhost:8080/mydomain/$1 [P,L]
> RewriteRule ^/myimages(.*)$
>
http://localhost:8080/an_image_folder/$1 [P,L]
> ProxyPassReverse /
http://localhost:5000/mydomain/></VirtualHost>
>-----------------------
>
>Note the entry for myimages, this is where this combination comes into
>it's own - here you have mapped requests coming in to myimages through
>to a completely different directory (it could be a different server if
>you wanted)
>
>Regardless of whether you chose mod_jk or the above this is a real pain
>when you're doing it for the first time. I hope this helps you get
>everything sorted out!
>
>Kind Regards
>
>