Hi Danny,
ActiveMQ is a standalone server which people often put on the admin
node since it does not need a lot of resources but you can put it
anywhere you want. It's a bit like a database.
Let's assume you installed it on your admin node and made sure that
your firewall lets other servers access it through TCP port 61616
(default).
On your admin, you can then just leave the default setting in the
custom.properties which looks for ActiveMQ on 127.0.0.1. On all other
servers, you have to point it to your admin node instead, setting
something like:
activemq.broker.url=failover://(tcp://admin.example.com:61616)?initialReconnectDelay=2000&maxReconnectAttempts=2
The `?initialReconnectDelay=2000&maxReconnectAttempts=2` is something
that will increase the stability in case of network problems and I
would append it. It's in the default configuration as well.
If you want to, you can also specify credentials for ActiveMQ access or
configure your firewall to allow access from some hosts only to
increase security. Though, if it's your first try, it might be easier to
leave this for now and come back to it later.
For more details, have a look at our message broker configuration
documentation at:
https://docs.opencast.org/r/2.2.x/admin/configuration/message-broker/
Best regards,
Lars