MessageBus Setup (ActiveMQ)
How to install ActiveMQ on a workstation or server.
Download the currently used ActiveMQ here: ActiveMQ 5.5.1 Release.
ActiveMQ can be installed by following the getting-started guide.
The default tcp port for the http administration page is 8161 and the tcp port for the broker itself is 61616, so these two ports must be opened for incoming connections in surrounding firewalls. If the ActiveMQ instance participates in a network of brokers, firewalls must be open for outgoing connections to these ActiveMQ instances' ports
Deployment Consideration
Multiple instances
Instead of running one message bus instance for all collections, you may consider running multiple broker instances to improve confidentiality and availability.
Pros
- No risk of users from different collections reading each others messages.
- Possible to service brokers on a pr. collection basis
Cons
- Need to administrate multiple broker instances, which requires more work from the operation department.
Running a network of brokers across organisations
ActiveMQ provides functionality for clustering multiple broker together to be exposed as one message bus. You might use this to have a network of brokers running in different organizations to create a high degree of redundancies.
Pros
- Better redundancy.
Cons
- More complex setup
- Many more error possiblities.
- Requires more organizational coordination
See also
- Running multiple activemq instances on the same server — How to configure multiple ActiveMQ instances in a single base installation
- Running a network of brokers
- Enabling SSL
- Installation on Redhat Server
- Installation of single ActiveMQ on Redhat Server