Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

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
Copiar enlace

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
Copiar enlace

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>
Copy to Clipboard Toggle word wrap

Configuring Tomcat
Copiar enlace

To deploy the Web console in Tomcat 5.x:
  1. 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/.
  2. Copy the Web console's WAR to the TOMCAT_HOME/webapps folder.
  3. Download activemq-all-6.0.0.redhat-024.jar from http://repo.fusesource.com/nexus/content/repositories/releases/org/apache/activemq/activemq-all/5.8.0.redhat-60024/.
  4. Copy activemq-all-6.0.0.redhat-024.jar to the TOMCAT_HOME/common/lib folder.
  5. 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"
    Copy to Clipboard Toggle word wrap
  6. Restart Tomcat.
The Web console will be available at tomcatURI/activemq-web-console-5.8.0.redhat-60024.

Monitoring clusters
Copiar enlace

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.url as 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
Copy to Clipboard Toggle word wrap
For more information about master/slave clusters see Fault Tolerant Messaging.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat