RabbitMQ installation tutorial in Linux environment

Table of Contents

Table of Contents

2.1 download rpm file

Baidu cloud resource address (recommended self-test can be successfully installed):

Link: pan.baidu.com/s/1mWsbW391qPQkw0QV1kSYNQ Extraction code: ck74 After copying this content, open the Baidu SkyDrive mobile app, the operation is more convenient

Or download using yum

yum install esl-erlang_17.3-1~centos~6_amd64.rpmyum install esl-erlang_17.3-1.x86_64.rpmyum install esl-erlang-compat-R14B-1.el6.noarch.rpm

2.2 Execute commands in sequence:

1) rpm -ivh esl-erlang-17.3-1.x86_64.rpm –force –nodeps

2) rpm -ivh esl-erlang_17.3-1centos6_amd64.rpm –force –nodeps

3) rpm -ivh esl-erlang-compat-R14B-1.el6.noarch.rpm –force –nodeps

First (Baidu cloud has RabbitMQ installation files) download link

3.1 installation:

rpm -ivh rabbitmq-server-3.4.1-1.noarch.rpm

3.2 Settings Profile

cp /usr/share/doc/rabbitmq-server-3.4.1/rabbitmq.config.example /etc/rabbitmq/rabbitmq.config

Enable user remote access

vi /etc/rabbitmq/rabbitmq.config

Unpack the comment, taking care to remove the trailing comma.

3.3 start, stop

service rabbitmq-server start ##Startservice rabbitmq-server stop ##stopservice rabbitmq-server restart ##Restart

3.4 Open web interface management tool

rabbitmq-plugins enable rabbitmq_management ##Open the management pageservice rabbitmq-server restart #restart

3.5 Setup Startup

chkconfig rabbitmq-server on #Auto-start at boot

3.6 Firewall opens port 15672

/sbin/iptables -I INPUT -p tcp --dport 15672 -j ACCEPT/etc/rc.d/init.d/iptables save

4.1. Homepage overview

connections: Both producers and consumers need to establish a connection with RabbitMQ before completing the production and consumption of messages. You can view the connection status here

channels: Channels. After the connection is established, a channel will be formed, and the delivery of messages will depend on the channel.

Exchanges: Exchanges, the way to implement messages

Queues: Queues, that is, message queues, messages are stored in the queue, waiting for consumption, and then removed from the queue after consumption.