Installing QM as a ROOT webapp
QueueMetrics is usually deployed as a webapp whose path stems from the root of the webserver - for example, as http://queuemetrics.example.com:8080/queuemetrics
It is possible to deploy Queuemetrics as a ROOT webapp, so that the complete address ends up being simply http://queuemetrics.example.com
Model 1: using a ROOT webapp
Changes to Tomcat
Copy the current version of QueueMetrics to a webapp named 'ROOT' (all capital letters).
cd /usr/local/queuemetrics/tomcat/webapps cp -R /usr/local/queuemetrics/webapps/queuemetrics-1.6.0/ ROOT
Restart QueueMetrics
Set the access port
If you want QueueMetrics to be available on a port that is different from the default one (8080), edit the 'server.xml' file and look for a line that looks like:
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> <Connector port="8080" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000"
and change that to:
<Connector port="80" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000"
CAUTION: Make sure you have no Apache running on port 80; in case, turn it off.
Restart QueueMetrics.
Model 2: defining a root context
It is also possible to define a specific webapp as the root webapp for a virtual host by setting it as a root context. This can be achieved quite easily by editing the ''server.xml'' file in Tomcat:
<Host name="example.com" debug="0" appBase="/www/example.com/www" unpackWARs="true"> <Alias>www.example.com</Alias> <Logger className="org.apache.catalina.logger.FileLogger" directory="/var/log/httpd" prefix="queuemetrics-" suffix=".log" timestamp="false"/> <Context path="" docBase="queuemetrics" debug="0" reloadable="true"/> </Host>
This example assumes that your QueueMetrics is installed in ''/www/example.com/www/queuemetrics'' and that you want to server QM as a root webapp for domains ''example.com'' and ''www.example.com''.