Configuring Message Broker for YOUnite

Owned by Mark Fitzpatrick (Unlicensed)
Last updated: Nov 27, 2017 by Former user (Deleted)
1 min read

The Message Broker (activeMQ) is already configured and part of the Docker Compose stack for YOUnite. So, no extra configuration is required to be able to run the system with a customized Message Broker. The steps mentioned below outline what is configured and where.

Message Broker configuration for YOUnite involves the following:

  1. Modify a Docker image to add customization. YOUnite uses webcenter/activemq:5.14.3 Docker image.
  2. Configure for secure communication: YOUnite uses SSL/TLS for securing communication over the message bus. This is accomplished using x.509 certificates.
    The ${ACTIVEMQ_CONF}/activemq.xml file is used to specify transports and one is added for SSL/TLS that uses NIO and SSL, and it listens on port 61617.
  3. Open ports only for the transports that are used by YOUnite. This too is specified in the ${ACTIVEMQ_CONF}/activemq.xml file.
  4. Use default persistence: Currently YOUnite is using the default persistence (KahaDB), but this may change later based on message persistence requirements.

Please note that the above0mentioned configuration is specific to ActiveMQ 5.14.3 and may change with the later version of ActiveMQ or if a different Message Broker is chosen.