RabbitMQ Official document translation for Windows installation!

RabbitMQ Windows installation and configuration

Official website windows:

Http://www.rabbitmq.com/releases/rabbitmq-server/v3.6.10/rabbitmq-server-3.6.10.exe

GitHub Windows Edition:

HTTPS://GITHUB.COM/RABBITMQ/RABBITMQ-SERVER/RELEASES/DOWNLOAD/RABBITMQv36_10/ Rabbitmq-server-3.6.10.exe

1. Uninstall the previous version

If your existing Setup program is planning to upgrade an Erlang VM from a 32-bit version to a 64-bit version, you must uninstall the agent before you can upgrade the VM. Setup will not be able to stop or remove services that are installed with Erlang VMS with different schemas.

2. Install the server

RABBITMQ installation dependent environment: Erlang

Erlang Linux Installation Detailed: http://flyingdutchman.iteye.com/blog/1885566

1) First, it takes approximately 5 minutes to download and run the Erlang Windows binaries.

2) then run the Setup program, Rabbitmq-server-3.6.10.exe. It takes approximately 2 minutes, and the RABBITMQ is set to a service, and the default configuration is configured.

3. Running the RABBITMQ service

customizing RABBITMQ environment variables

The service will run well with its default settings. You may need to customize the RABBITMQ environment or edit the configuration.

Run RABBITMQ

The RABBITMQ service starts automatically. You can stop/reinstall/start the RABBITMQ service from the Start menu.

Management Services

You can find a link to the RABBITMQ directory in the Start menu. Here is also a link to the command Prompt window that is launched into the Sbin directory in the Start menu. This is the most convenient way to run various command-line tools.

Port access

Firewalls and other security tools may prevent RABBITMQ from binding to ports. When this happens, RABBITMQ will not start. Make sure that the following ports are open:

Peer discovery Services used by 4369:EPMD,RABBITMQ nodes and CLI tools

5672,5671: Used by AMQP 0-9-1 and 1.0 clients without TLS and TLS

25672:erlang distribution is used for inter-node and CLI tool communication and is allocated from dynamic range (by default to a single port, calculated as AMQP port + 20000). See the Network Guide for details.

15672:http API client and Rabbitmqadmin (only when management plugin is enabled)

61613,61614: No Stomp clients with TLS (only stomp plugin enabled)

1883,8883:(does not have an MQTT clients with TLS, if MQTT is enabled plugin

15674:stomp-over-websockets clients (only Web STOMP plugin enabled)

15675:mqtt-over-websockets clients (only when web MQTT plugin is enabled) \

The RABBITMQ can be configured to use a different port.

Default User Access

The agent creates a user guest with password guest. These credentials are typically used by clients that are not configured. By default, these credentials are used only when connecting to a proxy with localhost, so you need to take action before connecting to any other machine.

For information about how to create more users, remove the guest user, or allow remote access to the guest user, see Access control documentation

Managing the Broker

To stop the agent or check its status, use Rabbitmqctl.bat in Sbin (as an administrator)

Stopping the Broker:rabbitmqctl stop.

Checking the Broker status:rabbitmqctl Status

If no agent is running (that is, Nodedown), all RABBITMQCTL commands will report that the node is missing. For more information see: Rabbitmqctl

4. Logging

The output from the server is sent to the Rabbitmq_nodename.log file in the Rabbitmq_log_base directory.

Other log data is written to Rabbitmq_nodename-sasl.log. The broker is always appended to the log file, so the full log record is preserved.

You can use Rabbitmqctl rotate_logs to rotate the log

5. Troubleshooting as a service runtime

If the Erlang VM crashes while RABBITMQ is running as a service, instead of writing the crash dump to the current directory (which does not make sense for the service), it writes the Erl crash.dump file in the base directory of the RABBITMQ server(by RABBITMQ Base environment variable setting). The default is%appdata%\%rabbitmq_servicename%-typically%appdata%\ RABBITMQ).

Windows-Specific issues

Our goal is to make RABBITMQ a first-class citizen on Windows. However, sometimes we have no control over the situation. See Windows-specific Issues page

Get help

If you have any questions or need help, please feel free to ask RABBITMQ mailing list

RabbitMQ Official document translation for Windows installation!