Author: buildbot
Date: Mon Jun 23 09:20:27 2014
New Revision: 913333
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/web-console.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/web-console.html
==============================================================================
--- websites/production/activemq/content/web-console.html (original)
+++ websites/production/activemq/content/web-console.html Mon Jun 23 09:20:27
2014
@@ -36,7 +36,6 @@
<link
href='http://activemq.apache.org/styles/highlighter/styles/shThemeEclipse.css'
rel='stylesheet' type='text/css' />
<script
src='http://activemq.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
<script
src='http://activemq.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
- <script
src='http://activemq.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
<script type="text/javascript">
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -82,47 +81,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>The ActiveMQ Web Console is a web
based administration tool for working with ActiveMQ. When used with the <a
shape="rect" href="jmx.html">JMX</a> support it can be an invaluable tool for
working with ActiveMQ</p>
-
- <div class="aui-message hint shadowed information-macro">
- <p class="title">Web console 5.3.1 problem workaround</p>
- <span class="aui-icon icon-hint">Icon</span>
- <div class="message-content">
-
-<p>If your web console doesn't start correctly in 5.3.1 release, you're
probably ran into a problem with a workaround for Camel web application. To fix
it, just change <code>ActiveMQCompnent</code> setup in
<code>webapps/camel/WEB-INF/applicationContext.xml</code> (and
<code>conf/camel.xml</code> if you use it), to something like this:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <!-- configure the camel activemq component to use the current broker
-->
- <bean id="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent" >
- <property name="connectionFactory">
- <bean
class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL"
value="vm://localhost?create=false&amp;waitForStart=10000" />
- <property name="userName"
value="${activemq.username}"/>
- <property name="password"
value="${activemq.password}"/>
-
- </bean>
- </property>
- </bean>
-]]></script>
-</div></div>
-
-<p>This will be fixed in 5.4.0 release</p>
- </div>
- </div>
-
-
-<h3 id="WebConsole-RunningtheWebConsoleonActiveMQ5.0orlater">Running the Web
Console on ActiveMQ 5.0 or later</h3>
-
-<p>We have integrated the Web Console into the binary distribution. So <a
shape="rect" href="download.html">Download</a> a binary distribution then
follow the instructions for <a shape="rect"
href="version-5-run-broker.html">Version 5 Run Broker</a>. Then you can point
your web browser at the URL</p>
-<ul><li><a shape="rect" class="external-link"
href="http://localhost:8161/admin";
rel="nofollow">http://localhost:8161/admin</a></li></ul>
-
-
-<p>And hey presto, you should now have the Web Console running.</p>
-
-<p>In the event that you are running a standalone broker and the Web Console
is not reachable, check that the following lines are included in your ActiveMQ
config xml:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<div class="wiki-content maincontent"><p>The ActiveMQ Web Console is a web
based administration tool for working with ActiveMQ. When used with the <a
shape="rect" href="jmx.html">JMX</a> support it can be an invaluable tool for
working with ActiveMQ</p><h3
id="WebConsole-RunningtheWebConsoleonActiveMQ5.0orlater">Running the Web
Console on ActiveMQ 5.0 or later</h3><p>We have integrated the Web Console into
the binary distribution. So <a shape="rect" href="download.html">Download</a> a
binary distribution then follow the instructions for <a shape="rect"
href="version-5-run-broker.html">Version 5 Run Broker</a>. Then you can point
your web browser at the URL</p><ul><li><a shape="rect" class="external-link"
href="http://localhost:8161/admin";
rel="nofollow">http://localhost:8161/admin</a></li></ul><p>And hey presto, you
should now have the Web Console running.</p><p>In the event that you are
running a standalone broker and the Web Console is not reachable, check that
the following lines
are included in your ActiveMQ config xml:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[<bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<value>file:${activemq.base}/conf/credentials.properties</value>
@@ -132,57 +91,14 @@
<!-- your broker config goes here -->
<import resource="${activemq.base}/conf/jetty.xml"
/>]]></script>
-</div></div>
-
-<p>The import will start up an embedded Jetty container. To verify that the
config is working, the following should appear in your ActiveMQ console/logs on
next startup:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>The import will start up an embedded Jetty container. To verify
that the config is working, the following should appear in your ActiveMQ
console/logs on next startup:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[INFO | jetty-7.1.6.v20100715
INFO | ActiveMQ WebConsole initialized.]]></script>
-</div></div>
-
-
-
-<p>As of 5.3 or later you should also have the <a shape="rect"
class="external-link" href="http://camel.apache.org/web-console.html";>Camel Web
Console</a> available for use to browse your endpoints and <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>
at the following URL</p>
-<ul><li><a shape="rect" class="external-link"
href="http://localhost:8161/camel";
rel="nofollow">http://localhost:8161/camel</a></li></ul>
-
-
-<h3 id="WebConsole-Changingtheport">Changing the port</h3>
-
-<p>If you want to change the port number of the web application try the
following</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn jetty:run -Djetty.port=9090
-]]></script>
-</div></div>
-<p>You can also set the port with the port attribute in the nioConnector tag
in the activemq.xml configuration file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<connectors>
- <nioConnector port="8161" />
-</connectors>
-]]></script>
-</div></div>
-
-<h3 id="WebConsole-SecuringWebConsole">Securing Web Console</h3>
-
-<p>Starting with ActiveMQ 5.4.0, Web Console comes pre-configured with basic
access authentication setup. It's turned off by default, so you need to turn it
on explicitly, but it's really simple. Go to the
<code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and find the following line</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h3 id="WebConsole-Changingtheport">Changing the port</h3><p>If
you want to change the port number of the web console, see the configuration
files in the conf directory.</p><h3 id="WebConsole-SecuringWebConsole">Securing
Web Console</h3><p>Starting with ActiveMQ 5.4.0, Web Console comes
pre-configured with basic access authentication setup. It's turned off by
default, so you need to turn it on explicitly, but it's really simple. Go to
the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and find the following
line</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[<property name="authenticate"
value="false" />]]></script>
-</div></div>
-
-<p>and change it to</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>and change it to</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[<property name="authenticate"
value="true" />]]></script>
-</div></div>
-
-<p>That's it. From that point on, web server will look at
<code>${ACTIVEMQ_HOME}/conf/jetty-realm.properties</code> file trying to match
provided credentials with those listed in the file. By default, you can access
the web console with <code>admin/admin</code> credentials. That can be changed
(and more users can be added) in the <code>jetty-realm.properties</code>
file.</p>
-
-<p>You may also wish to enable <strong>ssl connector</strong> to further
secure access to the web console and other web resources of the broker. To do
that, go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and make sure you
have the secure connector enabled. In versions 5.7 and newer just uncomment a
predefined config. In any case make sure your connectors settings looks similar
to this.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>That's it. From that point on, web server will look at
<code>${ACTIVEMQ_HOME}/conf/jetty-realm.properties</code> file trying to match
provided credentials with those listed in the file. By default, you can access
the web console with <code>admin/admin</code> credentials. That can be changed
(and more users can be added) in the <code>jetty-realm.properties</code>
file.</p><p>You may also wish to enable <strong>ssl connector</strong> to
further secure access to the web console and other web resources of the broker.
To do that, go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and make
sure you have the secure connector enabled. In versions 5.7 and newer just
uncomment a predefined config. In any case make sure your connectors settings
looks similar to this.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ <property
name="connectors">
<list>
<bean id="Connector"
class="org.eclipse.jetty.server.nio.SelectChannelConnector">
@@ -196,162 +112,7 @@ mvn jetty:run -Djetty.port=9090
</list>
</property>
]]></script>
-</div></div>
-
-<p>Standard connector is left enabled in this example, but you can remove it
in your configuration if you wish.</p>
-
-<p>Note that these changes will affect the whole web server, so if you're
using <a shape="rect" href="rest.html">REST</a> API or blob fileserver be sure
to provide appropriate credentials.</p>
-
-<p>If you're interested in securing 5.3.1 (and 5.3.2) Web consoles, take a
look at <a shape="rect" class="external-link"
href="http://www.nighttale.net/activemq/securing-activemq-531-console.html";
rel="nofollow">this article</a>. For older versions, please refer to <a
shape="rect" class="external-link"
href="http://it.toolbox.com/blogs/unix-sysadmin/securing-activemq-web-console-27727";
rel="nofollow">this article</a></p>
-
-<h3
id="WebConsole-StartingtheWebConsoleinaseperateVM/inaWeb-Container">Starting
the Web Console in a seperate VM/in a Web-Container</h3>
-
-<p>If you want to start the web-console in a different process than ActiveMQ
(f.e. for security or reliability reasons) then you've two options:</p>
-
-<h4 id="WebConsole-ConfigureusingSystem-Properties">Configure using
System-Properties</h4>
-
-<p>You need to configure the following system properties:</p>
-<ul><li>-Dwebconsole.type=properties</li><li>-Dwebconsole.jms.url=<url of
the broker> (f.e.
tcp://localhost:61616)</li><li>-Dwebconsole.jmx.url=<jmx url to the
broker> (f.e.
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi)</li><li>-Dwebconsole.jmx.user=<remote
jmx user name></li><li>-Dwebconsole.jmx.password=<remote jmx
password></li></ul>
-
-
-
-<p>These may be specified on the maven command line with mvn jetty:run
-Dwebconsole.type=properties..... or deploy the activemq-web-console.war into a
Web-Container (f.e. Jetty, Tomcat) and follow the example below.</p>
-
-<h4 id="WebConsole-ConfigureusingJNDI">Configure using JNDI</h4>
-
-<p>Deploy the activemq-web-console.war into a Web-Container (f.e. Jetty,
Tomcat) and specify the following System property</p>
-<ul><li>-Dwebconsole.type=jndi<br clear="none">
-The jndi-resources are named</li><li>java:comp/env/jms/connectionFactory:
JMS-ConnectionFactory (Type
javax.jms.ConnectionFactory)</li><li>java:comp/env/jmx/url: URL of the brokers
JMX (Type java.lang.String)</li></ul>
-
-
-<p>Don't forget to add the activemq-all jar to your webcontainer's shared lib
directory (common/lib for tomcat, lib for jetty).</p>
-
-
-<h4 id="WebConsole-Failoverconfigurations">Failover configurations</h4>
-
-<p>It's possible to configure the web-console to monitor master/slave-broker
setup. To do so use the normal failover: Syntax for the JMS-URL and a comma
separated list of JMX-URLs. This works with the System-property- and with the
JNDI-configuration.<br clear="none">
-Example:<br clear="none">
--Dwebconsole.jms.url=failover:(tcp://serverA:61616,tcp://serverB:61616)<br
clear="none">
--Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://serverA:1099/jmxrmi,service:jmx:rmi:///jndi/rmi://serverB:1099/jmxrmi</p>
-
-<h4 id="WebConsole-ExampleconfigurationusingJetty6">Example configuration
using Jetty 6</h4>
-
-<p>To start the web-console in a dedicated jetty use the following
startup-script (execute from the jetty-root-dir):</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-java -Dwebconsole.type=properties -Dwebconsole.jms.url=tcp://localhost:61616
-Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
-Dwebconsole.jmx.user=system -Dwebconsole.jmx.password=manager -jar start.jar
-]]></script>
-</div></div>
-<p>If the web-console should be password protected (BASIC Authentication) use
the standard jetty mechanisms:<br clear="none">
-1. Define a UserRealm in jetty.xml:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<Set name="UserRealms">
- <Array type="org.mortbay.jetty.security.UserRealm">
- <Item>
- <New
class="org.mortbay.jetty.security.HashUserRealm">
- <Set name="name">ActiveMQ Realm</Set>
- <Set name="config"><SystemProperty
name="jetty.home"
default="."/>/etc/amqrealm.properties</Set>
- </New>
- </Item>
- </Array>
- </Set>
-]]></script>
-</div></div>
-
-<p>2. Configure the users/passwords in the amqrealm.properties in jetty/etc</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-myAdmin: secret,amqAdmin
-]]></script>
-</div></div>
-
-<p>3. Configure the security constraint either in the webconsoles web.xml or
in jetty's webdefault.xml</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<security-constraint>
- <web-resource-collection>
- <web-resource-name>A Protected Page</web-resource-name>
- <url-pattern>/*</url-pattern>
- </web-resource-collection>
- <auth-constraint>
- <role-name>amqAdmin</role-name>
- </auth-constraint>
- </security-constraint>
-
- <login-config>
- <auth-method>BASIC</auth-method>
- <realm-name>ActiveMQ Realm</realm-name>
- </login-config>
-]]></script>
-</div></div>
-
-<p>This is just a sample configuration of a password protected webconsole.
Instead of the HashUserRealm one could also use a KerberosRealm or a
JDBCRealm.</p>
-
-<h4 id="WebConsole-ExampleconfigurationusingTomcat">Example configuration
using Tomcat</h4>
-
-<p>To start web console in Tomcat 5.x use the following steps:</p>
-
-<ul><li>Download the appropriate activemq-web-console war (<a shape="rect"
class="external-link"
href="http://repo1.maven.org/maven2/org/apache/activemq/activemq-web-console/";
rel="nofollow">http://repo1.maven.org/maven2/org/apache/activemq/activemq-web-console/</a>)
and copy it to ${TOMCAT_HOME}/webapps folder</li><li>Download the appropriate
activemq-all jar (<a shape="rect" class="external-link"
href="http://repo1.maven.org/maven2/org/apache/activemq/activemq-all/";
rel="nofollow">http://repo1.maven.org/maven2/org/apache/activemq/activemq-all/</a>)
and copy it to ${TOMCAT_HOME}/common/lib folder</li><li>Modify your
${TOMCAT_HOME}/bin/catalina.sh (.bat if you use Windows) and include the
following configuration</li></ul>
-
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-JAVA_OPTS="-Dwebconsole.type=properties \
--Dwebconsole.jms.url=tcp://localhost:61616 \
--Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi \
--Dwebconsole.jmx.user= \
--Dwebconsole.jmx.password="
-]]></script>
-</div></div>
-
-<ul><li>Start your Tomcat and visit the appropriate URL (e.g. <a shape="rect"
class="external-link" href="http://localhost:8080/activemq-web-console-5.0.0/";
rel="nofollow">http://localhost:8080/activemq-web-console-5.0.0/</a>)</li></ul>
-
-
-<h3 id="WebConsole-UsingtheWebConsole">Using the Web Console</h3>
-
-<p>The web console is depicted in the following image:</p>
-
-<p><img class="confluence-embedded-image confluence-thumbnail"
src="web-console.thumbs/web_console.png"
data-image-src="/confluence/download/attachments/36192/web_console.png?version=2&modificationDate=1293812132000&api=v2"></p>
-
-<p>To get started, go to the <a shape="rect" class="external-link"
href="http://localhost:8080/activemq-web-console/send.jsp";
rel="nofollow">Send</a> page and send a message to a queue (you can send
multiple if you like, see the message count field).</p>
-
-<p>Now that you have sent messages to a queue you should be able to <a
shape="rect" class="external-link"
href="http://localhost:8080/activemq-web-console/browse.jsp";
rel="nofollow">Browse</a> then and view the queue as an RSS or Atom feed.</p>
-
-<p>The Web Console has many features relative to it's tabs as shown in the
following table.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Tab</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Features</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>Home</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage";>System
Usage</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Queues</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Topics</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/advisory-message.html";>Viewing Advisory
Messages</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Subscribers</p></td><td colspan="1" rowspan="1" clas
s="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Connections</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/protocols.html";>Protocols</a></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Scheduled</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Send</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/delay-and-schedule-message-delivery.html";>Delay
and Schedule Message Delivery</a></p></td></tr></tbody></table></div>
-
-
-<h3 id="WebConsole-RunningtheWebConsoleonearlierversions">Running the Web
Console on earlier versions</h3>
-
-<p>The 5.3 webconsole does not run unmodified against a remote activemq 4.*.
However, it's easy to patch to avoid the new properties. See <a shape="rect"
class="external-link"
href="https://issues.apache.org/activemq/browse/AMQ-2145";>https://issues.apache.org/activemq/browse/AMQ-2145</a></p>
-
-<p>To run the ActiveMQ Web Console on earlier versions of ActiveMQ follow
these instructions</p>
-<ul><li>Install <a shape="rect" class="external-link"
href="http://maven.apache.org";>Maven</a> 2.0.4 or later</li><li>Grab the latest
<a shape="rect" href="source.html">Source</a> of ActiveMQ</li><li>Type the
following commands into a command shell</li></ul>
-
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-#mvn clean install -Dmaven.test.skip=true
-cd activemq-web-console
-patch -p0<AMQ-2145.diff
-mvn jetty:run -Dwebconsole.type=properties
-Dwebconsole.jms.url=tcp://localhost:61616 \
--Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
-Dwebconsole.jmx.user=system \
--Dwebconsole.jmx.password=manager
-]]></script>
-</div></div>
-
-<p>Most likely everyone except geronimo 2.1.x users will have upgraded to
activemq 5.x. Note that the jms connector url for geronimo is </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
--Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/JMXConnector
-]]></script>
-</div></div>
-
-<p>Now point your browser at <a shape="rect" class="external-link"
href="http://localhost:8080/"; rel="nofollow">http://localhost:8080/</a> (or the
appropriate port)</p>
-
-<p>And you should be in business!</p></div>
+</div></div><p>Standard connector is left enabled in this example, but you can
remove it in your configuration if you wish.</p><p>Note that these changes will
affect the whole web server, so if you're using <a shape="rect"
href="rest.html">REST</a> API or blob fileserver be sure to provide appropriate
credentials.</p><p>If you're interested in securing 5.3.1 (and 5.3.2) Web
consoles, take a look at <a shape="rect" class="external-link"
href="http://www.nighttale.net/activemq/securing-activemq-531-console.html";
rel="nofollow">this article</a>. For older versions, please refer to <a
shape="rect" class="external-link"
href="http://it.toolbox.com/blogs/unix-sysadmin/securing-activemq-web-console-27727";
rel="nofollow">this article</a></p><h3
id="WebConsole-UsingtheWebConsole">Using the Web Console</h3><p>The web console
is depicted in the following image:</p><p><img class="confluence-embedded-image
confluence-thumbnail" src="web-console.thumbs/web_console.png"
data-image-src="/confluence
/download/attachments/36192/web_console.png?version=2&modificationDate=1293812132000&api=v2"></p><p>To
get started, go to the <a shape="rect" class="external-link"
href="http://localhost:8080/activemq-web-console/send.jsp";
rel="nofollow">Send</a> page and send a message to a queue (you can send
multiple if you like, see the message count field).</p><p>Now that you have
sent messages to a queue you should be able to <a shape="rect"
class="external-link"
href="http://localhost:8080/activemq-web-console/browse.jsp";
rel="nofollow">Browse</a> then and view the queue as an RSS or Atom
feed.</p><p>The Web Console has many features relative to it's tabs as shown in
the following table.</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Tab</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Features</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Home</p></td><td colspan="1" rowspan="1
" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage";>System
Usage</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Queues</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Topics</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/advisory-message.html";>Viewing Advisory
Messages</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Subscribers</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Connections</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/protocols.html";>Protocols</a></p></td></tr><tr><td
colspan="
1" rowspan="1" class="confluenceTd"><p>Scheduled</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>Send</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/delay-and-schedule-message-delivery.html";>Delay
and Schedule Message Delivery</a></p></td></tr></tbody></table></div><h1
id="WebConsole-ExternalWebConsoles">External Web Consoles</h1><p>There are a
number of external web consoles for Apache ActiveMQ in separate open source
projects:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>External Project</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://hawt.io/"; rel="nofollow">hawtio</a></p></td><td colspan="1" ro
wspan="1" class="confluenceTd"><p>hawtio is an open source HTML5 web
application for visualising, managing, tracing and debugging Camel routes &
endpoints, ActiveMQ brokers, JMX, OSGi and logging. Here is a <a shape="rect"
class="external-link"
href="http://sensatic.net/activemq/activemq-and-hawtio.html";
rel="nofollow">blog entry</a> how to install hawtio as web console for
ActiveMQ.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://www.jboss.org/rhq"; rel="nofollow">RHQ</a></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>RHQ is an open source operational
monitoring tool which has support for Apache Camel (along with other Apache
projects like Tomcat, httpd, ActiveMQ etc)</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><a shape="rect" class="external-link"
href="http://www.hermesjms.com/confluence/display/HJMS/Home";
rel="nofollow">Hermes JMS</a></td><td colspan="1" rowspan="1" clas
s="confluenceTd">HermesJMS is an extensible console that helps you interact
with JMS providers making it simple to publish and edit messages, browse or
seach queues and topics, copy messages around and delete
them.</td></tr></tbody></table></div></div>
</td>
<td valign="top">
<div class="navigation">
