How to install rabbitmq server on Windows?

H开发者_开发知识库ow do I install RabbitMQ on Windows?

Installation from a complete bundle

The bundle zip file contains all the files listed in the next section, including an Erlang system installer and the RabbitMQ broker binary distribution, the .Net client, as well as an archive of the Java librabbitmq client library.[http://www.rabbitmq.com/download.html]

1. install for windows erlang5.7.4 [otp_win32_R13B03].
2. Download rabbitmq-server-windows-2.0.0.zip from the download page.

3.Contained in the zip file is a directory named rabbitmq_server-2.0.0. You should extract this folder to somewhere appropriate for application files, for example C:\Program Files\RabbitMQ.

4.Once the files are successfully extracted, you should end up with a structure similar to C:\Program Files\RabbitMQ\rabbitmq_server-2.0.0.

5. set the environment variable ERLANG_HOME to point to your Erlang directory (e.g. C:\Program Files\erl5.7.4)

6.by default RABBITMQ_BASE path for windows C:\Documents and Settings\User\Application Data\RabbitMQ. your all requird details information such as log file etc are stored in this dir.

Running the Server as an Application

1.rabbitmq_server-2.0.0\sbin and double-click the rabbitmq-server.bat file.

Running the Server as a Service

1.Log in as an administrator and open a command shell (cmd.exe) in the sbin directory where the broker was installed. Install the service by executing

rabbitmq-service.bat install

2.Ensure that a service with the name RABBITMQ_SERVICENAME now appears in the services control panel (services.msc).

for more details just visit http://www.rabbitmq.com/install.html

RabbitMQ is designed to be built on a Unix machine (we regularly use various Linux distros and OSX). The community also tests on FreeBSD.

That said, it's certainly possible to build on Windows, but you need a POSIX-like environment. The simplest way is by far with cygwin:

• Install the latest Erlang from here,
• Get the Cygwin installer from here,
• Run it to install the base system; make sure you also have make, libxslt/xlstproc and mercurial selected; if you forget anything, you can safely re-run the installer to get the missing programs;
• Update your PATH to include python and erl (so, add something like C:\Program Files\erl5.8.3\bin and C:\Python27\bin; of course, your paths will probably be different); check that everything works by running python and erl,
• get the RabbitMQ source (you'll also need the codegen) via Mercurial;
• from a cygwin shell, run make in the rabbitmq-server directory.

The last two steps are the normal Unix installation procedure. See the official instructions for more details.

Also, note that you may have to run the broker (scripts/rabbitmq-server.bat) from a normal command prompt and not a cygwin shell. This is due to a discrepancy between what Erlang and Cygwin think the root directory is /.

If you have any problems, send a message to the rabbitmq-discuss mailing list. The developers make a point of answering all queries posted there.

There is not really much point in doing this unless you intend to develop Erlang code, and in that case you should spend a day or two learning the basics of Erlang. After that it will be less of a struggle because RabbitMQ is written in Erlang.

I have built Erlang on Linux, but on Windows I just installed the binary package because it is just a test/dev environment for me. On Linux I had problems figuring out how to install the binaries and on Windows it took a while to figure out where to put the config file so that I could load plugins.

In any case, you don't run RabbitMQ on Windows or on Linux because it doesn't work that way. Like many Erlang applications, RabbitMQ runs on the cloud (your private cloud) and really expects to be part of a cluster of several servers all running a shared MQ broker service.

Go to this slide presentation from Google Tech Talks and look at the diagram on slide 17. That is how you would have 4 servers running RabbitMQ in a cluster to serve local clients where local might be one data center out of several in the same geographic region. Local traffic would not cross the cluster but applications don't need to do anything special in order to send/receive messages across the cluster.

Slide 22 sums it up "Making Erlang disappear". You get all the benefits of Erlang without having to learn anything about it. Just use AMQP messaging and many processes. Say goodbye to threads.

First, download and install Erlang for Windows from Download Erlang/OTP:

Then, download and install RabbitMQ for Windows from Direct Downloads:

Don't bother. Apparently it is "somehow" possible with Cygwin but I gave up too and consequently lost interest. This is a common problem rooted in Erlang culture, which doesn't really seem to understand cross-platform development.