Replicating the Message Broker

The message broker is responsible for communicating events across Sisense components. The message broker should be replicated as part of a high availability environment.

To replicate the message broker:

  1. On your application server:
    1. In Windows Services, stop the Sisense.Broker service.
    2. In C:\Windows\System32\config\systemprofile\ , copy the .erlang.cookie to C:\Users\Administrator .
  1. On your build server:
    1. Copy the .erlang.cookie from the application server to C:\Users\Administrator and C:\Windows\System32\config\systemprofile\
    2. In Windows Services, restart the Sisense.Broker service.
    3. Open the Command Prompt as an Administrator and in C:\Program Files\Sisense\infra\Rabbitmq\sbin , run rabbitmqctl.bat status
    4. Save the nodename for Step 3.4.

  1. In the application server:
    1. In Windows Services, start the Sisense.Broker service.
    2. Open the Command Prompt as an Administrator and in C:\Program Files\Sisense\infra\Rabbitmq\sbin :
    3. Run rabbitmqctl.bat stop_app.
    4. Run rabbitmqctl.bat join_cluster nodename.
    5. Run rabbitmqctl.bat start_app.
    6. Run rabbitmqctl.bat set_policy ha-all "." "{""ha-mode"":""all""}".
    7. In Windows Services, restart the Sisense.Broker service.
    8. In your browser, open localhost:3030. In General, edit the ‘RabbitMQ Connection String’ and enter the IP of the application server and build server delimited by a comma:
      For example:
      (amqp://applicationServerIP:5672,amqp://buildServerIP:5672)
  1. For each server, in the Configuration Manager, click at the top of the Configuration Manager and then confirm that you want to restart the relevant services by clicking Yes.



.r.