Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm assuming that you are using <code>mod_jk</code> to connect Apache &amp; Tomcat. If so, You will have to have to <a href="http://tomcat.apache.org/tomcat-6.0-doc/virtual-hosting-howto.html" rel="nofollow noreferrer">configure virtual hosting within Tomcat as well as Apache</a> (multiple <a href="http://tomcat.apache.org/tomcat-6.0-doc/config/host.html" rel="nofollow noreferrer"><code>&lt;Host&gt;</code> declarations</a> in your conf/server.xml)</p> <p>This basically means that you'll have two <code>&lt;Host ...&gt;</code> declarations within conf/server.xml. They will have different names, and appBase, but you will still have to name the war ROOT.war</p> <p>The example that they gave was:</p> <pre><code>&lt;Engine name="Catalina" defaultHost="ren"&gt; &lt;Host name="ren" appBase="renapps"/&gt; &lt;Host name="stimpy" appBase="stimpyapps"/&gt; &lt;/Engine&gt; </code></pre> <p>After you've configured the DNS of your virtual '<code>&lt;host&gt;</code>s'(much like Apache) you'll have to put your ROOT.war(s) into separate folders {renapps,stimpyapps} instead of the default 'webapps' folder</p> <p>This method works, but there is another method using <code>mod_proxy</code> instead of <code>mod_jk</code>. I'm not that familiar with <code>mod_proxy</code> but basically you would have the connector handle translating the root context to the actual context. So after its configured it would proxy &amp; forward requests sent to <code>http://virtualhost1.example.com/</code> to the right context within Tomcat (<code>/myGrailsApplication-0.1/</code>)</p> <p>Let us know what you find! Anyone else do this with <code>mod_proxy</code>?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload