Windows under Install configuration RABBITMQ

Install the deployment 1. Current environment and reference sources

1. Deployment environment: Windows Server R2 Enterprise
2. Official installation Deployment Documentation: http://www.rabbitmq.com/install-windows.html Official Document description

2. Installing Erlang

First, download and run the Erlang Windows binaries. After the installation is successful, the Erlang program should be found in all programs.

3. Installing RABBITMQ

On the official page, download the corresponding installation package, note that the RABBITMQ installation will occupy several ports, and firewalls and other security tools may prevent RABBITMQ from binding to the port. When this happens, RABBITMQ will not start. Make sure that you can open the following ports and, of course, install them yourself by modifying the configuration file to modify the occupied ports and then turn on the service.

• 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). For more information, see your network guide.
• 15672:http API client and Rabbitmqadmin (only when the management plug-in is enabled)
• 61613,61414: No Stomp client with TLS (only stomp plug-in enabled)
• 1883,8883:( MQTT client not and with TLS if the Mqtt plugin is enabled
• 15674:stomp-over-websockets Client (only Web STOMP plugin enabled)
• 15675:mqtt-over-websockets Client (only when the Web MQTT plugin is enabled)

After the installation is successful, all installed apps and plugins can be found in the Start menu.

4. Turn on the service

In the Start menu, click RABBITMQ Service start to open the services, you can go to the Service Manager to confirm whether the success is turned on. Is the related service found on the current machine and the status is started.

After the RABBITMQ service is set up and started, a further configuration of RABBITMQ is required, and the installed version provides the Rabbitmq_management plug-in, which provides management and monitoring services for the current RABBITMQ service through 15672来.

5. Configure RABBITMQ

1. In the Start menu, locate Rabbitmq Command Promt, open the console

2 input commands

1	rabbitmq-plugins enable rabbitmq_management

3. After enabling the plug-in to see some of the prompt information, and then you can go through http://server-name15672 access, the default user name and password for guest,guest, go to the Administration page, we can see a few large tab, This and RABBITMQ also in a sense reflect the overall structure of the RABBITMQ, which is not elaborated in detail.

4. Configure Allow remote access

In more cases, the queue service is often not on our local machine, we need to control RabbitMQ remotely, but by default it cannot be accessed by http://server-name, 15672来 can be modified by \RABBITMQ Server\ Rabbitmq_server-3.6.10\etc under Rabbitmq.config to set the Allow guest user to Telnet, modify it to the following value, and then restart the RABBITMQ service in Service Manager.

The default RabbitMQ will generate a configuration file in C:\Users\Administrator\AppData\Roaming\RabbitMQ, Rabbitmq.config inside is the actual configuration information, if the diagram is convenient, can also be directly changed here.

1	[{rabbit, [{loopback_users, [guest]}]}].

Windows under Install configuration RABBITMQ