In fact, English has been bad, but now some technology, must rely on reading English documents to learn, so today try to translate the official deployment of ACTIVEMQ documents.
Deploying the activemq-console
=================================
From ActiveMQ5.9 Activemq comes with a web console
The usual access paths are:
http://localhost:8161/admin/
Active default configuration automatically launches the Web console's VM agent, which is very convenient for the console
http://localhost:8161/admin/.
The console agent may ask the user who first logged in
The default user name and password is admin/admin
In the Conf/jetty-real.properties file, you can configure the default login console for the user,
And in this file you can configure users who cannot log on to the console.
With JMS and JMX proxies, it is possible to open a separate virtual machine to start the console, because perhaps to include
Enhance its own reliability (e.g., embedded consoles can use all reliable memory resources) or monitor master-slave systems
Simply deploy your first servlet container to join the Apache-activemq.jar jar package so that it is included under the container path
(as in the case of Tomcat Common/lib in Jetty's lib directory) these two options can be configured with proxies and JMS.
* System Properties
-----------------
Specify the following system properties into the Web container:
-dwebconsole.type=properties Property
-dwebconsole.jms.url=<url the URL of the broker> (such as. tcp://localhost:61616) Agent
URL of-dwebconsole.jmx.url=<jmx URL to the broker> (such as. service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi) JMS Proxy
* JNDI java naming and directory interfaces
----
If your servlet container can support the use of Jndi, you can use the Jms-connectionfactory
War package outside of configuration:
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)
Install console to Apache Karaf/apache servicemix
-----------------------------------------------------------
If you are using Apache Karaf, you can install the ActiveMQ agent or the client will use it in the container:
Chooseurl ACTIVEMQ 5.9.0
Install Agent:
Install Activemq-broker
or turn the customer list (the console is not available):
Install Activemq-client
By looking at the context path console access list, you can look at the Web Access path,
Usually: Http://localhost:8181/activemqweb
Master and slave Monitoring
-----------------------
Install JMS/JMX master and slave console
Monitor the following (System properties, which can also use 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/jmxrmi
Configuration master-Slave control desktop is no longer reliable, the configuration requires a certain backup.
The following is the original
Deploying the Activemq-webconsole
=================================
From ActiveMQ 5.9 onwards ActiveMQ ships with a web console which
is accessible at it usual location at:
http://localhost:8161/admin/
In the default configuration ActiveMQ automatically starts the Web console in the
Same 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 "the".
The default username and password is admin/admin.
The Web console can configure the default users, in the
Conf/jetty-real.properties file. And in the Conf/jetty.xml file for you can configure
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 does may include increased reliability
of the broker itself (F.E. The embedded Web console could use the ' all ' available
memory) or the monitoring of a master/slave system.
Just Deploy the war into your preferred servlet container and add the Apache-activemq.jar
To the classpath of the container (F.E. Under Tomcat, "D be common/lib and under
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:///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 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 a using Apache Karaf, you can install ActiveMQ broker/client to 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
can then use Web:list to and 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 the JMS/JMX
as follows (System properties shown, but this option are 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/jmxrmi
The With this configuration the Web console with the switch to the slave as the master no longer
Available and back as soon as the master are back up.
This article comes from csdn user nothing http://write.blog.csdn.net/postedit/52100362
</pre><pre code_snippet_id= "1802768" snippet_file_name= "blog_20160803_13_1258721" "Name=" code "class=" Plain ">