Red Hat SummitRed Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Este contenido no está disponible en el idioma seleccionado.
4.3. Deploying a Standalone Web Console
| Revision History | |
|---|---|
| 10/29/12 | |
| updated the url used to download the components | |
Overview
For more security or reliability reasons you can deploy the Web console as a standalone application in Tomcat or another Web container. When running as a standalone application, the Web console can be set up to monitor Master/Slave clusters.
Disabling the Web embedded console
There is no need to disable the embedded Web console when using a standalone console. However, If you are using a standalone Web console, there is no reason to use the resources required by the embedded console. Nor is there a reason to leave an extra administrative access point open.
To disable the embedded Web console, you simply need to comment out, or remove, the
import element that imports the Jetty configuration into your broker's configuration file as shown in Example 4.3, “Disabling the Embedded Web Console”.
Example 4.3. Disabling the Embedded Web Console
<beans ... >
<broker ... >
...
</broker>
<!-- <import resource="jetty.xml"/> -->
</beans>Configuring Tomcat
To deploy the Web console in Tomcat 5.x:
- Download the Web console's WAR,
activemq-web-console-6.0.0.redhat-024.war, from http://repo.fusesource.com/nexus/content/repositories/releases/org/apache/activemq/activemq-web-console/5.8.0.redhat-60024/. - Copy the Web console's WAR to the
TOMCAT_HOME/webappsfolder. - Download
activemq-all-6.0.0.redhat-024.jarfrom http://repo.fusesource.com/nexus/content/repositories/releases/org/apache/activemq/activemq-all/5.8.0.redhat-60024/. - Copy
activemq-all-6.0.0.redhat-024.jarto theTOMCAT_HOME/common/libfolder. - Modify
TOMCAT_HOME/bin/catalina.sh(.bat)to include the configuration in Example 4.4, “Configuration for Deploying the Web Console in Tomcat”.Example 4.4. Configuration for Deploying the Web Console in Tomcat
JAVA_OPTS="-Dwebconsole.type=properties \ -Dwebconsole.jms.url=brokerURL \ -Dwebconsole.jmx.url=brokerJMXURL \ -Dwebconsole.jmx.user=JMXUserName \ -Dwebconsole.jmx.password=JMXPassword"
- Restart Tomcat.
The Web console will be available at tomcatURI/activemq-web-console-5.8.0.redhat-60024.
Monitoring clusters
It's possible to configure the Web console to monitor a master/slave cluster. To do so:
- Specify the JMS URL,
webconsole.jms.url, with a failover: URI specifying the brokers in the cluster. - Specify the JMX URL,
webconsole.jmx.urlas a comma separated list that contains the JMX URL for each of the brokers in the cluster.
Example 4.5, “Configuration for Monitoring a Cluster with the Web Console” shows the properties for monitoring a cluster using the Web console.
Example 4.5. Configuration for Monitoring a Cluster with the Web Console
-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/jmxrmi
For more information about master/slave clusters see Fault Tolerant Messaging.
