Pre-Installation Requirements
Hardware:
- ~ 60 MB of free disk space for the ActiveMQ 5.x binary distribution.
(you need additional disk space for storing persistent messages to disk) - ~ 300 MB of free disk space for the ActiveMQ 5.x source or developer's distributions.
Operating Systems:
- Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.
- Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.
Environment:
- Java Runtime Environment (JRE) JRE 1.7 (1.6 for version <=5.10.0)
(a JDK is required if you plan to recompile source code) - The JAVA_HOME environment variable must be set to the directory where the JRE is installed
(Unix: the binary "java" has to be resolvable by the PATH variable; execute "which java" to verify) - Maven 3.0.0 build system
(only if you plan to recompile source code) - JARs that will be used must be added to the classpath.
(only if you plan to recompile source code)
Installation Procedure for Windows
下载windows的版本,解压在一个环境目录下面即可。
Start ActiveMQ from the target directory, for example:
Starting ActiveMQ
There now follows instructions on how to run the ActiveMQ Message Broker.
On Windows:
From a console window, change to the installation directory and run ActiveMQ
:
|
where activemq_install_dir
is the directory in which ActiveMQ was installed, e.g., c:\Program Files\ActiveMQ-5.x
.
Then type:
启动方法:
|
NOTE: Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.
Listen port
ActiveMQ's default port is 61616. From another window run netstat and search for port 61616.
From a Windows console, type:
|
OR
From a Unix command shell, type:
|
Monitoring ActiveMQ
You can monitor ActiveMQ using the Web Console by pointing your browser at
From ActiveMQ 5.8 onwards the web apps is secured out of the box.
The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.
Or you can use the JMX support to view the running state of ActiveMQ.
For more information see the file docs/WebConsole-README.txt
in the distribution.
Stopping ActiveMQ
For both Windows and Unix installations, terminate ActiveMQ by typing "CTRL-C" in the console or command shell in which it is running.
If ActiveMQ was started in the background on Unix, the process can be killed, with the following:
|
Configuring ActiveMQ
The ActiveMQ broker should now run. You can configure the broker by specifying an Xml Configuration file as a parameter to the activemq command. An alternative is to use the Broker Configuration URI to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also
Also see Configuring Transports to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.
See the Initial Configuration for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code
If you want to use JNDI to connect to your JMS provider then please view the JNDI Support. If you are a Spring user you should read about Spring Support
After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the Configuration section.
Additional Resources
If you are new to using ActiveMQ, running the Web Samples or the Examples is a good next step to learn more about ActiveMQ.
The Commercial Providers listed on the Support page may also have additional documentation, examples, tutorials, etc... that can help you get started.