Deploying the ActiveMQ-WebConsole=================================From ActiveMQ 5.9 onwards ActiveMQ ships with a web console whichis accessible at its usual location at: http://localhost:8161/admin/In the default configuration ActiveMQ automatically starts the web console in thesame VM as the broker. The console is accessibly under http://localhost:8161/admin/.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 theconf/jetty-real.properties file. And in the conf/jetty.xml file you can configureto disable login for the web consoles.However it's also possible to start the web console in a separate VM and connect itto the broker via JMS and JMX. The reasons to do so may include increased reliabilityof the broker itself (f.e. the embedded web console could use up all the availablememory) or the monitoring of a master/slave system.Just deploy the war into your preferred servlet container and add the apache-activemq.jarto the classpath of the container (f.e. under Tomcat that'd be common/lib and underJetty the lib-directory). Two options are available for the configuration of the brokerand jmx uri(s): * System Properties ----------------- Specify the following system properties in your web container: -Dwebconsole.type=properties -Dwebconsole.jms.url= (f.e. tcp://localhost:61616) -Dwebconsole.jmx.url= (f.e. service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi) * JNDI ---- If your servlet container supports JNDI it's possible to use a JMS-ConnectionFactory configured outside the war:java:comp/env/jms/connectionFactory: javax.jms.ConnectionFactory for the brokerjava: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.0To install the broker: features:install activemq-brokeror the client only (web console not available): features:install activemq-clientYou can then use web:list to see the context-path the console is accessible,that is usually: http://localhost:8181/activemqwebMaster/Slave monitoring-----------------------To configure the web console to monitor a master/slave configuration configure the jms/jmxas follows (system properties shown, but this option is also available when using JNDI): -Dwebconsole.jms.url=failover:(tcp://serverA:61616,tcp://serverB:61616) -Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://serverA:1099/jmxrmi,service:jmx:rmi:///jndi/rmi://serverB:1099/jmxrmiWith this configuration the web console with switch to the slave as the master is no longeravailable and back as soon as the master is back up.