Scripted deployment of a RabbitMQ cluster (master and slave) for use with Symantec Mobility Suite


Article ID: 178601


Updated On:


Mobility Application Management Mobility Device Management Mobility Suite




Note: This article outlines how to use prepared scripts to deploy a high-availability RabbitMQ cluster for use with Symantec Mobility Suite 5.0 or later.  Each script adds the necessary firewall rules to allow for message queuing and cluster management between each node (for up to 10 slaves).  For manual instructions on configuring both the RabbitMQ master and slave servers, see HOWTO100093.  Additional information is available at  This document assumes a Centos 6.5 or Redhat equivalent environment.
A high-availability RabbitMQ cluster requires the following:
  • A minimum of two servers, each in a different data center (or at the least, running on different hardware).
  • A high-reliability network connection between the RabbitMQ servers.
  • The Symantec Mobility front end servers are configured to point to the single address of a master RabbitMQ server.
  1. Transfer the attached scripts ( and to their respective servers.
    Tip: Follow HOWTO110248 to transfer each file.
  2. On the rabbit master server execute the script by entering the following two lines, as root:
    sudo yum -y install unzip
    sudo unzip

    sudo chmod +x
    sudo ./
  3. Follow the prompts within the script.
  4. Take note of the cookie and IP values, displayed after the installation completes.
  5. On the rabbit slave server execute the script, by entering the following two lines, as root:
    sudo yum -y install unzip
    sudo unzip

    sudo chmod +x
    sudo ./
  6. Follow the prompts to complete the RabbitMQ cluster installation.

Important: These servers should not be accessible from outside the local network; and for the installation scripts to succeed, outbound communication is required; once the installation completes Network communication is only required between the RabbitMQ servers and each Mobility front end (FE).

Attachments get_app get_app