Sei sulla pagina 1di 2

Deploying the ActiveMQ-WebConsole

=================================
From ActiveMQ 5.9 onwards ActiveMQ ships with a web console which
is accessible at its usual location at:
http://localhost:8161/admin/
In the default configuration ActiveMQ automatically starts the web console in th
e
same VM as the broker. The console is accessibly under http://localhost:8161/adm
in/.
The broker may ask for credentials to login the web console the first time.
The default username and password is admin/admin.
In the web console you can configure the default users, in the
conf/jetty-real.properties file. And in the conf/jetty.xml file you can configur
e
to disable login for the web consoles.
However it's also possible to start the web console in a separate VM and connect
it
to the broker via JMS and JMX. The reasons to do so may include increased reliab
ility
of the broker itself (f.e. the embedded web console could use up all the availab
le
memory) or the monitoring of a master/slave system.
Just deploy the war into your preferred servlet container and add the apache-act
ivemq.jar
to the classpath of the container (f.e. under Tomcat that'd be common/lib and un
der
Jetty the lib-directory). Two options are available for the configuration of the
broker
and jmx uri(s):
* System Properties
----------------Specify the following system properties in your web container:
-Dwebconsole.type=properties
-Dwebconsole.jms.url=<url of the broker> (f.e. tcp://localhost:61616)
-Dwebconsole.jmx.url=<jmx url to the broker> (f.e. service:jmx:rmi:///j
ndi/rmi://localhost:1099/jmxrmi)
* JNDI
---If your servlet container supports JNDI it's possible to use a JMS-Connecti
onFactory
configured outside the war:
java:comp/env/jms/connectionFactory: javax.jms.ConnectionFactory for the
broker
java:comp/env/jmx/url: URL of the brokers JMX (Type java.lang.String)

Installing Web consoles in Apache Karaf / Apache ServiceMix


----------------------------------------------------------If you are using Apache Karaf, you can install ActiveMQ broker / client into the

container using:
features:chooseurl activemq 5.9.0
To install the broker:
features:install activemq-broker
or the client only (web console not available):
features:install activemq-client
You can then use web:list to see the context-path the console is accessible,
that is usually: http://localhost:8181/activemqweb
Master/Slave monitoring
----------------------To configure the web console to monitor a master/slave configuration configure t
he jms/jmx
as follows (system properties shown, but this option is also available when usin
g JNDI):
-Dwebconsole.jms.url=failover:(tcp://serverA:61616,tcp://serverB:61616)
-Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://serverA:1099/jmxrmi,servic
e:jmx:rmi:///jndi/rmi://serverB:1099/jmxrmi
With this configuration the web console with switch to the slave as the master i
s no longer
available and back as soon as the master is back up.