5. 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

5.1. Prerequisites

  • A working QueueMetrics instance

5.2. 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

5.2.1. 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.

5.3. Changes to QueueMetrics

None required.